Read-only & MySQL Failed

[ccreighton]

Hello,

Merry Christmas to all!

My server is acting up...

MySQL is presenting the following error:
"Warning: mysql_pconnect(): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)"

Then when I attempted to apply fixes shown in the forums I ran into this problem: "Read-only file system"

I don't know if one caused the other. Your help is appreciated.

 

[jphilipson]

Sounds like you were owned,start over with a clean drive... then resore your data from the old

 

[HSAdam]

That's totally not true, and a very stupid response.. you should get off these boards.

 

[jphilipson]

Well it does sound like he is owned.. while there are other ways to solve that problem, I do not think most dcs will allow it.. it is in the dcs best interest to make the server leasee get a fresh drive.. and if he was owned its easy enough to restore from the old drive, and its much safer than tring to clean up an owned server

 

[Donna]

assuming he was owned and somehow something didn't get mounted right (I've had that happen, and done by a DC tech no less).

First he needs to investigate a little, try a reboot, reset the mySQL root pass etc, check tmp and /var/tmp for odd things as well as running chkrootkit and so on and so forth.

Also, did he run the new securetmp script nick made, I have a mysql problem similar to this guys on one server when I use that script and have to disable it to keep it working.

Assuming he was owned right off the bat with no real information provided by the original poster is getting a little ahead of things. If apache fails should you reinstall too? Or maybe take a look at things first and see if you can get it going again?

 

[denisdekat09]

How do you disable this script (securetmp)? I am going batty, I took it out of the cron job thinking that would do it but mysql is dead

I should add that the server had no tmp partition as it was an older one, I hope this is reversible....



cPanel.net Support Ticket Number: 34570

 

[denisdekat09]

BTW, I fixed the mysql problem by rerunning /scripts/securetmp I think the fact that this server had no /tmp partition to begin with may have made it more difficult to remove.

 

[denisdekat09]

Ok, I fixed my woes, it was all my own mishaps and advetures...

Sorry for the noise

 

[guinea812]

hey-I have the same problem, how did you fix it? It killed sql and it won't allow it to work, please help. I also had no /tmp partition, please help!

 

[denisdekat09]

this may help:

http://www.webhostingtalk.com/showthread.php?s=&threadid=221516

I can't quite remember, I think it was the reboot that fixed it.