RE: FreeBSD 6.2-REL, system lockup, recovers when keyboard pressed
Sorry for the top post. Over the year's I've had a few boxes that did stuff like this. Putting the same software packages on a different PC that had a different motherboard and cards in it resulted in no lockups. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dale Shaw Sent: Wednesday, March 12, 2008 6:52 PM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 6.2-REL, system lockup, recovers when keyboard pressed Hi again all, Just an update on my problem (see below). I upgraded the box to 6.3-REL and the problem persisted -- exactly the same behaviour. I've narrowed the problem down to nfdump though -- without the NetFlow collectors (nfcapd) running, the box is rock solid. If anyone out there happens to have seen this problem (with nfdump and friends) before, or has some general advice for troubleshooting something like this (I suspect some system resource tuning may be required), please drop me a line. In the meantime, I'll head on over to the nfdump list. cheers, Dale On Thu, Feb 28, 2008 at 10:57 PM, Kris Kennaway [EMAIL PROTECTED] wrote: Dale Shaw wrote: Hi all, [...] I have a vanilla 6.2-RELEASE system running a bunch of network management type tools like RANCID, nfcapd, cacti and so on. After a few days of normal operation, the system (locked away in a data centre) falls off the network. Can't SSH to it, can't ping it. No ARP -- gone! I have no OOB access to this machine (it's a test box/play pen). I have a vague memory of something like this but cannot point to a specific commit that resolved it. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-REL, system lockup, recovers when keyboard pressed
Hi again all, Just an update on my problem (see below). I upgraded the box to 6.3-REL and the problem persisted -- exactly the same behaviour. I've narrowed the problem down to nfdump though -- without the NetFlow collectors (nfcapd) running, the box is rock solid. If anyone out there happens to have seen this problem (with nfdump and friends) before, or has some general advice for troubleshooting something like this (I suspect some system resource tuning may be required), please drop me a line. In the meantime, I'll head on over to the nfdump list. cheers, Dale On Thu, Feb 28, 2008 at 10:57 PM, Kris Kennaway [EMAIL PROTECTED] wrote: Dale Shaw wrote: Hi all, [...] I have a vanilla 6.2-RELEASE system running a bunch of network management type tools like RANCID, nfcapd, cacti and so on. After a few days of normal operation, the system (locked away in a data centre) falls off the network. Can't SSH to it, can't ping it. No ARP -- gone! I have no OOB access to this machine (it's a test box/play pen). I have a vague memory of something like this but cannot point to a specific commit that resolved it. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-REL, system lockup, recovers when keyboard pressed
Sorry all, I typo'd -- the system is 6.2-REL, not 6.0-REL. Does that make the answer any clearer? (maybe it's fresher in people's minds?) Is confidence high that an update to 6.2-STABLE would sort this out? (I'd really love a bug fix reference). cheers, Dale On Thu, Feb 28, 2008 at 10:57 PM, Kris Kennaway [EMAIL PROTECTED] wrote: Dale Shaw wrote: Hi all, [...] I have a vanilla 6.2-RELEASE system running a bunch of network management type tools like RANCID, nfcapd, cacti and so on. After a few days of normal operation, the system (locked away in a data centre) falls off the network. Can't SSH to it, can't ping it. No ARP -- gone! I have no OOB access to this machine (it's a test box/play pen). I have a vague memory of something like this but cannot point to a specific commit that resolved it. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 6.2-REL, system lockup, recovers when keyboard pressed
You look at upgrading to 6.3-REL or 7.0-REL? -Sean Date: Fri, 29 Feb 2008 08:47:18 +1100 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: freebsd-questions@freebsd.org Subject: Re: FreeBSD 6.2-REL, system lockup, recovers when keyboard pressed Sorry all, I typo'd -- the system is 6.2-REL, not 6.0-REL. Does that make the answer any clearer? (maybe it's fresher in people's minds?) Is confidence high that an update to 6.2-STABLE would sort this out? (I'd really love a bug fix reference). cheers, Dale On Thu, Feb 28, 2008 at 10:57 PM, Kris Kennaway [EMAIL PROTECTED] wrote: Dale Shaw wrote: Hi all, [...] I have a vanilla 6.2-RELEASE system running a bunch of network management type tools like RANCID, nfcapd, cacti and so on. After a few days of normal operation, the system (locked away in a data centre) falls off the network. Can't SSH to it, can't ping it. No ARP -- gone! I have no OOB access to this machine (it's a test box/play pen). I have a vague memory of something like this but cannot point to a specific commit that resolved it. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] _ Connect and share in new ways with Windows Live. http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-REL, system lockup, recovers when keyboard pressed
Hi Sean, On Fri, Feb 29, 2008 at 8:57 AM, Sean Cavanaugh [EMAIL PROTECTED] wrote: You look at upgrading to 6.3-REL or 7.0-REL? Well, I could, but that's a sledgehammer approach and while likely to work, in the absence of a bug report/fix (I'm not saying there isn't one), it is not guaranteed to work. For example, it might be freezing up because of something I can control with configuration (loader.conf stuff). I'll have to stop the processes for a while and see if I can reproduce the behaviour while the system is essentially idle. I'm certainly willing to upgrade but it would be good to go into that process with more confidence of success. cheers, Dale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
