MySQL socket error?

[Xpajun]

I'm getting the following error (on and off I think but in batches - multiple attempts at a time) in my error log - anyone come across it and has a cure?

 

PHP Warning:  mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11) in /******/*******/public_html/includes/functions/database.php on line 19

 

Line 19 is 2nd $$link:

   if (USE_PCONNECT == 'true') {
     $$link = mysql_pconnect($server, $username, $password);
   } else {
     $$link = mysql_connect($server, $username, $password);
   }

[goldoi]

I'm getting the following error (on and off I think but in batches - multiple attempts at a time) in my error log - anyone come across it and has a cure?

 

PHP Warning:  mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11) in /******/*******/public_html/includes/functions/database.php on line 19

 

Line 19 is 2nd $$link:

   if (USE_PCONNECT == 'true') {
     $$link = mysql_pconnect($server, $username, $password);
   } else {
     $$link = mysql_connect($server, $username, $password);
   }

 

Is your includes/configure.php et admin/includes/configure.php correct ?

Check this line: define('DB_SERVER', 'localhost');

[burt]

Usually means the SQL server is intermittent (ie, a hosting problem).

I've not come across the error in any other context.

[Xpajun]

Is your includes/configure.php et admin/includes/configure.php correct ?

Check this line: define('DB_SERVER', 'localhost');

 

 

Yes it's a live active site - been live without the problem for 5 or 6 years

 

 

Thanks for your suggestion though

[Xpajun]

Usually means the SQL server is intermittent (ie, a hosting problem).

I've not come across the error in any other context.

 

 

Thanks Gary - actually the hosts have just done a SQL update (without telling me of course) wonder if that might cure it in that case - the errors have been coming in for the last 2 months at least (so not the update that has caused it)