MYSQL Modsecparse.pl Can't Connect
I'm getting the following message on my server, only thing I can think of is a resize of my VPS, but I wouldn't have figured that would have changed this. The message is coming off a cron, so I'm getting it every hour:
I checked the DB out in PHPmyadmin and found the following:
Any advice would be most appreciated, I tried logging in via SSH to access the DB and received the following error:
/etc/cron.hourly/modsecparse.pl:
DBI connect('modsec:localhost','modsec',...) failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) at /etc/cron.hourly/modsecparse.pl line 20
Unable to connect to mysql database at /etc/cron.hourly/modsecparse.pl line 20. I checked the DB out in PHPmyadmin and found the following:
modsec localhost database-specific SELECT,INSERT,UPDATE,DELETE No
root 127.0.0.1 global ALL PRIVILEGES Yes
root ::1 global ALL PRIVILEGES Yes
root li-xxx-xx global ALL PRIVILEGES Yes
root localhost global ALL PRIVILEGES Yes
Any advice would be most appreciated, I tried logging in via SSH to access the DB and received the following error:
DBI connect('modsec:localhost','modsec',...) failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) at /etc/cron.hourly/modsecparse.pl line 20 -
Hello :) Please see the following thread: Recreate /tmp/mysql.sock Thank you. 0 -
[quote="cPanelMichael, post: 1708572">Hello :) Please see the following thread: Recreate /tmp/mysql.sock Thank you.
This was perfect, cleared up the issue right away. Out of curiosity, will the symbolic link have to be created every time MYSQL restarts or does this establish this link on a permanent basis?0 -
It should still exist through MySQL restarts but you may want to restart MySQL on your system to confirm that's the case. Thank you. 0 -
[quote="cPanelMichael, post: 1708691">It should still exist through MySQL restarts but you may want to restart MySQL on your system to confirm that's the case. Thank you.
Okay, I'll make sure to give it a try. Out of curiosity, you wouldn't happen to know anything about this?Time: Thu Aug 14 19:17:28 2014 +0000 File: /tmp/mysql.sock Reason: Suspicious symlink (->/var/lib/mysql/mysql.sock) Owner: ownerex:ownerex (500:500) Action: No action taken
I assume it is a result of my earlier modification, do you know how to add an exception to lfd to not worry about this particular file? I assume that there's nothing malicious here.0 -
I believe this thread from their forums should help you: [url=http://forum.configserver.com/viewtopic.php?t=2910]ConfigServer Community Forum - Dealing with false-positives in cxs Thank you. 0
Please sign in to leave a comment.
Comments
5 comments