Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Sep 2001 13:56:03 -0700
From:      Tony Saign <tony@saign.com>
To:        "'john'" <johng@musicman.com>
Cc:        <freebsd-isp@FreeBSD.ORG>
Subject:   RE: Server Freezup 
Message-ID:  <000001c13a3b$01a3fb90$da0b010a@tsaignmobl>
In-Reply-To: <Pine.BSF.4.21.0109101344460.23620-100000@ren.sasknow.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
I have 4 systems (2 FreeBSD boxes) connected to a Belkin KVM (piece of s***!),
and consoles become inaccessable very frequently!
They are both configured to have COM1 serial consoles though, so I can always
connect either directly using SecureCRT > COM1, or remotely using SSH.

-Tony

* -----Original Message-----
* From: owner-freebsd-isp@FreeBSD.ORG
* [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Ryan Thompson
* Sent: Monday, September 10, 2001 1:02 PM
* To: john
* Cc: freebsd-isp@FreeBSD.ORG
* Subject: Re: Server Freezup
*
*
* john wrote to freebsd-isp@FreeBSD.ORG:
*
* > Hi,
* >
* > I've got a FreeBSD server running Apache that freezes up
* from time to
* > time.  When this happens it does not recognize any keyboard
* input and
* > I have to reboot the computer.
*
* It is likely something hardware related... However, if you use a KVM
* switch (Keyboard/Video/Mouse switch), you may experience
* keyboard lockups.
* (Cheap KVMs don't properly simulate a keyboard signal, and
* the PC keyboard
* interface doesn't always cope well with "hot plugging").
*
* Can you access the machine remotely? (I.e., does it respond
* to ping? Can
* you log in?) Perhaps only the keyboard/console is frozen? If
* you're lucky,
* the rest of the computer is operational, and you can log in and reboot
* remotely, to prevent corruption of your filesystems.
*
* Check your logs (like /var/log/messages) after the fact for any
* interesting information that might have been saved. Also look
* for common
* pre-cursors to freezeups (i.e., does it usually occur during compiles,
* heavy network traffic, etc?)
*
* Turn on kernel debugging (there is a good FreeBSD handbook section on
* this). If the kernel will actually panic, you will get some useful
* information and a core dump.
*
* More general advice would be to check your hardware. Is your
* power supply
* output normal? (under load?), are all your cards/chips firmly
* seated with
* clean contacts? Are all your fans working properly? Is your CPU being
* cooled adequately? (Check for thermal paste between the
* CPU/heatsink--on
* CPUs that have been installed/running for a long time, the paste will
* sometimes break down and start to crumble, which is worse
* than not having
* it at all. It needs to be re-applied periodically for proper cooling).
*
*
* > When I do the reboot it is unable to mount the /usr/home/
* file system,
* > which is on da0 drive.  Then I have to do fsck da0s1h.  When this is
* > done, I can mount /usr/home and do another reboot successfully.
*
* That is normal after a crash/hard boot. It becomes more scary
* on large,
* busy filesystems that have been mounted for months with
* hundreds or more
* unsynced writes at the time of the crash. :-)
*
*
* > My question is, does anyone have any idea why this freezup might be
* > happening?
* >
* > I'd appreciate any assistance.
* >
* > Thanks!
* >
* > John
*
*
* Hope this helps,
* - Ryan
*
*
* --
*   Ryan Thompson <ryan@sasknow.com>
*   Network Administrator, Accounts
*
*   SaskNow Technologies - http://www.sasknow.com
*   #106-380 3120 8th St E - Saskatoon, SK - S7H 0W2
*
*         Tel: 306-664-3600   Fax: 306-664-1161   Saskatoon
*   Toll-Free: 877-727-5669     (877-SASKNOW)     North America
*
*
* To Unsubscribe: send mail to majordomo@FreeBSD.org
* with "unsubscribe freebsd-isp" in the body of the message
*



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?000001c13a3b$01a3fb90$da0b010a>