I ended up falling back to the previous Debian release. I'm planning to try
again in Debian 9.
On Tue, Jan 12, 2016 at 9:52 AM, FredB wrote:
> Hello,
>
> I have exactly the same issue that here
> https://mail-archives.apache.org/mod_mbox/perl-modperl/201509.mbox/%3CCAC5eUSu85CoiT0MkQvwvxjfrhJcn1
First, let me thank you for your efforts! I doubt I could have come to the
bottom of that. Unfortunately, I have been unable to reproduce my problem
outside of a production environment and I can't risk pushing a version of
perl into production that I've built myself just to test that. As unhelpful
Steve, John:
I did a bisect today against perl git, using mod_perl 2.0.9 and apache
2.2.29 to find out where my two issues were caused. It turns out that
both of my problems, which were:
- panic: attempt to copy freed scalar to
and also
- segmentation fault caused by a specific "retu
On 9/14/15 12:12 PM, Steve Hay wrote:
> Have you tried 5.20.3? This has just been released and contains a
> number of crash fixes. (I wonder if #123398 might be relevant?)
I just tried 5.20.3.
For my issue (mentioned earlier in this thread), 5.20.3 does not help.
I'll post a followup message in
No, I have not. I don't have time to mess with compiling my own version and
I certainly don't have time to support a custom version. I always run the
version that comes with Debian out of the box.
On Mon, Sep 14, 2015 at 1:12 PM, Steve Hay
wrote:
> Have you tried 5.20.3? This has just been relea
Have you tried 5.20.3? This has just been released and contains a number of
crash fixes. (I wonder if #123398 might be relevant?)
On 14 September 2015 at 15:57, John Dunlap wrote:
> I'll probably deal with this by staying on Debian 7 for the near future.
> I'll attempt upgrading again in Debian
I'll probably deal with this by staying on Debian 7 for the near future.
I'll attempt upgrading again in Debian 9.
On Mon, Sep 14, 2015 at 10:27 AM, Michael Schout wrote:
> On 9/11/15 2:26 PM, John Dunlap wrote:
> > I found a lot of stuff like the following in my Apache logs. Is it
> > possible
On 9/11/15 2:26 PM, John Dunlap wrote:
> I found a lot of stuff like the following in my Apache logs. Is it
> possible to get this kind of output from Apache when the server runs
> out of memory? I wouldn't have expected so. It has all the hallmarks
> of something more sinister.
For whatever its w
John,
Sometimes it's difficult to see what the error is because you can't see
the request (doesn't get logged)
To get round this - add:
* a transhandler which writes a tag (e.g. ST), the request and the PID
to the error log
* a cleanuphandler which does the same... with a different tag (
