Date: Tue, 23 Dec 1997 22:27:19 +0000 From: Brian Somers <brian@awfulhak.org> To: Kwoody <kwoody@citytel.net> Cc: brian@awfulhak.org, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Kernel messages. Message-ID: <199712232227.WAA15091@awfulhak.demon.co.uk> In-Reply-To: Your message of "Fri, 19 Dec 1997 13:01:07 PST." <Pine.BSF.3.91.971219091842.20204A-100000@mybsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Dec 15 08:01:03 mybsd ppp[11735]: Error: select: Bad file descriptor > Dec 15 23:53:19 mybsd ppp[16264]: Warning: _PATH_ALIAS > (/usr/lib/libalias.so.2.4): Invalid lib: open failed for > "/usr/lib/libalias.so.2.4" : No such file or directory > Dec 15 23:53:19 mybsd ppp[16264]: Warning: Cannot load alias library > > The above showed up in messages after I compiled/installed 971215 of ppp. > Its there but never showed up again in the messages. And whats a bad file > descriptor? I backed up my old PPP stuff, but forgot to backup the lib > files for -alias. Is there going to be a prob with using the 970820 ppp > with the 971215 libalias files? So far there doesnt seem to be. There have been no recent libalias changes. > Dec 16 23:29:40 mybsd /kernel: stray irq 7 > Dec 16 23:29:42 mybsd last message repeated 4 times > Dec 16 23:29:42 mybsd /kernel: too many stray irq 7's; not logging any more > > This happend the first time I managed to get ppp to dial out after > compiling/installing 971215 of ppp. Ive had them before, but only a few. > Never this bad. Hmm, > Dec 17 02:00:23 mybsd /kernel: rtinit: wrong ifa (0xf0923500) was (0xf08a5800) > Dec 17 08:00:21 mybsd ppp[17912]: tun0: Error: SetIpDevice: ioctl(SIOCAIFADDR): > File exists > Dec 17 10:30:43 mybsd /kernel: rtinit: wrong ifa (0xf091e880) was (0xf0821c80) > Dec 17 11:56:55 mybsd ppp[17912]: tun0: Error: SetIpDevice: ioctl(SIOCAIFADDR): > File exists > Dec 17 12:00:48 mybsd ppp[17912]: tun0: Warning: DialModem: dial failed. > > I dont know what this is. I have cron jobs at 0200,(the default system > maint). At 0800, 1200 and 1700 hours cron jobs dial out for mail. None of > them worked but this was what was recorded in /var/log/messages. > What file is being referred to here? tun0.pid? Nope, the ``File exists'' is the text associated with errno EEXIST. In this context it means that there's already an interface with the given (via `set ifaddr') destination address. The `wrong ifa' messages indicate that there's already an interface with the given (via `set ifaddr') source address. > Dec 17 17:00:24 mybsd ppp[18474]: tun0: Error: SetIpDevice: ioctl(SIOCAIFADDR): > File exists > Dec 17 17:41:56 mybsd /kernel: rtinit: wrong ifa (0xf091c180) was (0xf07f9600) > Dec 17 18:12:03 mybsd init: getty repeating too quickly on port /dev/ttyv1, > sleeping 30 secs Are you trying to run ppp from /etc/ttys without the -direct switch ? This won't work as ppp daemonizes itself and init will then try to respawn ppp. The result is loads of ppp processes - all failing to run, and an unstable system that probably runs out of file descriptors among other things. If you want to run ppp from /etc/ttys, use the -direct switch. > At 1800 hours I doing a few things trying to figure out why ppp was not > working correctly, when at 18:12 things froze up on me and all three > vtty's were logged out automatically and I couldnt log back in. I got weird > chars when I tried to log back in. > > I had X running and was able to <alt>-f4 into it and everything was still > running and no other errors had been reported on any of the windows, or > in the messages file. > > PPP was running as a -auto -alias process at this point and it seemed to be > the thing mucking everything up so killed it, switched back to a vtty > and was able to log in again. This sounds as if ppp was using up all the file descriptors. Was there only a single ppp running or was there loads of them (all spawned by init in /etc/ttys) ? Can you reproduce the problem ? > Dialup also screwed up. Seems I had ppp.conf set to 115200, yet I am > using std.38400 for dialup. I guess ppp was overriding the getty cause > after ppp had dialed out I just got garbage when I dialed in. Is that > possible? This is normal. Your modem will lock its DTR at whatever speed was last used. The only way to reset it is to send an `AT' to the modem. Just use std.115200. > Sorry for the long post but I would like to use the newer version of PPP > since it has some nice logging features now that I would like to use. > BTW this is BSD 2.1.7. I updated ppp on Dec 19 so that it exits in -auto mode if the specified interface addresses are already configured. You may want to get the latest version. > Thanks for any insight. > kwoody@citytel.net -- Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org> <http://www.Awfulhak.org> Don't _EVER_ lose your sense of humour....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712232227.WAA15091>