Subject: Re: [netatalk-admins] netatalk problem on solaris 2.5.1
From: Quay Ly (quay@turing.cs.hmc.edu)
Date: Wed Jul 23 1997 - 18:03:58 EDT
On Tue, 22 Jul 1997, Bill Studenmund wrote:
> On Tue, 22 Jul 1997, Quay Ly wrote:
>
> > Hello. For some reason, the atalkd daemon would die every so often on my
> > solaris box. Here's a clip of the messages/log that atalkd dumps:
> >
> > ---
> > Jul 22 02:29:18 church atalkd[180]: route: 31810 -> 1221.104: No such file
> > or directory
> > Jul 22 02:29:18 church atalkd[180]: route: 31811 -> 1221.104: No such file
> > or directory
> > Jul 22 02:32:42 church atalkd[180]: rtmp_packet: can't remove loopback: No
> > such file or directory
> > Jul 22 02:32:45 church atalkd[180]: looproute panic two routes
> > ---
> >
> > Do anyone have any idea why this happens or how do I go about fixing this?
> > The logs said "No such file or directory", what file or directory are they
> > talking about?
>
> I'm not positive, but I think atalkd is trying to contact the router
> involved in a link, and failing. Which is weird as atalkd is supposed to
> be the router involved. :-) Or a routing socket has been opened to a
> now-defunct routing process, and there's a problem getting the changes to
> propogate.
According to the log, it said that it's trying to contact 1221:104.
I did a nbplkup and got the following information about 1221.104
Banshee.ATM1/0.5:ciscoRouter 1221.104:254
Banshee:SNMP Agent 1221.104:8
Does anyone know why is it going out to the router/snmp agent?
-quay
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:25:47 EST