[OpenAFS] "FSYNC_clientInit temporary failure" fails to be temporary
ted creedon
tcreedon@easystreet.com
Mon, 15 Mar 2004 09:25:43 -0800
I did the same thing for my servers. The local /etc/hosts file contains the
ip address and FQDN of all the servers
Look at your lan port (eth0, typically) with ethereal
tedc
-----Original Message-----
From: openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs.org]
On Behalf Of David Miller
Sent: Monday, March 15, 2004 1:56 AM
To: Jon Larsson
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] "FSYNC_clientInit temporary failure" fails to be
temporary
I've had the exact same problems...also under debian woody
I think it was due to some name resolution problems.
make sure you have the forward and reverse DNS entries resolving for
your hostname, and you dont have any entries in /etc/hosts that might
confuse things
For me the problem seemed to be in /etc/hosts I had my hostname
resolving to localhost (127.0.0.1)
which the debian (and most other distros) installer put in there.
I changed the /etc/hosts entry to reflect the same as in DNS, the
machines real non-local IP.
and that problem went away.
I think its because openafs doesnt listen on the local interface...But i
could be wrong.
Also notice the warning in bos status:
"Bosserver reports inappropriate access on server directories "
you need to chmod 755 /etc/openafs/server
Jon Larsson wrote:
> Hi!
>
> After having used AFS from the client side for a number of years, I'm
> currently in the process of setting up my first server (on an i386
> Debian Woody system). I've followed the instructions in the quick
> start guide together with the ones on
> http://www.debianplanet.org/node.php?id=816.
>
> I've now reached the point where I'm to create the fs instance. The
> anticipated "FSYNC_clientInit temporary failure (will retry)" appears,
> with a trailing ": Connection refused". What's odd is, that it doesn't
> stop. I've now left it for an hour or so, and that same message
> appears over and over again at regular intervals. After every five
> such messages, a "FSYNC_clientInit failed (giving up!): Connection
> refused" is printed, and the fs instance exits with an error and
> restarts. I've also tried manually stopping and restarting the server,
> but to no avail.
>
> Below follows output from bos status.
>
>
> putte:/# bos status putte -long -noauth
> Bosserver reports inappropriate access on server directories
> Instance ptserver, (type is simple) currently running normally.
> Process last started at Sat Mar 13 12:12:45 2004 (4 proc starts)
> Last exit at Sat Mar 13 12:12:45 2004
> Command 1 is '/usr/lib/openafs/ptserver'
>
> Instance fs, (type is fs) currently running normally.
> Auxiliary status is: file server running.
> Process last started at Sat Mar 13 12:20:51 2004 (30 proc starts)
> Last exit at Sat Mar 13 12:20:51 2004
> Last error exit at Sat Mar 13 12:20:51 2004, by vol, by exiting
> with code 1
> Command 1 is '/usr/lib/openafs/fileserver'
> Command 2 is '/usr/lib/openafs/volserver'
> Command 3 is '/usr/lib/openafs/salvager'
>
> Instance buserver, (type is simple) currently running normally.
> Process last started at Sat Mar 13 12:12:45 2004 (2 proc starts)
> Last exit at Sat Mar 13 12:12:45 2004
> Command 1 is '/usr/lib/openafs/buserver'
>
> Instance vlserver, (type is simple) currently running normally.
> Process last started at Sat Mar 13 12:12:45 2004 (2 proc starts)
> Last exit at Sat Mar 13 12:12:45 2004
> Command 1 is '/usr/lib/openafs/vlserver'
>
>
> Any kind of help with this is appreciated.
>
> / Jon
>
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info