[owning_y0u]

I keep getting the following error

Database error in vBulletin :

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' (2)
/var/www/vhosts/xxxxxxxx.eu/httpdocs/includes/class_core.php on line 313

Database error in vBulletin :

mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Too many connections
/var/www/vhosts/xxxxxxx.eu/httpdocs/includes/class_core.php on line 313

the database has a connection limit set on 250 connections so thats not the problem (as we have max 75 connections at the sametime.
Cookie session times out after 15 mins so not a problem.

getting crazy as i get around the 50 e-mails a day about it.

[Lynne]

These are server issues that you will need to talk to your host about.

[owning_y0u]

Originally Posted by Lynne

These are server issues that you will need to talk to your host about.

The host said it has nothing to-do with the server i hope you can be a bit more precise about it so i know where to start looking

[KevinL]

Your host has limited the connections to the database. So it is a host problem.

If it is hostgator I think they only allow 50 concurrent connections...

[TheRageIsOn]

check the mysql config to shorten the timeout values!
You may post them here...

[TNCclubman]

are you on a dedicated server or shared server?

[owning_y0u]

Originally Posted by KevinL

Your host has limited the connections to the database. So it is a host problem.

If it is hostgator I think they only allow 50 concurrent connections...

no its not hostgator we use a decent host, Connection limited is set to 250 and we have a max of 75 open connections on peak times.

Originally Posted by TNCclubman

are you on a dedicated server or shared server?

its shared with 1 other website. at this very moment a dedicated server isn't in the option list.

[Lynne]

See this page which covers both problems - Common MySQL Error Messages It is a server issue.

[Videx]

High CPU loads on an oversold shared server can cause both these errors - and lots of other semi-random ones. But unless your one other co-sharer is really misbehaving I can't see that. Still, you need to check your cpu loads around the times of the errors.