Re: [mp2] 1.99_14: socket problem

2004-06-01 Thread Stas Bekman
Jie Gao wrote: [...] [Sat May 29 21:43:08 2004] [error] [client 129.xxx.xxx.xxx] Undefined subroutine main::129.xxx.xxx.xxx called at -e line 0\n Looks definitely like %ENV problem, although it only shows in the error_log. I've found what caused this. The culprit seems to be this sub in my httpd.

Re: [mp2] 1.99_14: socket problem

2004-05-31 Thread Jie Gao
On Sat, 29 May 2004, Jie Gao wrote: > Date: Sat, 29 May 2004 22:38:05 +1000 (EST) > From: Jie Gao <[EMAIL PROTECTED]> > To: Stas Bekman <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > > > > On Fri, 28 May 20

Re: [mp2] 1.99_14: socket problem

2004-05-30 Thread Jie Gao
On Sat, 29 May 2004, Stas Bekman wrote: > Date: Sat, 29 May 2004 12:50:46 -0700 > From: Stas Bekman <[EMAIL PROTECTED]> > To: Jie Gao <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > Jie Gao wrote: > [...] > &g

Re: [mp2] 1.99_14: socket problem

2004-05-29 Thread Stas Bekman
Jie Gao wrote: [...] I find I get this kind of error message with almost all accesses. I get this when accessing server-status: [Sat May 29 21:41:07 2004] [error] [client 129.xxx.xxx.100] Undefined subroutine main:: called at -e line 0\n\tApache::porting::__ANON__('Apache::RequestRec=SCALAR(0x83b3

Re: [mp2] 1.99_14: socket problem

2004-05-29 Thread Jie Gao
On Fri, 28 May 2004, Stas Bekman wrote: > Date: Fri, 28 May 2004 18:00:28 -0700 > From: Stas Bekman <[EMAIL PROTECTED]> > To: Jie Gao <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > Jie Gao wrote: > > >>

Re: [mp2] 1.99_14: socket problem

2004-05-29 Thread Jie Gao
On Fri, 28 May 2004, Stas Bekman wrote: > Date: Fri, 28 May 2004 18:00:28 -0700 > From: Stas Bekman <[EMAIL PROTECTED]> > To: Jie Gao <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > Jie Gao wrote: > > >>

Re: [mp2] 1.99_14: socket problem

2004-05-28 Thread Jie Gao
On Fri, 28 May 2004, Stas Bekman wrote: > Date: Fri, 28 May 2004 17:36:44 -0700 > From: Stas Bekman <[EMAIL PROTECTED]> > To: Jie Gao <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > Jie Gao wrote: > [...] >

Re: [mp2] 1.99_14: socket problem

2004-05-28 Thread Stas Bekman
Jie Gao wrote: Oh, wait, it was an error, not a warning. You want: $SIG{__DIE__} = \&Carp::confess; then. OK, I've got this after changing to use confess: [Sat May 29 10:53:41 2004] [error] [client 129.78.64.21] Undefined subroutine &Apache::Connection::AUTOLOAD called at /usr/local/perl-5.8.4/

Re: [mp2] 1.99_14: socket problem

2004-05-28 Thread Stas Bekman
Jie Gao wrote: [...] Thanks very much. I'll do when I find some time for it. Right now I'm getting segmentation faults and am going to debug it today. Sure, please take your time. BTW, I am getting this in the log: Undefined subroutine &Apache::Connection::AUTOLOAD called.\n, It seems that some mod

Re: [mp2] 1.99_14: socket problem

2004-05-28 Thread Jie Gao
On Fri, 28 May 2004, Stas Bekman wrote: > Date: Fri, 28 May 2004 11:27:46 -0700 > From: Stas Bekman <[EMAIL PROTECTED]> > To: Jie Gao <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > Jie Gao wrote: > > > &g

Re: [mp2] 1.99_14: socket problem

2004-05-28 Thread Stas Bekman
Jie Gao wrote: On Wed, 26 May 2004, Stas Bekman wrote: Date: Wed, 26 May 2004 19:08:40 -0700 From: Stas Bekman <[EMAIL PROTECTED]> To: Jie Gao <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: [mp2] 1.99_14: socket problem Jie Gao wrote: [...] If you've moved to Apache 2.0

Re: [mp2] 1.99_14: socket problem

2004-05-28 Thread Jie Gao
On Wed, 26 May 2004, Stas Bekman wrote: > Date: Wed, 26 May 2004 19:08:40 -0700 > From: Stas Bekman <[EMAIL PROTECTED]> > To: Jie Gao <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > Jie Gao wrote: > [...] > &

Re: [mp2] 1.99_14: socket problem

2004-05-26 Thread Stas Bekman
Jie Gao wrote: [...] If you've moved to Apache 2.0.49, it now gives you a non-blocking socket. So all protocol handlers now must start with: use APR::Const-compile => 'SO_NONBLOCK'; $sock->opt_set(APR::SO_NONBLOCK => 0); Is this supported? $socket->opt_set(APR::SO_KEEPALIVE, 1); I haven't

Re: [mp2] 1.99_14: socket problem

2004-05-26 Thread Jie Gao
On Mon, 24 May 2004, Stas Bekman wrote: > Date: Mon, 24 May 2004 14:53:31 -0700 > From: Stas Bekman <[EMAIL PROTECTED]> > To: Jie Gao <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > Jie Gao wrote: > > > &g

Re: [mp2] 1.99_14: socket problem

2004-05-24 Thread Stas Bekman
Jie Gao wrote: On Mon, 24 May 2004, Stas Bekman wrote: Date: Mon, 24 May 2004 10:18:22 -0700 From: Stas Bekman <[EMAIL PROTECTED]> To: Jie Gao <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: [mp2] 1.99_14: socket problem Jie Gao wrote: Hi All, This used to work: $socket->

Re: [mp2] 1.99_14: socket problem

2004-05-24 Thread Jie Gao
On Mon, 24 May 2004, Stas Bekman wrote: > Date: Mon, 24 May 2004 10:18:22 -0700 > From: Stas Bekman <[EMAIL PROTECTED]> > To: Jie Gao <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [mp2] 1.99_14: socket problem > > Jie Gao wrote: >

Re: [mp2] 1.99_14: socket problem

2004-05-24 Thread Stas Bekman
Jie Gao wrote: Hi All, This used to work: $socket->recv($line, 34); but the syntax has changed in 1.99_14, so I modified it to be: $line = $socket->recv(34); But I am getting this error: [error] APR::Socket::recv: Resource temporarily unavailable at ...pm line 117 OBAny other obvious c