Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <21433144.post@talk.nabble.com>
Date: Tue, 13 Jan 2009 02:49:26 -0800 (PST)
From: eros <eros.zanchetta@gmail.com>
To: user@geronimo.apache.org
Subject: Re: Startup time delay in Ubuntu server
In-Reply-To: <4B2AAEFD-5538-4184-AFE8-0B988F00EF3B@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <f2516fb30901051526l6805c162n90f6169616e0f607@mail.gmail.com>
 <4963602A.4010201@apache.org>
 <f2516fb30901061219s39a4f512j2108ac8f94098312@mail.gmail.com>
 <4963F521.6020409@gmail.com> <21420457.post@talk.nabble.com>
 <4B2AAEFD-5538-4184-AFE8-0B988F00EF3B@gmail.com>


> I think you have a problem with system entropy that's causing a  
> problem generating pseudo-random numbers.
> 
> While the server startup was stalled, I sent a kill -3 signal to the  
> server process (think I mentioned doing this earlier in this thread)  
> and got the following thread stack:

Yep that's it!

I tried the kill -3 thingy (didn't know about it, thanks!) and got the a
stack trace just like yours. Having the server do some expensive
calculations while tomcat starts up seems to improve the situation a bit
(probably because this activity generates entropy).

The thing that really does the trick is:

mv /dev/random /dev/random.bak
mv /dev/urandom dev/random

even if I don't particularly like the security implications of this.

The problem seems to be working on underused servers and is apparently more
debian-related (see
http://n0tablog.wordpress.com/2007/11/24/running-out-of-entropy-in-debian-etch/)
than geronimo-related.
-- 
View this message in context: http://www.nabble.com/Startup-time-delay-in-Ubuntu-server-tp21301711s134p21433144.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.