View Full Version : Unable to connect to database : Check the connection script.

04-05-2004, 01:20 PM
I'm running about 3 weeks phpdig works good, use most 2 spiders in different dir with one db.
But today if I want spider of make a search I get his message;
Unable to connect to database : Check the connection script.
Read other posts, cheqk of mysql is running, reboot the server,
reload mysql via phpmyadmin. Change the site quota.
Other scripts with db work good.
Any idea?

marten :)

04-07-2004, 03:52 AM
I'm using PHPDIG now 3 weeks.
Spider everyday, the rseults in 3 weeks are about;

17.000 urls
excludes 15.322.789 =250mb
keywords 1.054.603 = 57,4mb
logs 407
spider 92.639 = 31.4mb
tempspider 497.335 = 45,5mb

webspace = 1gb
mysql = more then 10gb

If I want spider I get the message;
Unable to connect to database : Check the connection script.
I cannot come in the admin, the search dont work more.
I think that a maximum is reach, becourse other scripts running normal also mysql.

Any idea what to do on it, can I change some setings somewhere?

Marten :)

04-07-2004, 07:37 PM
Is it possible you are out of disk space on your web server?

04-07-2004, 10:06 PM
Hi Pat thanks for the reply.

There is enoff webspace over on the server.
I use for thecomplete server about 5 gb on a disk of 20gb.
The url for the spider have a space of 1 gb and use now 480 mb.
Most of the space, of that, is use by the text_content dir.
Have also install PHPDIG on a other url. that run normal.

Marten :)

04-10-2004, 03:13 PM
Hi. The only place that message would be printed is from the connect.php file - see below - so verify that the correct database info is in the connect.php file:

// Connection configuration

//connection to the MySql server
$id_connect = @mysql_connect(PHPDIG_DB_HOST,PHPDIG_DB_USER,PHPDIG_DB_PASS);
if (!$id_connect) {
die("Unable to connect to database : Check the connection script.\n");

04-12-2004, 02:35 AM
All the settings are correct, it was working also fine till it stop.

Have copy the tables to a other DB.
Copy the text_content to my local computer.
Delete the excisting DB and the dir with PHPDIG in it.
(have install phpdig more than one time, use one DB - perhaps it's to much)
Install PHPDIG again (twice) use the other DB, it run now normal.

Perhaps was the failure a bit flu.
Computers sometimes like human :D

Marten :)