This is a discussion on RE: 'make test' fails with "the server is down, giving up after 121 secs" - modperl ; This might not be any help, but the one time that i ran into this it was = because for some reason traffic to localhost was being blocked by = iptables due to a configuration oversight. You might want to ...
This might not be any help, but the one time that i ran into this it was =
because for some reason traffic to localhost was being blocked by =
iptables due to a configuration oversight. You might want to check to =
make sure that isn't happening to you.=20
From: Colvin, Joshua [mailto:email@example.com]=20
Sent: Thursday, October 18, 2007 10:07 AM
Subject: RE: 'make test' fails with "the server is down, giving up after =
Thanks for the reply Malcolm. I didn't see anything in error_log that
gave me any clues. I've posted the entire contents of error_log in the
original posting (unless there's another error_log I should be looking
We do have ssl configured, but currently disabled:
[root@oomweb conf.d]# ls -l /etc/httpd/conf.d/ssl*
-rw-r--r-- 1 root root 10919 Dec 15 2005 /etc/httpd/conf.d/ssl.conf
-rw-r--r-- 1 root root 10919 Aug 31 2005 =
however the entropy seems okay regardless:
[root@oomweb bugzilla-3]# more /proc/sys/kernel/random/entropy_avail=20
Do you think it's as simple as hacking the test to wait for longer than
From: Malcolm =
Sent: Thursday, October 18, 2007 9:54 AM
Subject: Re: 'make test' fails with "the server is down, giving up after =
On Thursday 18 October 2007 9:47:31 am Colvin, Joshua wrote:
> Hello all,
> I am trying to upgrade bugzilla from 2.22 to 3.0.2 on 32-bit RHEL4, =
> this means upgrading mod_perl from 1.99_16 to 2.0.03 via CPAN.
> Unfortunately the 'make test' fails, saying:
> the server is down, giving up after 121 secs
> [=A0 error] failed to start server! (please examine t/logs/error_log)
Was there nothing useful in the error_log?
> httpd is up and running when the above is output. It does not fail on =
> specific test number according to the error_log and I don't see any =
> msgs in the error_log. I've made sure httpd is stopped before doing =
> upgrade, otherwise I always get a:
> Below is the console output for everything I did, minus the lengthy =
> that didn't seem relevant. Any ideas?
Do you have ssl configured? One thing I've noticed is that if you do, =
you're restarting apache a lot (as happens when you're testing) then =
very easy to run out of entropy for the random number generator, at =
point apache will hang on start until the system gains enough entropy.
On a linux box, check:
You need numbers over 50 for apache/ssl to be happy, in the hundreds is=20
better, single digit means you're stuck.
Solutions include less random random sources, entropy generator sources=20
and "cat /var/logs/* > /dev/null" (the quick and dirty method if you =
need it occasionally).