Subject: Re: [netatalk-admins] afpd grief
From: Tim Bell (bhat@cs.mu.OZ.AU)
Date: Fri Jul 25 1997 - 01:00:23 EDT
m* wrote:
>
> my 1.4b2-4 server logs:
>
>
> Jul 22 16:28:37 apps afpd[291]: atp_sreq to (5) 32511.164:245
> Jul 22 16:31:19 apps afpd[291]: kill: No such process
> Jul 22 16:31:19 apps afpd[291]: asp_alrm: 6149 timed out
>
>
> after which all conections are dropped and a reboot is required
> to restore connectivity.
I am having similar problems; the last three messages I get before
afpd stops working are exactly the same.
> in rtfm and search mode, but pointers would be helpful.
I have no answers, but a very kludgy workaround which I'm using at
the moment -- I restart afpd every morning. Note that a reboot is
not required, nor do you need to stop any other netatalk services.
After the restart, everything is fine, until it breaks again. This
usually happens within the next 24 hours (often 12 hours), so perhaps
I should be restarting every 12 hours.
I am running Debian GNU/Linux 1.3.1 with a 2.0.29 kernel. Netatalk is
from the Debian package version 1.4b2-4. I have a sneaking suspicion
this could be happening only with the Debian netatalk package, in which
case I can take the matter up with the Debian netatalk package person.
If anyone *doesn't* have this problem with the netatalk 1.4b2-4 Debian
package, or *does* have this problem *not* on Debian, please speak up.
In the meantime, I too am in rtfm and search mode.
Tim.
-- Tim Bell .--_|\ bhat@cs.mu.oz.au / \ Department of Computer Science \_.--._/ University of Melbourne, Australia v
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:25:48 EST