Loading ...
Sorry, an error occurred while loading the content.
 

Re: make test failed on solaris 8

Expand Messages
  • Tulan W. Hu
    1) Don t worry about the t/TEST -verbose t/apr/util.t anymore. The problem went away after I removed all RC4 and rebuilt it. don t really know what had
    Message 1 of 21 , Feb 2, 2005
      1) Don't worry about the t/TEST -verbose t/apr/util.t anymore.
      The problem went away after I removed all RC4 and rebuilt it.
      don't really know what had happened.

      2) After you mentioned AAA, I thought about our private modules again.
      By default, they use cookie to authenticate instead of userid and passwd.
      Unless the browser is set no cookie accept, the uid/pass will be prompted.
      So that I tend to think that it may not be issues for those failures.
      My question is if I can setup it not to use cookies in the test cases or the
      conf file.

      Our mp1 httpd.conf has
      <directory /www/force/enter/uid/for/this/one>
      AuthCookieName NoCookieUsed
      AuthName "enter uid and password)"
      AuthType BasiC
      <limit GET POST>
      require valid-user
      </limit>
      </directory>

      $ t/TEST -clean
      $ t/TEST -verbose t/protocol/pseudo_http.t
      ====error_log
      END in modperl_extra.pl, pid=2338
      [Wed Feb 02 07:23:35 2005] [notice] Apache/2.0.52 (Unix) world domination
      series
      /2.0 mod_perl/1.999.21 Perl/v5.8.6 configured -- resuming normal operations
      [Wed Feb 02 07:23:35 2005] [info] Server built: Jan 31 2005 15:14:31
      [Wed Feb 02 07:23:35 2005] [debug] prefork.c(955): AcceptMutex: fcntl
      (default:fcntl)
      starting method: run_access_checker
      u/p: stas/foobar
      finished method: run_access_checker
      starting method: run_check_user_id
      starting method: run_access_checker

      *** The following error entry is expected and harmless ***
      u/p: stas/foObaR
      finished method: run_access_checker
      starting method: run_check_user_id
      [Wed Feb 02 07:23:39 2005] [info] Child process pid=2580 is exiting
      [Wed Feb 02 07:23:39 2005] [info] Child process pid=2582 is exiting
      END in modperl_extra.pl, pid=2580
      END in modperl_extra.pl, pid=2582
      [Wed Feb 02 07:23:39 2005] [info] Child process pid=2694 is exiting
      END in modperl_extra.pl, pid=2694
      [Wed Feb 02 07:23:39 2005] [info] removed PID file
      /s5/twh/papache/mod_perl-2.0.0-RC4/t/logs/httpd.pid (pid=2462)
      [Wed Feb 02 07:23:39 2005] [notice] caught SIGTERM, shutting down
      END in modperl_extra.pl, pid=2462
    • Stas Bekman
      ... Cool. ... You mean some AAA bits of your global httpd.conf make it into t/conf/httpd.conf? ... So it fais the run_check_user_id phase, performed by:
      Message 2 of 21 , Feb 2, 2005
        Tulan W. Hu wrote:
        > 1) Don't worry about the t/TEST -verbose t/apr/util.t anymore.
        > The problem went away after I removed all RC4 and rebuilt it.
        > don't really know what had happened.

        Cool.

        > 2) After you mentioned AAA, I thought about our private modules again.
        > By default, they use cookie to authenticate instead of userid and passwd.
        > Unless the browser is set no cookie accept, the uid/pass will be prompted.
        > So that I tend to think that it may not be issues for those failures.
        > My question is if I can setup it not to use cookies in the test cases or the
        > conf file.
        >
        > Our mp1 httpd.conf has
        > <directory /www/force/enter/uid/for/this/one>
        > AuthCookieName NoCookieUsed
        > AuthName "enter uid and password)"
        > AuthType BasiC
        > <limit GET POST>
        > require valid-user
        > </limit>
        > </directory>

        You mean some AAA bits of your global httpd.conf make it into
        t/conf/httpd.conf?

        > $ t/TEST -clean
        > $ t/TEST -verbose t/protocol/pseudo_http.t
        > ====error_log

        > starting method: run_access_checker
        > u/p: stas/foobar
        > finished method: run_access_checker
        > starting method: run_check_user_id

        So it fais the run_check_user_id phase, performed by:
        <IfModule mod_auth.c>
        # htpasswd -mbc basic-auth stas foobar
        # using md5 password so it'll work on win32 too
        AuthUserFile [...]/t/htdocs/protocols/basic-auth
        </IfModule>
        Require user stas

        (see the TestProtocol::pseudo_http entry in t/conf/httpd.conf).
        What's inside that file? Should be:

        stas:$apr1$qnKIk...$TRSGo5zlwo3LMc0R/iLWo/

        see if recreating it with:

        htpasswd -mbc t/htdocs/protocols/basic-auth stas foobar

        makes any difference.

        --
        __________________________________________________________________
        Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
        http://stason.org/ mod_perl Guide ---> http://perl.apache.org
        mailto:stas@... http://use.perl.org http://apacheweek.com
        http://modperlbook.org http://apache.org http://ticketmaster.com
      Your message has been successfully submitted and would be delivered to recipients shortly.