libdbd-mysql-perl and mysql-server-5.0.19-3 problems

Bug #41872 reported by Jason
4
Affects Status Importance Assigned to Milestone
libdbd-mysql-perl (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Whenever I'm accessing mysql through libdbd-mysql-perl in a perl/CGI app, the database dies. In the past, I have been able to get things working by shutting down mysql, removing the libdbd-mysql-perl library, re-downloading and reinstalling it, then restarting the mysql server, and in a while loop watching the mysql.sock file with a simple ls -l. However, that appears not to be a working jerry-rig anymore.

Here are the messages in my apache error log:

[Fri Apr 28 07:30:08 2006] [error] [client 10.254.254.4] DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/lib/perl5/Mysql.pm line 175., referer: http://docsdev/TransFlo/
[Fri Apr 28 07:30:08 2006] [error] [client 10.254.254.4] DBD::mysql::st execute failed: MySQL server has gone away at /usr/lib/perl5/Mysql.pm line 175., referer: http://docsdev/TransFlo/
[Fri Apr 28 07:30:08 2006] [error] [client 10.254.254.4] Can't call method "numrows" on an undefined value at /usr/local/DOCS/SessionID.pl line 473., referer: http://docsdev/TransFlo/
[Fri Apr 28 07:30:08 2006] [error] [client 10.254.254.4] Compilation failed in require at ../GlobalConfig.pl line 35., referer: http://docsdev/TransFlo/
[Fri Apr 28 07:30:08 2006] [error] [client 10.254.254.4] Compilation failed in require at ./Config.pl line 4., referer: http://docsdev/TransFlo/
[Fri Apr 28 07:30:08 2006] [error] [client 10.254.254.4] Compilation failed in require at /usr/local/DOCS/TransFlo/TerminalAuditReports.cgi line 16., referer: http://docsdev/TransFlo/
[Fri Apr 28 07:30:08 2006] [error] [client 10.254.254.4] Premature end of script headers: TerminalAuditReports.cgi, referer: http://docsdev/TransFlo/
[Fri Apr 28 07:30:08 2006] [error] [client 10.254.254.4] script not found or unable to stat: /usr/local/DOCS/TransFlo/ErrorHandler.cgi, referer: http://docsdev/TransFlo/

Here is the list of relevant installed packages:

ii libdbd-mysql-perl 3.0002-2build1 A Perl5 database interface to the MySQL data
ii libmysqlclient10 3.23.56-3 LGPL-licensed client library for MySQL datab
ii libmysqlclient12 4.0.24-10ubuntu2 mysql database client library
ii libmysqlclient14 4.1.15-1ubuntu5 mysql database client library
ii libmysqlclient15off 5.0.19-3 mysql database client library
ii mysql-admin 1.1.6-1build1 GUI tool for intuitive MySQL administration
ii mysql-admin-common 1.1.6-1build1 Architecture independent files for MySQL Adm
ii mysql-client-5.0 5.0.19-3 mysql database client binaries
ii mysql-common 5.0.19-3 mysql database common files (e.g. /etc/mysql
ii mysql-navigator 1.4.2-6 GUI client program for MySQL database server
ii mysql-query-browser 1.1.17-5ubuntu2 Official GUI tool to query MySQL database
ii mysql-query-browser-common 1.1.17-5ubuntu2 Architecture independent files for MySQL Que
ii mysql-server 5.0.19-3 mysql database server (current version)
ii mysql-server-5.0 5.0.19-3 mysql database server binaries

Finally, as you can see, the mysql.sock file *does* go away:

srwxrwxrwx 1 mysql mysql 0 2006-04-28 07:55 /var/run/mysqld/mysqld.sock
srwxrwxrwx 1 mysql mysql 0 2006-04-28 07:55 /var/run/mysqld/mysqld.sock
srwxrwxrwx 1 mysql mysql 0 2006-04-28 07:55 /var/run/mysqld/mysqld.sock
srwxrwxrwx 1 mysql mysql 0 2006-04-28 07:55 /var/run/mysqld/mysqld.sock
srwxrwxrwx 1 mysql mysql 0 2006-04-28 07:55 /var/run/mysqld/mysqld.sock
ls: /var/run/mysqld/mysqld.sock: No such file or directory
ls: /var/run/mysqld/mysqld.sock: No such file or directory
ls: /var/run/mysqld/mysqld.sock: No such file or directory
ls: /var/run/mysqld/mysqld.sock: No such file or directory
ls: /var/run/mysqld/mysqld.sock: No such file or directory

The query is a simple select:
select doc_uri from help_system_document_map where cgi_uri_md5='$cgi_uri_md5';

Is there anything else I can examine to find out *exactly* what's going wrong and where the problem is?

Thank you!

--Jason

Revision history for this message
Jason (jason-pfeil) wrote :

I got it to work this time by:

1. dpkg --force-all -P libdbd-mysql-perl
2. rm /var/cache/apt/archives/libdbd-mysql-perl_3.0002-2build1_i386.deb
3. apt-get install libdbd-mysql-perl
4. /etc/init.d/mysql stop
5. /etc/init.d/mysql start
6. while [ 1 ]; do ls -l /var/run/mysqld/mysqld.sock; echo; ps auxw | grep mysql; done
7. run the CGI

Thanks!

Revision history for this message
Jason (jason-pfeil) wrote :

Further research indicates that the sequence of purging the package and reinstalling it is not the key. Just keep reloading the page over and over again eventually works for a period of time. It appears that the crash behavior is random.

Does anyone have any suggestions on anything I can do to get more helpful diagnostic information?

Thanks!

--Jason

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom reproducible in 8.10 alpha?

Changed in libdbd-mysql-perl:
status: New → Incomplete
Revision history for this message
Jason (jason-pfeil) wrote : Re: [Bug 41872] Re: libdbd-mysql-perl and mysql-server-5.0.19-3 problems

Hi, Mr. Chen.

Unfortunately, I am no longer able to test this as I have changed careers
and I am currently in training. As such, I no longer have access to the
tools necessary to test this problem. Once I settle down (probably early
next year), I will try to test it again.

Thank you!

--Jason

On Wed, Sep 10, 2008 at 10:05 PM, Daniel T Chen <email address hidden>wrote:

> Is this symptom reproducible in 8.10 alpha?
>
> ** Changed in: libdbd-mysql-perl (Ubuntu)
> Status: New => Incomplete
>
> --
> libdbd-mysql-perl and mysql-server-5.0.19-3 problems
> https://bugs.launchpad.net/bugs/41872
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Ensign Jason A. Pfeil, USN
J.D., Florida Coastal School of Law, 2008
japfeil=at=fcsl.edu / jason.pfeil=at=gmail.com

Revision history for this message
JanBrinkmann (jbrinkmann) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in libdbd-mysql-perl:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.