We have two private add on modules that have been converted
from v1.x to v2. I'll check them again.
Tulan
----- Original Message -----
From: "Tulan W. Hu" <[EMAIL PROTECTED]>
To: "Stas Bekman" <[EMAIL PROTECTED]>
Cc: <modperl@perl.apache.org>
Sent: Wednesday, January 26, 2005 7:52 AM
Subject: Re: make test failed on solaris 8
> ---- Original Message -----
> From: "Stas Bekman" <[EMAIL PROTECTED]>
> > Tulan W. Hu wrote:
> >
> > >>I think I need to fix the syntax error in the httpd.conf first.
> > >>however, I cannot just modify the httpd.conf file under t/conf
> > >>since it will be overwrite when I run make test.
> >
> > Run t/TEST instead of 'make test', in which case t/conf/httpd.conf is
> > *not* overwritten. You can do t/TEST -start / t/TEST -stop. But see
below
> > (it's the best to just start httpd manually in this case)
> >
> > >>===========================================
> > >>The line 960 of httpd.conf file:
> > >>
> > >>....cut...
> > >> AuthType Basic
> > >> AuthName "Access"
> > >> Require user goo bar #####this is the line 960
> > >> Require group bar tar
> > >> <Limit POST>
> > >> Require valid-user
> > >> </Limit>
> > >>....cut....
> > >>
> > >>=================================================
> > >>
> > >>$ truss ../httpd -d t -f
> conf/httpd.conf -DAPACHE2 -DONE_PROCESS -DNO_DETATCH
> > >>output:
> > >>....cut....
> > >>Syntax error on line 960 of t/conf/httpd.conf:
> > >>write(2, " S y n t a x e r r o r".., 47) = 47
> > >>require takes 1-2 arguments,
> > >>write(2, " r e q u i r e t a k e".., 30) = 30
> > >>llseek(0, 0, SEEK_CUR) = 184313
> > >>_exit(1)
> >
> > Hmm, Require is a core directive, so it should be there. I don't quite
> > understand why you don't see this error in the normal STDERR output.
what
> > happens when you run the above w/o truss?
>
> I do see the syntax error when I ran make test.
>
> > can you start apache w/o mod_perl (i.e. with a default httpd.conf)? if
> > yes, copy the "Require" parts of section around line 960 into the
default
> > httpd.conf and try again. does it still work?
>
> I think this is odd too. Both 2.0.49 and 2.0.52 show up syntax error for
me
> on "Require user goo bar". (I comment out Load modperl in httpd.conf)
> As it said, the Require only takes 1-2 arguments.
> It seems to be ok if I put a quote for goo and bar.
> Require user 'goo bar' seems to get rid of syntax error.
> FYI - mod_perl 1.99_13dev version that worked for me only has
> "Require valid-user", also it was built with perl 5.8.2 instead of
perl
> 5.8.5.
> However, I still have problem on
>
> $ t/TEST -start # i ran this with Require user 'goo bar' in the httpd.conf
> [warning] Skipping 'set unlimited ulimit for coredumps', since we are
> running as a non-root user on Solaris
> /s5/twh/apache2/bin/httpd -d
> /s5/twh/papache/httpd-2.0.52/mod_perl-2.0.0-RC4/t -f
> /s5/twh/papache/httpd-2.0.52/mod_perl-2.0.0-RC4/t/conf/httpd.conf -D
APACHE2
> using Apache/2.0.49 (prefork MPM)
>
> waiting 120 seconds for server to start: ..[Wed Jan 26 07:31:45 2005]
[info]
> 7 Apache:: modules loaded
> [Wed Jan 26 07:31:45 2005] [info] 0 APR:: modules loaded
> [Wed Jan 26 07:31:45 2005] [info] base server + 27 vhosts ready to run
tests
> ..[Wed Jan 26 07:31:48 2005] [error] Insecure directory in $ENV{PATH}
while
> running with -T switch at
>
/s5/twh/papache/httpd-2.0.52/mod_perl-2.0.0-RC4/Apache-Test/lib/Apache/TestC
> onfig.pm line 1062.\nCompilation failed in require at
> /s5/twh/papache/httpd-2.0.52/mod_perl-2.0.0-RC4/t/conf/modperl_startup.pl
> line 17.\n\t...propagated at
> /s5/twh/papache/httpd-2.0.52/mod_perl-2.0.0-RC4/t/conf/modperl_startup.pl
> line 18.\nBEGIN failed--compilation aborted at
> /s5/twh/papache/httpd-2.0.52/mod_perl-2.0.0-RC4/t/conf/modperl_startup.pl
> line 20.\nCompilation failed in require at (eval 2) line 1.\n
> [Wed Jan 26 07:31:48 2005] [error] Can't load Perl file:
> /s5/twh/papache/httpd-2.0.52/mod_perl-2.0.0-RC4/t/conf/modperl_startup.pl
> for server localhost:8529, exiting...
>
............................................................................
> ..........................................
> waiting 120 seconds for server to start: not ok
> [ error] giving up after 121 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. 420) and repeat the last command.
>
> [ error] server failed to start! (t/logs/error_log wasn't created, start
> the server in the debug mode)
>
>
>
