Jie Gao wrote:
SunOS banquo 5.9 Generic_112233-11 sun4u sparc

Apache/2.0.48 mod_perl/1.99_13-dev Perl/v5.8.3 (threaded)

Make test fails:

% gmake test
...
[warning] root mode: changing the files ownership to 'nobody' (60001:60001)
[warning] testing whether 'nobody' is able to -rwx /u0/local/src/mod_perl-1.99_13-dev/t
/usr/local/perl-5.8.3_threaded/bin/perl 
-Mlib=/u0/local/src/mod_perl-1.99_13-dev/Apache-Test/lib
-MApache::TestRun -e 'eval { Apache::TestRun::run_root_fs_test(60001, 60001,
q[/u0/local/src/mod_perl-1.99_13-dev/t]) }';


[warning] result: OK /usr/local/apache_2.0.48/bin/httpd -d /u0/local/src/mod_perl-1.99_13-dev/t -f /u0/local/src/mod_perl-1.99_13-dev/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS using Apache/2.0.48 (worker MPM)

waiting 300 seconds for server to start: .....[Sat Mar 06 15:12:30 2004] [info] 27 
Apache:: modules loaded
[Sat Mar 06 15:12:30 2004] [info] 5 APR:: modules loaded
[Sat Mar 06 15:12:30 2004] [info] base server + 16 vhosts ready to run tests
..(126)Cannot assign requested address: make_sock: could not bind to address [::1]:8549
no listening sockets available, shutting down
Unable to open logs

Are you sure you aren't already running mod_perl at ports 8529 and 8549? Do:


ps auxc | grep httpd

and kill any running httpd processes (of course not productional ones ;) It starts at 8549, after finding the port 8529 busy.

I also assume that you are running on ipv6, because of [::1]:8549

I should have reminded that any problem reports must follow the guidelines from: http://perl.apache.org/bugs/

Thanks!

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to