Date: Wed, 18 Jul 2001 23:09:16 -0400 From: David Hill <david@phobia.ms> To: Noah Dunker <ndunker@jccc.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: microuptime problem Message-ID: <20010718230916.1fdd0001.david@phobia.ms> In-Reply-To: <C18E28011272D41180AD00B0D0496C0801C021D7@ns-exch05> References: <C18E28011272D41180AD00B0D0496C0801C021D7@ns-exch05>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Jul 2001 22:04:46 -0500 Noah Dunker <ndunker@jccc.net> wrote: > hey - I found info on this bug in some REALLY archaic FreeBSD list postings. > > I was wondering if you ever found out what causes the Microuptime went > backwards bug. I have built a firewall for an acquaintance of mine, and it > seems that just recently his firewall stopped working after an indefinite > period of time, usually between 5 and 20 minutes. From what I can tell the > machine is dealocked. Kaput. > > It's a headless unit running FreeBSD 4.0-RELEASE on a compaq proliant (old, > 486 DX/66, genuine intel processor) > > I have zero physical access to this host. It's a good 400 miles away from > me. As a last resort, I am messing with the idea of dropping 4.3-RELEASE on > a hard drive and shipping it to him, but it could take days, and I hate to > see him rebooting his system > > There are other strange things happening in the logs as well. What I have: > > FreeBSD 4.0-Release > Custom Kernel configuration (kernel config file available upon request) > Caching DNS Server (Bind, whatever shipped with FBSD4.0) > isc-dhcpd on internal interface (ep1) > dhclient on external interface (ep0) > apache (whatever version shipped with FBSD4.0) > > I'm getting logs from dhcpd that seem to indicate it's not happy about the > DNS configuration, > and a "microuptime() went backwards" error, usually is the last thing before > the first boot up messages. > > I can attach anything you guys need to help me out on this one. I've messed > with FreeBSD for almost 3 years now, and I've never had a problem with it > locking up, crashing, or anything. I've been messing with scripts, logs, > daemons, and whatnot for about 3 days with no luck and I've gotten no > further on solving this problem. Any takers? > > Noah Dunker > Systems Analyst/Technician > Johnson County Community College > > I believe its something in the APM support. If you recompile your kernel without it, it should work. - David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010718230916.1fdd0001.david>