Mandriva 2008 update crashes openEMR

dr_smit wrote on Thursday, November 15, 2007:

An upgrade from Mandriva 2007.0 to Mnadriva 2008 resulted in the following error…
------------------------------------------------------------------------------
Warning: mysql_pconnect() [function.mysql-pconnect]: Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (2) in /var/www/html/openemr/library/adodb/drivers/adodb-mysql.inc.php on line 335
Check that mysqld is running.

ERROR: Could not connect to server!

Error: Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (2)
-----------------------------------------------------------------------------\

Does this mean that MySQL has been upgarded to an incompatible version…

What can be the solution??

drbowen wrote on Saturday, November 17, 2007:

Dear Dr. Smit,

The error message:

Error: Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’

usually means that your MySQL server is not running.

Your Mandriva update did not crash OpenEMR but it does seem to have crashed your MySQL server.  You need to touble shoot what is happening here.

Look in the MySQL error log. The file is usually named with the name of your server like "myserver.err" In Linux this is usually located in the /var/lib/mysql directory but this varies between distributions.

Sam Bowen, MD

dr_smit wrote on Tuesday, November 20, 2007:

smitdesk.err reads as:

070823 12:11:24  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait…
070823 12:11:25  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait…
070823 12:11:25  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait…
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
070823 12:11:27  InnoDB: Started; log sequence number 0 0
070823 12:11:27 [Note] /usr/sbin/mysqld: ready for connections.
Version: ‘5.0.37’  socket: ‘/var/lib/mysql/mysql.sock’  port: 0  Mandriva Linux - MySQL Standard Edition (GPL)
070823 12:11:29 [Note] /usr/sbin/mysqld: Normal shutdown

070823 12:11:30  InnoDB: Starting shutdown…
070823 12:11:32  InnoDB: Shutdown completed; log sequence number 0 43655
070823 12:11:32 [Note] /usr/sbin/mysqld: Shutdown complete

070823 12:11:32  mysqld ended

070830 13:41:19  mysqld started
070830 13:41:19  InnoDB: Started; log sequence number 0 43655
070830 13:41:19 [Note] /usr/sbin/mysqld: ready for connections.
Version: ‘5.0.37’  socket: ‘/var/lib/mysql/mysql.sock’  port: 0  Mandriva Linux - MySQL Standard Edition (GPL)
070830 13:41:21 [Note] /usr/sbin/mysqld: Normal shutdown

070830 13:41:23  InnoDB: Starting shutdown…
070830 13:41:25  InnoDB: Shutdown completed; log sequence number 0 43655
070830 13:41:26 [Note] /usr/sbin/mysqld: Shutdown complete

070830 13:41:26  mysqld ended

dr_smit wrote on Friday, November 30, 2007:

can graduation to Mysql 5 be playing the error?

dr_smit wrote on Friday, November 30, 2007:

I did service mysqld restart

and it worked

thanks sam and linuxforum.org