Date: Mon, 8 Apr 1996 11:41:13 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: adf@cafu.fl.net.au (Andrew Foster) Cc: freebsd-bugs@freebsd.org, cinder@cafu.fl.net.au Subject: Re: Machines locking Message-ID: <199604080941.LAA04290@uriah.heep.sax.de> In-Reply-To: <Pine.BSF.3.91.960408121643.13249A-100000@cafu.fl.net.au> from "Andrew Foster" at Apr 8, 96 12:22:45 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Andrew Foster wrote: > I've observed this on several machines : > > A lockup in which : > > - pings return > - some programs will still work via opening a socket (e.g. telnetting to > port 80 will sometimes work, but not always) > - I can telnet in (no connection refused) but nothing will happen > - I can switch vtys at the console > - Pressing enter at the console login prompt will redisplay the banner > - Entering a username and pressing enter will do nothing - the machine just > sits there > - The only way to fix it is to press reset Out of mbufs? I think it's the same appearance. Try options "NMBCLUSTERS=2048" in your config file. > - My syslog.conf mentions a file which doesn't exist - as a result when I > press C-A-D I see a syslogd error - so the machine tries to respawn > something (this is my guess) but can't. This is unrelated. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604080941.LAA04290>