Re: mod_perl 1.30 seg faults

. Salvador Ortiz. On 10/29/2010 02:50 PM, Brian Hirt wrote: I'm running a modperl installation with 1.30 and apache 1.3.42. I recently upgrade from Ubuntu 9.04 to Ubuntu 10.04 and now every time a mod perl process shuts, it dumps core. None of the application code changed. Maybe modperl

mod_perl 1.30 seg faults

I'm running a modperl installation with 1.30 and apache 1.3.42. I recently upgrade from Ubuntu 9.04 to Ubuntu 10.04 and now every time a mod perl process shuts, it dumps core. None of the application code changed. Maybe modperl isn't playing nicely with perl 5.10.1 (the old machine had

Segfault in Perl_av_undef

I just built up a new mod_perl1.30 with apache 1.3.41 and started seeing segfaults in my logs. I ended up tracking the problem down to http://svn.apache.org/viewvc?view=revrevision=555908 It looks like a fix was committed almost 2 years ago. So my questions are these. Is a 1.31 ever going

Re: Callback called exit.

of with gigibytes of 'Callback called exit' messages. regards, brian On May 5, 2004, at 11:00 PM, Glenn wrote: On Wed, May 05, 2004 at 08:11:56PM -0600, Brian Hirt wrote: I've been running across a problem lately where a child process terminates because of an out of memory error. It prints Out

Re: Callback called exit.

On May 6, 2004, at 10:27 AM, Perrin Harkins wrote: On Wed, 2004-05-05 at 22:11, Brian Hirt wrote: I've been running across a problem lately where a child process terminates because of an out of memory error. It prints Out of Memory once, the the process sucks up all available cpu print Callback

Re: Callback called exit.

supported. See +http://perlmonks.org/index.pl?node_id=287850 for more information. =head2 server reached MaxClients setting, consider raising the MaxClients setting regards, Brian On May 6, 2004, at 1:19 PM, Stas Bekman wrote: Brian Hirt wrote: I too followed the advice too, but it did nothing

Callback called exit.

I've been running across a problem lately where a child process terminates because of an out of memory error. It prints Out of Memory once, the the process sucks up all available cpu print Callback called exit. to the log file until it hit's it's 2GB max size. I have some Apache::Resource

Re: introducing new code with no perceived user delays?

The way i do this is having a lightweight apache proxy on port 80. My mod perl application listens on a different port and receives requests from the proxy. When i need to roll out new code, i start up a 2nd mod perl application on a 3rd port, update the rules for the proxy to go to the new

should we be using tempnam() ?

i think that libapreq shouldn't be using tempnam()It frustraiting that you can't force tempnam to use a given directory via some sort of api. this makes the TEMP_DIR argument to Apache::Request behave inconsistently depending on what environment variables may or may not be set. If you

[libapreq] could not create/open temp file

all of a sudden i'm getting '[libapreq] could not create/open temp file'. Searching on google, i came across a patch stan posted to give a more meaningful error message, but somehow it never made it into the CVS tree. (i've got libapreq1.2 installed) here was the old patch. anyway, it would