in reply to debugging mod_perl?

Are you saying this happened during a shutdown? If so, don't worry about it. If this happened during normal page-serving, when MySQL was up and appeared to be okay, you should be concerned. One thing you might want to try is connecting via TCP instead of local sockets.

Replies are listed 'Best First'.
Re: Re: debugging mod_perl?
by Flame (Deacon) on May 19, 2003 at 04:44 UTC
    Those errors were primaraly from threads that somehow froze and were forced to quit during shutdown. Apache::Session tried to save the data from the tied hash and failed because the database had already been shut down... at least that's my interpretation.


    My code doesn't have bugs, it just develops random features.

    Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

[reply]
      Hmmm. Why is your server being shut down in the middle of handling requests? Are you sure that you're completely destroying the session object every time? You could have a scoping problem that prevents Apache::Session from saving.
[reply]
        That's the question I'm trying to answer... sometimes I'll request the page and it will just sit there... I'll never get a reply (this from a process that should reply almost instantly.) I can't find any loops it could concievably be getting stuck in.


        My code doesn't have bugs, it just develops random features.

        Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

[reply]

In Section Seekers of Perl Wisdom