Google Answers Logo
View Question
Q: mod_perl technical problem ( Answered,   1 Comment )
Subject: mod_perl technical problem
Category: Computers > Programming
Asked by: tomazos-ga
List Price: $10.00
Posted: 20 Apr 2002 02:07 PDT
Expires: 27 Apr 2002 02:07 PDT
Question ID: 2263
Why is mod_perl producing the following errors in my apache web server 

"null: Attempt to free unreferenced scalar."
"[notice] child pid 11830 exit signal Segmentation fault (11)"

It happens repeatedly and without pattern.
Subject: Re: mod_perl technical problem
Answered By: gale-ga on 21 Apr 2002 12:53 PDT

I noticed that you already posted your question on several message boards.

The answer to your question depends on a number of factors, including the 
versions of Perl and mod_perl you are using, the Perl modules referenced by the 
scripts that cause the errors, whether you're using embedded Perl, etc. 

The most recommended solution is installing the latest versions of Perl and 
mod_perl that probably have the patches for these often discussed problems. 

Other solutions include not using certain Perl modules, such as 
Apache::StatINC, changing certain Apache directives, such as PerlFreshRestart, 

For many specific solutions that may work for your particular configuration,
have a look at the unreferenced scalar threads on the GeoCrawler mod_perl board:

and the segmentation fault threads on Mathforum's mod_perl mailing list archive:

Also, do report your problem to the mod_perl developers. Stas Bekman, one of 
the most active developers, already recommended that you do that in his reply 

and provided a link to the document on reporting mod_perl problems:

More useful links:

Perldiag: Perl diagnostics (section on the unreferenced scalar error)

Debugging mod_perl

mod_perl Guide (sections on errors and warnings)

mod_perl FAQ (section on errors)

Doug Sparling's mod_perl links collection

Useful Google searches:

"attempt to free unreferenced scalar" mod_perl OR modperl
"segmentation fault" OR segfault OR segfaults OR segv "exit signal" mod_perl OR 
Subject: Re: mod_perl technical problem
From: sergio_carvalho-ga on 20 Apr 2002 04:21 PDT
Try to get some more info, and narrow down the problem. It would be useful if
you could know which script is causing the error. Try increasing the log level
to "debug". See here:

Also look on access.log for pages with HTTP result codes other than 200. 

A word of advice, though: do this at non-peak usage times. Debug log level
writes lots of data to the disk and really slows down apache. If you have enough
RAM, mount a ramdisk and direct the error log there. ~256Mb should be enough if
error conditions are relatively frequent.

Important Disclaimer: Answers and comments provided on Google Answers are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or other professional advice. Google does not endorse, and expressly disclaims liability for any product, manufacturer, distributor, service or service provider mentioned or any opinion expressed in answers or comments. Please read carefully the Google Answers Terms of Service.

If you feel that you have found inappropriate content, please let us know by emailing us at with the question ID listed above. Thank you.
Search Google Answers for
Google Answers  

Google Home - Answers FAQ - Terms of Service - Privacy Policy