Hi Torsten, I ran make test and it failed with below errors. Also, can you please elaborate how 32bits arcitecture can create issue here.
[soni498@sz1061:NODB mod_perl-2.0.7]$ make test cd "src/modules/perl" && make /usr/bin/perl -Iblib/arch -Iblib/lib \ t/TEST -clean [warning] Skipping 'set unlimited ulimit for coredumps', since we are running as a non-root user on Solaris APACHE_TEST_GROUP= APACHE_TEST_HTTPD= APACHE_TEST_PORT= APACHE_TEST_USER= APACHE_TEST_APXS= \ /usr/bin/perl -Iblib/arch -Iblib/lib \ t/TEST -bugreport -verbose=0 [warning] Skipping 'set unlimited ulimit for coredumps', since we are running as a non-root user on Solaris /usr/httpd2.2.20/httpd/bin/httpd -d /home/soni498/mod_perl-2.0.7/t -f /home/soni498/mod_perl-2.0.7/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS using Apache/2.2.20 (prefork MPM) waiting 300 seconds for server to start: .............................................................................................................................................................................................................................................................................................................. waiting 300 seconds for server to start: not ok [ error] giving up after 301 secs. If you think that your system is slow or overloaded try again with a longer timeout value. by setting the environment variable APACHE_TEST_STARTUP_TIMEOUT to a high value (e.g. 600) and repeat the last command. [ error] server failed to start! (t/logs/error_log wasn't created, start the server in the debug mode) +--------------------------------------------------------+ | Please file a bug report: http://perl.apache.org/bugs/ | +--------------------------------------------------------+ *** Error code 1 make: Fatal error: Command failed for target `run_tests' [soni498@sz1061:NODB mod_perl-2.0.7]$ cd Thanks & Regards, ----------------------------------------------------- Jitendra Soni Accenture, Bangalore INDIA Mailto: jitendra.s...@accenture.com Phone: (+91) 99860 29897 -----Original Message----- From: Torsten Förtsch [mailto:torsten.foert...@gmx.net] Sent: Tuesday, February 05, 2013 6:59 PM To: Soni, Jitendra Cc: modperl@perl.apache.org Subject: Re: [mp2] mod_perl resulting apache failure On 02/05/2013 01:29 PM, jitendra.s...@accenture.com wrote: > 1. Problem Description: > > Apache start is failing after adding mod_perl module in httpd.conf. > I take it you ran "make test" and all tests passed? Then make sure you use the same perl/modperl/httpd combination. Make sure all the paths are correct. On a linux box the best way to do that is to look at /proc/$HTTPD_PID/maps when the modperl test suite is running. Then start your production server without modperl, take the output and compare it with the modperl case. Then you can setup your production server to produce core dumps (ulimit, CoreDumpDirectory). Inspect the core dump with GDB. It lists all shared libraries it loads. It also can generate a stack trace that can help identifying your problem. These recommendations are not very useful in pointing directly to your problem. But given the little information you provide this is all I can do. The only thing I see is that you are using 32 bit architecture. There is a large-file-support related problem there. See: http://www.gossamer-threads.com/lists/modperl/modperl/103514#103514 The patch mentioned at the end of the thread may help. But if that were the case "make test" should have failed. I don't have any 32 bit system here and I don't fully understand the implications of the patch. Torsten This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com
