On Tue, Feb 8, 2011 at 6:26 PM, Max Pinton wrote:
> I checked $dbh->{mysql_auto_reconnect} and, as per the docs, it's 1 in a
> mod_perl script and 0 otherwise. Is there another place to look? It seems
> like something I'd really want to have on.
Recommended practice is to turn this off. If it's
On Tue, Feb 8, 2011 at 16:26, Max Pinton wrote:
> On Feb 8, 2011, at 7:36 AM, Perrin Harkins wrote:
>> That doesn't explain all of your errors though. I'm guessing that
>> you're opening a connection during startup and forking with it. You
>> need to find that. Look for things that might open a
On Feb 8, 2011, at 7:36 AM, Perrin Harkins wrote:
I'm just curious why it used to work. It seems like DBI would
reconnect a $dbh closure if it timed out.
One thing that might have changed is your database configuration.
MySQL is often configured to automatically reconnect.
I checked $dbh->{my
On Sun, Feb 6, 2011 at 4:44 PM, Max Pinton wrote:
> Did earlier versions of Perl/mod_perl/DBI/Apache::DBI handle closures
> differently?
No, not at all. This is a core Perl thing.
> I'm just curious why it used to work. It seems like DBI would
> reconnect a $dbh closure if it timed out.
One th
On Feb 6, 2011, at 8:20 AM, Perrin Harkins wrote:
Are you running the worker MPM? Apache::DBI will do the right thing
with prefork MPM, but I don't think it will work with threads.
Nope, prefork:
# apache2 -V
Server version: Apache/2.2.16 (Debian)
Server built: Nov 14 2010 18:14:55
Server's
Hi Max,
On Sat, Feb 5, 2011 at 10:01 PM, Max Pinton wrote:
> But the issue I'm asking about today is with DBI (1.612) and Apache::DBI
> (1.08). In my old configuration they worked fine, but after the upgrade I
> started seeing tons of errors like this:
>
> DBD::mysql::st execute failed: Commands
