Help is my database MAXING out!!

[eluser]smatakajr[/eluser]
Hey

I have Host Gator Box 8 GIG 4 Processors there biggest server
and im having

A Database Error Occurred Unable to connect to your database server using the provided settings."

Now i know the setting work.. they have been and apparently it looks
like the DB hiccuped

Is this because of too many connections at once? How do i fix?

Thanks for your help in advance!

[eluser]osci[/eluser]
Connect to your panel and see your logs. How can we help if there is no info or errors provided?

[eluser]toopay[/eluser]
Check your database.php at your config folder! Make sure you fill the righ username, password, database. Also Host and its port, if neccessary.

[eluser]InsiteFX[/eluser]
Try truning off pconnect
application/config/database.php

Code:

$db['default']['pconnect'] = TRUE;

// to
$db['default']['pconnect'] = FALSE;

This could also be a MySQL timing problem in your MySQL configuration!

InsiteFX

[eluser]smatakajr[/eluser]
Wow.. Didn't think of the Pconnect that's a default?
Shit ok thanks guys for all your help I will check my logs as well
But last night I could not even get into the box!!

Thanks!!

[eluser]smatakajr[/eluser]
Can I ask what is the added benifit to using pconnect?
I have always just used regular connect?

[eluser]InsiteFX[/eluser]
This should help you understand it!

persistent connection to a MySQL server

InsiteFX

[eluser]smatakajr[/eluser]
Here is why NOT to use it.. but CI comes with it ??

Here's a recap of important reasons NOT to use persistent connections:

* When you lock a table, normally it is unlocked when the connection closes, but since persistent connections do not close, any tables you accidentally leave locked will remain locked, and the only way to unlock them is to wait for the connection to timeout or kill the process. The same locking problem occurs with transactions. (See comments below on 23-Apr-2002 & 12-Jul-2003)

* Normally temporary tables are dropped when the connection closes, but since persistent connections do not close, temporary tables aren't so temporary. If you do not explicitly drop temporary tables when you are done, that table will already exist for a new client reusing the same connection. The same problem occurs with setting session variables. (See comments below on 19-Nov-2004 & 07-Aug-2006)

* If PHP and MySQL are on the same server or local network, the connection time may be negligible, in which case there is no advantage to persistent connections.

* Apache does not work well with persistent connections. When it receives a request from a new client, instead of using one of the available children which already has a persistent connection open, it tends to spawn a new child, which must then open a new database connection. This causes excess processes which are just sleeping, wasting resources, and causing errors when you reach your maximum connections, plus it defeats any benefit of persistent connections. (See comments below on 03-Feb-2004, and the footnote at http://devzone.zend.com/node/view/id/686#fn1)