Re: Error running apache test

2004-06-23 Thread Abhishek Khandelwal
I think you misunderstood the problem.

I did not build single binary. I seperately build binaries on Red-hat
and Fedora machines. i.e I build httpd on two different machine one
running Red-hat and one running Fedora core 1.

Moreover, I am running Red-hat 9

Its some kind of library incompatibility of httpd and red-hat.

Any ideas?

Abhishek

On Wed, 2004-06-23 at 01:03, Joe Orton wrote:
> On Tue, Jun 22, 2004 at 06:08:17PM -0700, Abhishek Khandelwal wrote:
> > I am getting another strange problem.
> > I compile and install apache 2.0.49 for both fedora core 1 and red-hat
> > linux.
> > 
> > Everything seems okay, and installs properly.
> > When I start httpd manually, it start running and when I do wget using
> > http://localhost It works fine in both the machines.
> > 
> > But, when I run the test provided my perl-test-framework. And try to run
> > the server using t/TEST -httpd-start, the server starts perfectly on
> > Fedora core but it dies immediately with exit code 255 on Red-hat
> > machine.
> 
> The httpd binary you built on Fedora Core 1 will not work correctly
> out-of-the-box on Red Hat Linux 8.0 and earlier.  If you want to build a
> single binary which works correctly across a set of distributions, build
> it on the *oldest* target distribution, not the newest.
> 
> joe



Re: Error running apache test

2004-06-23 Thread Abhishek Khandelwal
I changed original ssl.conf
to the SSLMutex default as shown below.

> #   Semaphore:
> #   Configure the path to the mutual exclusion semaphore the
> #   SSL engine uses internally for inter-process synchronization.
> #SSLMutex  file:/opt/oss/var/apache2/run/ssl_mutex
> SSLMutex default
> 

Then I rebuild the test and try to run the test.
But still my error log shows SSLMutex not created error.





On Tue, 2004-06-22 at 20:20, Randy Kobes wrote:
> On Tue, 22 Jun 2004, Abhishek Khandelwal wrote:
> 
> > Where exactly I put this?
> >
> > In the conf file generated by test, which is in t/conf/httpd.conf
> >
> > or even before compiling and building test, I change the original
> > httpd.conf?
> 
> Try changing the original first - I think Apache-Test should
> pick up this setting.
> 
> > Also, where exactly do I put this SSLMutex default?
> 
> When installing Apache, assuming a fresh install, this
> directive probably appears somewhere in a sample ssl
> configuration file.



Re: Error running apache test

2004-06-23 Thread Abhishek Khandelwal
Where exactly I put this?

In the conf file generated by test, which is in t/conf/httpd.conf

or even before compiling and building test, I change the original
httpd.conf?

Also, where exactly do I put this SSLMutex default?

Abhishek

On Tue, 2004-06-22 at 19:47, Randy Kobes wrote:
> On Tue, 22 Jun 2004, Abhishek Khandelwal wrote:
> 
> > I am getting another strange problem.
> > I compile and install apache 2.0.49 for both fedora core 1 and red-hat
> > linux.
> >
> > Everything seems okay, and installs properly.
> > When I start httpd manually, it start running and when I do wget using
> > http://localhost It works fine in both the machines.
> >
> > But, when I run the test provided my perl-test-framework. And try to run
> > the server using t/TEST -httpd-start, the server starts perfectly on
> > Fedora core but it dies immediately with exit code 255 on Red-hat
> > machine.
> >
> > Looking at the error log, in t/log/error_log directory, I see the error:
> > [error] (38)Function not implemented: Cannot create SSLMutex
> 
> In the ssl portion of your system httpd.conf, if the
> SSLMutex directive is not given as
>SSLMutex default
> does changing it to that help?



Error running apache test

2004-06-23 Thread Abhishek Khandelwal
I am getting another strange problem.
I compile and install apache 2.0.49 for both fedora core 1 and red-hat
linux.

Everything seems okay, and installs properly.
When I start httpd manually, it start running and when I do wget using
http://localhost It works fine in both the machines.

But, when I run the test provided my perl-test-framework. And try to run
the server using t/TEST -httpd-start, the server starts perfectly on
Fedora core but it dies immediately with exit code 255 on Red-hat
machine.

Looking at the error log, in t/log/error_log directory, I see the error:
[error] (38)Function not implemented: Cannot create SSLMutex


Here is the complete error log:
---
[Tue Jun 22 17:43:02 2004] [info] Init: Initializing OpenSSL library
[Tue Jun 22 17:43:02 2004] [info] Init: Seeding PRNG with 136 bytes of
entropy
[Tue Jun 22 17:43:02 2004] [info] Loading certificate & private key of
SSL-aware server
[Tue Jun 22 17:43:02 2004] [debug] ssl_engine_pphrase.c(468):
unencrypted RSA private key - pass phrase not required
[Tue Jun 22 17:43:02 2004] [info] Loading certificate & private key of
SSL-aware server
[Tue Jun 22 17:43:02 2004] [debug] ssl_engine_pphrase.c(468):
unencrypted RSA private key - pass phrase not required
[Tue Jun 22 17:43:02 2004] [info] Init: Generating temporary RSA private
keys (512/1024 bits)
[Tue Jun 22 17:43:02 2004] [info] Init: Generating temporary DH
parameters (512/1024 bits)
[Tue Jun 22 17:43:02 2004] [error] (38)Function not implemented: Cannot
create SSLMutex



Ideas???

Abhishek




Apache-httpd -Test coverage

2004-05-08 Thread Abhishek Khandelwal
Hi,

I am trying to find out the code-coverage for httpd using the
perl-testframework.

I am trying to use Rational's PureCoverage tool to do that.
One of the requirements for Purecoverage tool is to insert purecov
before CC(cc or gcc) in makefile.

Does anyone have idea, how to insert purecov before cc in makefile?

Since the makefile of httpd is automatically generated using configure
script, it has to be done automatically.

I tried to pass CC="purecov gcc" to the configure, but it inserts
purecov everywhere and purecov tries to instrument .a and .so files as
well, which should not be done at compile time.

Anyone has any idea about how to proceed, please let me know.

Thanks,
Abhishek 





Re: httpd test (perl-framework)

2004-04-15 Thread Abhishek Khandelwal


On Thu, 2004-04-15 at 12:48, Stas Bekman wrote:
> Abhishek Khandelwal wrote:
> > On Thu, 2004-04-15 at 12:19, Stas Bekman wrote:
> > 
> >>Abhishek Khandelwal wrote:
> >>
> >>>I dont see any difference in two files.
> >>>
> >>>I runt the test twice to do a test coverage analysis.
> >>>At first, I install and test apache without test coverage
> >>>and then I again install and test with test-coverage enabled.
> >>>Second time, I get this error.
> >>
> >>Aha, you should have mentioned that in first place. In which case that's 
> >>your 
> >>problem. With test-coverage enabled you don't get mod_access loaded. I 
> >>don't 
> >>know why. Not an Apache-Test problem I think.
> > 
> > 
> > No, it is not related to code coverage. Since, I can run the test with
> > code coverage many a times. As I said, it occurs randomly without any
> > set pattern. So I dont know what exactly is causing this. 
> > And this problem occurs even when I have not enabled code coverage. 
> > The work around solution I got is I clean the test with t/TEST -clean,
> > remove the Makefile from test/perl-framework and the rebuild the test
> > with perl Makefile.PL option. When I do that, everythign goes smoothly.
> > 
> > The problem lies somewhere else.
> 
> Are you absolutely sure that the config doesn't change? Please do the real 
> check with diff on the whole t/conf directory if you didn't yet.


I see no difference in the config file. 

> 
> > What exactly is sticky configuration?
> 
> perldoc Apache::TestRun
> 
> and scroll to:
> 
> Persistent Custom Configuration
> 
> Please do this testing for me:
> 
> >>I doubt it has something to do with sticky configuration, but give it a try 
> >>and try to run with:
> >>
> >>APACHE_TEST_NO_STICKY_PREFERENCES=1 make test

I will do this test, but as I said, it is no confirmation that problem
is gone since it happens randomly. As I just ran the tests again without
any changes and it did run properly, both with and without coverage.

> 
> __
> Stas BekmanJAm_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



Re: httpd test (perl-framework)

2004-04-15 Thread Abhishek Khandelwal
On Thu, 2004-04-15 at 12:19, Stas Bekman wrote:
> Abhishek Khandelwal wrote:
> > I dont see any difference in two files.
> > 
> > I runt the test twice to do a test coverage analysis.
> > At first, I install and test apache without test coverage
> > and then I again install and test with test-coverage enabled.
> > Second time, I get this error.
> 
> Aha, you should have mentioned that in first place. In which case that's your 
> problem. With test-coverage enabled you don't get mod_access loaded. I don't 
> know why. Not an Apache-Test problem I think.

No, it is not related to code coverage. Since, I can run the test with
code coverage many a times. As I said, it occurs randomly without any
set pattern. So I dont know what exactly is causing this. 
And this problem occurs even when I have not enabled code coverage. 
The work around solution I got is I clean the test with t/TEST -clean,
remove the Makefile from test/perl-framework and the rebuild the test
with perl Makefile.PL option. When I do that, everythign goes smoothly.

The problem lies somewhere else.

What exactly is sticky configuration?

> 
> > Moreover, this is just not doing with test-coverage.
> > It happens quite often and without any predictablility.
> > I am not sure how to reproduce it. Because it may or may not give me
> > this error.
> 
> We need to be able to reproduce it in order to fix it. If we can't we can't 
> fix it, since we don't know what the problem is.
> 
> I doubt it has something to do with sticky configuration, but give it a try 
> and try to run with:
> 
> APACHE_TEST_NO_STICKY_PREFERENCES=1 make test
> 
> __
> Stas BekmanJAm_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



Re: httpd test (perl-framework)

2004-04-15 Thread Abhishek Khandelwal
I dont see any difference in two files.

I runt the test twice to do a test coverage analysis.
At first, I install and test apache without test coverage
and then I again install and test with test-coverage enabled.
Second time, I get this error.

Moreover, this is just not doing with test-coverage.
It happens quite often and without any predictablility.
I am not sure how to reproduce it. Because it may or may not give me
this error.

Abhishek

On Thu, 2004-04-15 at 11:47, Stas Bekman wrote:
> [dropping the irrelevant CC address]
> 
> Abhishek Khandelwal wrote:
> > I am getting the following error when I run the perl-test framework.
> > I get this error when I run the test twice, one after another.
> > The first time, it goes thru properly and prints the summary of the
> > results.
> > But When I run for the second time, I get this error. I am using same
> > extra.conf in both the runs, but in second run, it fails. 
> > Anyone has any idea about what might be the reason for the error.
> > 
> > This is the error:::
> 
> > waiting 60 seconds for server to start: .Syntax error on line 16 of
> > /usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t/conf/extra.conf:
> > Invalid command 'Order', perhaps mis-spelled or defined by a module not 
> > included in the server configuration
> 
> Abhishek, the directive Order needs mod_access to be loaded. Is your server 
> built with mod_access built in or as a shared object?
> 
> What do you mean by running the test twice? Like so:
> 
> make test
> make test
> 
> In which case, save away t/conf after the first 'make test' and then when the 
> second time it fails compare the two directories (diff -ru t/conf.old 
> t/conf). 
> Do you see any difference?
> 
> __
> Stas BekmanJAm_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



httpd test (perl-framework)

2004-04-15 Thread Abhishek Khandelwal
I am getting the following error when I run the perl-test framework.
I get this error when I run the test twice, one after another.
The first time, it goes thru properly and prints the summary of the
results.
But When I run for the second time, I get this error. I am using same
extra.conf in both the runs, but in second run, it fails. 
Anyone has any idea about what might be the reason for the error.

This is the error:::


Manifying ../../blib/man3/HTTP::Date.3pm
Manifying ../../blib/man3/LWP::RobotUA.3pm
make[2]: Leaving directory 
`/usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/httpd-test-bundle-0.02/libwww-perl-5.76'
make[1]: Leaving directory 
`/usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/httpd-test-bundle-0.02'
Manifying blib/man3/Apache::TestConfigData.3pm
/opt/dev/apache/httpd/bin/httpd -d 
/usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t -f 
/usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t/conf/httpd.conf
 -DAPACHE2 -DPERL_USEITHREADS
using Apache/2.0.48 (prefork MPM)

waiting 60 seconds for server to start: .Syntax error on line 16 of
/usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t/conf/extra.conf:
Invalid command 'Order', perhaps mis-spelled or defined by a module not 
included in the server configuration
!!! 
server has died with status 255 (please examine t/logs/error_log)




Thanks,
Abhishek



Re: test-perl-framework test fails for apache 2.0

2004-04-09 Thread Abhishek Khandelwal
I have that installed and version is 5.76
I guess its part of module libwww-perl-5.76

Any other idea what the problem might be?

On Thu, 2004-04-08 at 18:16, Stas Bekman wrote:
> Abhishek Khandelwal wrote:
> > I am not sure about it?
> > How do I check whether its installed or not?
> 
> perl -MLWP -le 'print LWP->VERSION'
> 
> > In case it is not installed how do I install?
> > would be from CPAN.. install LWP?
> 
> yup



Re: test-perl-framework test fails for apache 2.0

2004-04-09 Thread Abhishek Khandelwal
I am not sure about it?
How do I check whether its installed or not?
In case it is not installed how do I install?
would be from CPAN.. install LWP?

Thanks

On Thu, 2004-04-08 at 17:56, Stas Bekman wrote:
> Abhishek Khandelwal wrote:
> > Hi Stas,
> > 
> > I installed apache httpd and the usual Apache::TestBundle.
> > Finally when I run the tests, I get this error in ssl/http.t module
> > 
> > Anyone has idea about what might be missing in the configuration or is
> > it a bug in apache 2.0?
> > 
> > This is the error I get::
> > 
> > ---
> > 
> > ssl/http.response had protocol HTTP/0.9 (headers not
> > sent?) at ssl/http.t line 27
> > dubious
> > Test returned status 255 (wstat 65280, 0xff00)
> > Scalar found where operator expected at (eval 170) line 1, near "'int' 
> > $__val"
> > DIED. FAILED tests 1-2
> > Failed 2/2 tests, 0.00% okay
> > (Missing operator before   $__val?)
> > 
> > --
> 
> May be you don't have LWP installed?
> 



test-perl-framework test fails for apache 2.0

2004-04-09 Thread Abhishek Khandelwal
Hi Stas,

I installed apache httpd and the usual Apache::TestBundle.
Finally when I run the tests, I get this error in ssl/http.t module

Anyone has idea about what might be missing in the configuration or is
it a bug in apache 2.0?

This is the error I get::

---

ssl/http.response had protocol HTTP/0.9 (headers not
sent?) at ssl/http.t line 27
dubious
Test returned status 255 (wstat 65280, 0xff00)
Scalar found where operator expected at (eval 170) line 1, near "'int' 
$__val"
DIED. FAILED tests 1-2
Failed 2/2 tests, 0.00% okay
(Missing operator before   $__val?)

--

Please help

Abhishek



Apache test -- Perl-test-framework

2004-04-02 Thread Abhishek Khandelwal
Is there a way to count the total number of tests when the perl-test
suits are run.
If all the tests passes, then in final report it specifies the total
number of files and total number of tests run. But in case there are
tests which fails, it publishes a report which looks like as follows:

--
Failed Test   Stat Wstat Total Fail  Failed  List of Failed
---
modules/cgi.t   50   21  42.00%  14 16 24 26 28 30 32 34 36 38-
 41 43-50
modules/include.t   826   7.32%  11 27 39 41-42 65
ssl/http.t 255 65280 24 200.00%  1-2
ssl/proxy.t1692   1.18%  114 117
2 tests and 14 subtests skipped.
!!! error running tests (please examine t/logs/error_log)

--

Now I dont have any way to know how many total tests were run as the report 
only shows the results of failed tests.

Does anyone know a way to do it. My guess is, I can somehow instrument 
Apache::Test or Apache::TestRequest etc to get the total count.

Please help.

Thanks,
Abhishek



apache -Perl Test framework

2004-04-01 Thread Abhishek Khandelwal
Hi,
Is anyone working on Perl framework to test Apache httpd.
We are working on different open source component and trying to
integrate them.
I am looking in to the perl-framework provided to test the apache 2.1
Have someone used it? Are you getting the 100% passing of all the tests?
In my case, some of the test cases are failing for no apparent reason.
Let me know what do you think guys!!

Thanks,
Abhishek