On Fri, Nov 14, 2008 at 9:48 PM, <[EMAIL PROTECTED]> wrote:
> -8<-- Start Bug Report 8<--
> 1. Problem Description:
>
> Per suggestion made in this forum, I gave up on static build and am building
> dynamic.
> Now I get 2 errors in make test, plus undef erro
-8<-- Start Bug Report 8<--
1. Problem Description:
Per suggestion made in this forum, I gave up on static build and am
building dynamic.
Now I get 2 errors in make test, plus undef errors during 'sudo make
install'
t/hooks/authen_basic1..4
# Runn
David Weekly wrote:
Failed Test Stat Wstat Total Fail Failed List of
Failed
---
t/apache/content_length_header.t 271 3.70% 17
t/api/status.t
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/apache/content_length_header.t 271 3.70% 17
t/api/status.t 62 33.33% 4-5
15 t
At 01:25 AM 2/1/2006 -0800, Stas Bekman wrote:
Bennett Haselton wrote:
[...]
still waiting for server to warm up:
...
the server is down, giving up after 121 secs
[ error] failed to st
Bennett Haselton wrote:
[...]
still waiting for server to warm up:
...
the server is down, giving up after 121 secs
[ error] failed to start server! (please examine t/logs/error_log)
I'm not very familiar with UNIX but I believe I followed the instructions
exactly for installing mod_perl, and I still ran into the problem
below. (Since I'm not used to UNIX though, if you need me to post more
information, please specify as precisely as possible what I should type
since I won
On Wed, Jun 08, 2005 at 12:00:01AM +1000, Stas Bekman wrote:
> Great! William, can you please write a new entry for the troubleshooting
> chapter? With a full diagnosis and the solution? Really it should belong
> to the Apache-Test troubleshooting, but as at the moment it doesn't exist,
> we wil
William McKee wrote:
Stas,
It's been awhile, but I'm back to working on these tests under FreeBSD
5.3 with mp2. I'm using the current release (2.0.0) with Apache 2.0.54.
The root of many of my problems appears to be how Apache is resolving my
localhost address. Apparently FBSD resolves localhost
Stas,
It's been awhile, but I'm back to working on these tests under FreeBSD
5.3 with mp2. I'm using the current release (2.0.0) with Apache 2.0.54.
The root of many of my problems appears to be how Apache is resolving my
localhost address. Apparently FBSD resolves localhost to my Jail IP.
Apache
Joe Orton wrote:
On Fri, Feb 18, 2005 at 05:35:56PM -0500, Stas Bekman wrote:
Joe, shouldn't the APR API emit some kind of errors in the situation like
William has with jail env+ac_cv_o_nonblock_inherited thingy, rather than
silently fail?
The issue is that the configure test couldn't make a dec
On Fri, Feb 18, 2005 at 05:35:56PM -0500, Stas Bekman wrote:
> Joe, shouldn't the APR API emit some kind of errors in the situation like
> William has with jail env+ac_cv_o_nonblock_inherited thingy, rather than
> silently fail?
The issue is that the configure test couldn't make a decision, but
Jie Gao wrote:
Hi Stas,
The documentation at http://perl.apache.org/docs/2.0/api/APR/OS.html
has an inconsistency.
In the example, it seems the method "thread_current" should actually be
"current_thread_id".
Thanks Jie, committed.
--
_
Hi Stas,
The documentation at http://perl.apache.org/docs/2.0/api/APR/OS.html
has an inconsistency.
In the example, it seems the method "thread_current" should actually be
"current_thread_id".
Regard,
Jie
Joe, shouldn't the APR API emit some kind of errors in the situation like
William has with jail env+ac_cv_o_nonblock_inherited thingy, rather than
silently fail?
--
__
Stas BekmanJAm_pH --> Just Another mod_perl Hack
William McKee wrote:
[...]
To recap, these are the results of the mp2 test (RC4) with the following
environment setting:
export ac_cv_o_nonblock_inherited=yes
[...]
# Failed test 2 in t/api/access2.t at line 15
# testing : no credentials passed
# expected: 401
# received: 403
not ok 2
I
On Fri, Feb 18, 2005 at 10:15:19AM -0500, William McKee wrote:
> Actually, I suppose that I could try running the nonblock script first
> to see if that works.
I was able to get my hosting provider to run the nonblock program
outside of a jailed process and it works. We've been trying to figure
ou
On Thu, Feb 17, 2005 at 06:27:15PM -0500, Stas Bekman wrote:
> As for 'Can't open t/conf/perlsection.conf', do
>
> t/TEST -clean
To make a long story short, I had run the make test on the source as
root which caused the t/ directory to have its ownership changed to
nobody. So when I went to run m
On Fri, Feb 18, 2005 at 01:40:44PM +, Joe Orton wrote:
> That confirms that the problem: you got a connect() failure when the
> configure test program attempted to a listener bound to 0.0.0.0
OK.
> You can try the standalone test program here to reproduce the failure:
Yes, that seems to be
On Thu, Feb 17, 2005 at 03:05:31PM -0500, William McKee wrote:
> On Thu, Feb 17, 2005 at 04:53:45PM +, Joe Orton wrote:
> > Check for the result of the:
> >
> > "checking if O_NONBLOCK setting is inherited from listening sockets"
> >
> > test when you run the configure script.
>
> I wasn't s
William McKee wrote:
On Thu, Feb 17, 2005 at 04:53:45PM +, Joe Orton wrote:
Check for the result of the:
"checking if O_NONBLOCK setting is inherited from listening sockets"
test when you run the configure script.
I wasn't sure if you were referring to the mod_perl or Apache configure
script.
William McKee wrote:
On Wed, Feb 16, 2005 at 07:14:24PM -0500, Stas Bekman wrote:
Yes, it is (though keep in mind that this is a virtual server running as
a jailed process, not a separate machine).
That could be the reason.
But if I open a lynx session and surf over to localhost, my server comes
u
On Thu, Feb 17, 2005 at 04:53:45PM +, Joe Orton wrote:
> Check for the result of the:
>
> "checking if O_NONBLOCK setting is inherited from listening sockets"
>
> test when you run the configure script.
I wasn't sure if you were referring to the mod_perl or Apache configure
script. When I ra
On Thu, Feb 17, 2005 at 09:18:31AM -0500, William McKee wrote:
> On Thu, Feb 17, 2005 at 10:39:46AM +, Joe Orton wrote:
> > That was all the non-blocking-vs-blocking stuff. First I'd ask whether
> > or not this fails in a non-chroot environment. A chroot will screw up
> > all kinds of stuff (
On Thu, Feb 17, 2005 at 10:39:46AM +, Joe Orton wrote:
> That was all the non-blocking-vs-blocking stuff. First I'd ask whether
> or not this fails in a non-chroot environment. A chroot will screw up
> all kinds of stuff (e.g. the resolver libraries) unless you set it up
> properly.
Any poin
On Wed, Feb 16, 2005 at 07:12:11PM -0500, Stas Bekman wrote:
> please look at your original report, William, it was failing the same 2
> sub-tests.
That's weird because it's only failing one if I run it by itself. This
obviously wasn't the case earlier when I reported the error. At any
rate, this
On Wed, Feb 16, 2005 at 07:14:24PM -0500, Stas Bekman wrote:
> >Yes, it is (though keep in mind that this is a virtual server running as
> >a jailed process, not a separate machine).
>
> That could be the reason.
But if I open a lynx session and surf over to localhost, my server comes
up fine.
On Wed, Feb 16, 2005 at 07:12:11PM -0500, Stas Bekman wrote:
> Joe, do you have an idea why this doesn't work on FreeBSD 5.3 (in jail
> environment). I remember last time you've fixed something about some BSD
> flavor in APR socket lib. Thanks.
That was all the non-blocking-vs-blocking stuff. F
William McKee wrote:
On Wed, Feb 16, 2005 at 04:06:39PM -0500, Stas Bekman wrote:
whereas Apache-Test sees 127.0.0.1. I suppose 166.70.252.34
is the external IP of the same machine.
Yes, it is (though keep in mind that this is a virtual server running as
a jailed process, not a separate machine).
William McKee wrote:
On Wed, Feb 16, 2005 at 04:08:45PM -0500, Stas Bekman wrote:
see if this patch helps:
Uh-oh, from bad to worse. Now we're failing two tests (instead of only
the last one):
please look at your original report, William, it was failing the same 2
sub-tests.
# Running under pe
On Wed, Feb 16, 2005 at 04:06:39PM -0500, Stas Bekman wrote:
> whereas Apache-Test sees 127.0.0.1. I suppose 166.70.252.34
> is the external IP of the same machine.
Yes, it is (though keep in mind that this is a virtual server running as
a jailed process, not a separate machine).
> Try to debug
On Wed, Feb 16, 2005 at 04:08:45PM -0500, Stas Bekman wrote:
> see if this patch helps:
Uh-oh, from bad to worse. Now we're failing two tests (instead of only
the last one):
# Running under perl version 5.008006 for freebsd
# Current time local: Wed Feb 16 17:23:47 2005
# Current time GMT:
On Wed, Feb 16, 2005 at 04:12:34PM -0500, Stas Bekman wrote:
> Don't forget that we are talking about APR socket API, not perl socket
> API, which aren't the same.
Oh, right, I hadn't really considered that. Hopefully it's at least
useful to see that the perl sockets are working.
> I've never s
William McKee wrote:
I didn't get very far with debugging the test (basically the test server
got started and I lost control of the debugger). At any rate, I found
some more information about sockets inside of jailed environments[1].
Section 4.2.2 seems to indicate that the type of socket we are cr
William McKee wrote:
t/TEST t/protocol/echo_block.t -v
# Failed test 2 in t/protocol/echo_block.t at line 22
# expected: hello
# received:
# Failed test 3 in t/protocol/echo_block.t at line 22 fail #2
not ok 2
# expected: world
# received:
not ok 3
see if this patch helps:
Index:
William McKee wrote:
BTW, this is a different issue:
t/TEST t/preconnection/note.t -v
# testing : connection notes
# Failed test 1 in t/preconnection/note.t at line 16
# expected: 127.0.0.1
# received: 166.70.252.34
Here the Apache API:
my $ip = $c->remote_ip;
sees 166.70.252.34
where
I didn't get very far with debugging the test (basically the test server
got started and I lost control of the debugger). At any rate, I found
some more information about sockets inside of jailed environments[1].
Section 4.2.2 seems to indicate that the type of socket we are creating
in the followi
Stas (and anyone else using FreeBSD),
I tried searching the archives but didn't find anything that
specifically addressed the errors I'm having. As shown in my original
bug report, I'm using FreeBSD 5.3 in a jailed (chrooted) environment.
I'm willing to dig into the test errors if you can give me
On Tue, Feb 15, 2005 at 06:41:04PM -0500, Stas Bekman wrote:
> I think there were a few similar reports posted here before (check the
> archives). Unfortunately no one running FreeBSD has volunteered to look at
> those. From what we have seen before all test failures seem to be caused
> by some
William McKee wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
While installing mod_perl2 on a FreeBSD 5.3 jail environment, I received
the following test errors:
Failed Test Stat Wstat Total Fail Failed List of Failed
--
-8<-- Start Bug Report 8<--
1. Problem Description:
While installing mod_perl2 on a FreeBSD 5.3 jail environment, I received
the following test errors:
Failed Test Stat Wstat Total Fail Failed List of Failed
41 matches
Mail list logo
