On Mon, Jun 30, 2008 at 4:54 AM, Tobias Kremer [EMAIL PROTECTED] wrote:
We never fork and I thought that Apache::DBI takes care of checking if a
connection went stale by utilizing DBI's/DBD::mysql's ping() method?
It does, but it can't stop you from doing things like putting a
database handle
On Mon, Jun 30, 2008 at 10:54:20AM +0200, Tobias Kremer wrote:
Any other ideas? Thanks!
It could be that your query(result) is too large for the
'max_allowed_packet' setting. The mysql-client that is connected to your
process will then silently die, giving the 'Lost mysql...' error as
result.
Quoting Tobias Kremer [EMAIL PROTECTED]:
On 25.06.2008, at 20:58, Amiri Barksdale wrote:
I had big trouble with DBD::mysql 4.007. I didn't get rid of my
segfault problem running mod_perl 1.31 until I went back to 4.004.
Thanx. It really looks a lot like my problem:
when connecting during Apache startup with
Apache::DBI
Quoting Tobias Kremer [EMAIL PROTECTED]:
On 25.06.2008, at 20:58, Amiri Barksdale wrote:
I had big trouble with DBD::mysql 4.007. I didn't get rid of my
segfault problem running mod_perl 1.31 until I went back to 4.004.
Thanx. It really
On Fri, Jun 27, 2008 at 5:51 AM, Tobias Kremer [EMAIL PROTECTED] wrote:
Now if I could just get rid of those annoying random Commands out of sync
and
Lost connection to MySQL server during query errors that happen once in a
while ...
Those generally mean that you timed out (set MySQL's
- Ubuntu Feisty with apache-perl.
- stock Ubuntu Perl 5.8.8 (which unfortunately comes with threads)
- self-rolled DBD::mysql (against libmysqlclient15-dev), DBI and Apache::DBI
I should have mentioned that we're using DBI 1.605, Apache::DBI 1.07 and
DBD::mysql 4.007. The Ubuntu apache-perl
Quoting Tobias Kremer [EMAIL PROTECTED]:
- Ubuntu Feisty with apache-perl.
- stock Ubuntu Perl 5.8.8 (which unfortunately comes with threads)
- self-rolled DBD::mysql (against libmysqlclient15-dev), DBI and
Apache::DBI
I should have mentioned that we're using DBI 1.605, Apache::DBI 1.07
Quoting André Warnier [EMAIL PROTECTED]:
I don't know if the above versions are imposed to you, but in case you
have a choice, I would recommend de-installing your Apache and mod_perl,
and re-install the Apache 2.2 version and the mod_perl that goes with it.
Apache 1.x and mod_perl 1.x are old
On Wed, Jun 25, 2008 at 5:49 AM, Tobias Kremer [EMAIL PROTECTED] wrote:
After de-installing the latest (self-rolled) DBI and DBD::mysql modules and
installing the corresponding packages provided by Ubuntu (libdbd-mysql-perl
and
libdbi-perl) the segfaults are gone.
It sound like this is a
I had big trouble with DBD::mysql 4.007. I didn't get rid of my
segfault problem running mod_perl 1.31 until I went back to 4.004.
Amiri
On Jun 25, 2008, at 12:14 PM, Perrin Harkins wrote:
On Wed, Jun 25, 2008 at 5:49 AM, Tobias Kremer [EMAIL PROTECTED]
wrote:
After de-installing the
On 25.06.2008, at 20:58, Amiri Barksdale wrote:
I had big trouble with DBD::mysql 4.007. I didn't get rid of my
segfault problem running mod_perl 1.31 until I went back to 4.004.
Thanx. It really looks a lot like my problem:
http://bugs.mysql.com/bug.php?id=36810
I'll try reverting to an
11 matches
Mail list logo
