Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Jun 2005 11:26:06 -0400
From:      Matt Juszczak <matt@atopia.net>
To:        Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
Cc:        Gleb Smirnoff <glebius@freebsd.org>, freebsd-stable@freebsd.org
Subject:   Re: FreeBSD -STABLE servers repeatedly crashing.
Message-ID:  <42C16C0E.9090002@atopia.net>
In-Reply-To: <1119971279.36316.45.camel@buffy.york.ac.uk>
References:  <42BF8815.6090909@atopia.net>	<20050627081933.GA97832@cell.sick.ru> <42C16394.4040904@atopia.net> <1119971279.36316.45.camel@buffy.york.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
Gavin Atkinson wrote:

>On Tue, 2005-06-28 at 10:49 -0400, Matt Juszczak wrote:
>  
>
>>Gleb Smirnoff wrote:
>>
>>    
>>
>>>On Mon, Jun 27, 2005 at 01:01:09AM -0400, Matt Juszczak wrote:
>>>M> About three weeks ago, I upgraded my 5.3-RELEASE boxes to 5.4-RELEASE.  
>>>M> I also turned on procmail globally on our mail server.  Here is our 
>>>M> current FreeBSD server setup:
>>>M> 
>>>M> URANUS  -  primary ldap
>>>M> CALIBAN -  secondary ldap
>>>M> ORION     -  primary mail
>>>M> 
>>>M> Orion was the first one to crash, about three weeks ago.  Orion is 
>>>M> constantly talking to uranus, because uranus is our primary ldap server 
>>>M> (we have a planet scheme), and caliban is our secondary ldap server.  I 
>>>M> ran an email flood test on orion to see if I could crash it again.  This 
>>>M> time, the high requests on Uranus caused Uranus to crash. With two 
>>>M> different servers on two different hardware setups crashing, I had to 
>>>M> start thinking of what could be causing the problem.
>>>M> 
>>>M> http://paste.atopia.net/126
>>>
>>>Can you please build kernel with debugging and obtain a crashdump?
>>>      
>>>
>>Ever since I setup the debug kernel the machine is now crashing every 12 
>>hours.  I think I have to switch to OpenBSD or 4.11 FreeBSD because this 
>>box can't keep crashing.  It  refuses to do a crash dump.
>>    
>>
>
>OK, when it crashes next and is sat at the "db>" prompt, type "tr" and
>press enter to get a trace.  Copy this down (or have a serial console to
>capture the output).  Also, try typing "call doadump()" and see if that
>succeeds in generating a crash dump.  How were you trying to generate
>one before?
>
>Gavin
>  
>

I can't type anything.  The machine locks up.

See: http://paste.atopia.net/126

After CPUID: 1, the machine locks cold and nothing else is printed to 
the screen.

-Matt



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42C16C0E.9090002>