Tim Moore wrote:
> Hi,
> 
> I have been getting a few problems recently with our web server (running
> Apache::ASP) where a few times the server has locked up and the following
> errors occur in the apache log...
> 
> 
> ----------------
> [Wed Sep 25 11:35:12 2002] [error] perl_call did not return a status arg,
> assuming OK
> MLDBM error: Please make sure     _File.pm is a properly installed package.
>  Perl says: "Null filename used at
> /opt/our-product/perl/lib/site_perl/5.6.1/MLDBM.pm line 107.
> " at /opt/our-product/perl/lib/site_perl/5.6.1/MLDBM/Sync.pm line 214
> [Wed Sep 25 11:35:15 2002] [error] can't tie to MLDBM with args:
> /tmp/asp/server/internal,258,416; error:  at
> /opt/our-product/perl/lib/site_perl/5.6.1/MLDBM/Sync.pm line 214.
> ----------------
> 

What are your StateSerializer & StateDB settings, if any?
What if you change them?

> and a similar one here...
> 
> ----------------
> MLDBM error: Please make sure MLDBM/Serializer/    /Dumper.pm is a properly
> installed package.
>  Perl says: "Unrecognized character \x02 at
> /opt/our-product/perl/lib/site_perl/5.6.1//MLDBM/Serializer/ line 1.
> Compilation failed in require at
> /opt/our-product/perl/lib/site_perl/5.6.1/MLDBM.pm line 107.
> " at /opt/our-product/perl/lib/site_perl/5.6.1/MLDBM/Sync.pm line 214
> [Wed Sep 25 14:44:01 2002] [error] can't tie to MLDBM with args:
> /tmp/asp/server/internal,258,416; error:  at
> /opt/our-product/perl/lib/site_perl/5.6.1/MLDBM/Sync.pm line 214.
> ----------------
> 
> 
> Note, there are some non-printable characters in the file/directory names in
> the log file, though I haven't a clue why (as far as I know, that's not the
> case on the hard disc).
> 
> Any idea what this is about?
> 

I am guessing that something is getting corrupt, but could not
tell you what or why. A common things to watch out for
includes not mounting StateDir over NFS unless you have verified
file locking.

> We don't use MLDBM, but I assume Apache::ASP does? What does it do anyway?
> 

Apache::ASP uses MLDBM to manage data for $Session & $Application.
If you do not use these, you may set NoState to 1.

Please post back to the list when you have figured out the
answer to your problem.

Regards,

Josh
________________________________________________________________
Josh Chamas, Founder                   phone:925-552-0128
Chamas Enterprises Inc.                http://www.chamas.com
NodeWorks Link Checking                http://www.nodeworks.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to