Hi all,
I am having a very busy LAMP server with about 10 GBs of database.
The server gets an average of 100 HTTP requests per second, & hence the server always has 500+ active persistent connections as I can judge using the mysql command " SHOW PROCESSLIST"
I used the whm backups to backup the user with all databases.
Strangely, when I extracted the backup tarballs, I found that all small databases had complete sql dump file with all the data, except the one whose size is 10 GB.
Here are the contents of the file "/cpbackup/monthly/mydomain/mysql/database_name.sql"
mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect
Its very strange, that the rest of the DB backups are fine & this one got messed.
Can anyone suggest some reason for this strange behaviour?
Server configuration is dual xeon cpu quad,i.e., 8 cores, & 8 GB of RAM.
Thanks...
I am having a very busy LAMP server with about 10 GBs of database.
The server gets an average of 100 HTTP requests per second, & hence the server always has 500+ active persistent connections as I can judge using the mysql command " SHOW PROCESSLIST"
I used the whm backups to backup the user with all databases.
Strangely, when I extracted the backup tarballs, I found that all small databases had complete sql dump file with all the data, except the one whose size is 10 GB.
Here are the contents of the file "/cpbackup/monthly/mydomain/mysql/database_name.sql"
mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect
Its very strange, that the rest of the DB backups are fine & this one got messed.
Can anyone suggest some reason for this strange behaviour?
Server configuration is dual xeon cpu quad,i.e., 8 cores, & 8 GB of RAM.
Thanks...
