Deployment Architecture

MySQL 5.3 connection issues

Langbost
Engager

Hello, experts. Recently i have met with CentOS 6.3 x64 server at my new office. On this server apache2, MySQL, postfix and apache protection on the base of mod_security installed, also there is Splunk on this server. And a couple of days ago MySQL started to experience some connection difficulties, it shows me connection errors sometimes, 'Can't connect to [local] MySQL server' and 'Too many connections' and so on. I have seen such errors on my local server, so i made all the same as i made earlier to fix it. Namely, set a larger value for a max_connections variable and check all connection settings and so on. Everything looks fine, all settings are alright and i am confused...can it be Splunk problem? Honestly, i have not worked with Splunk, so i do not know all its features. Maybe anyone knows?

0 Karma
1 Solution

AlfwineTrefield
Engager

Check whether the server is running on that host by executing telnet some_host 3306 and pressing the Enter key a couple of times. If there is a MySQL server running and listening to the port, you should get a response that includes the server's version number. If you get an error such as telnet: Unable to connect to remote host: Connection refused, then there is no server running on the given port.

Unfortunately this all what i found. Read also: https://answers.yahoo.com/question/index?qid=20140714042757AAqezy3
it might help

View solution in original post

AlfwineTrefield
Engager

Check whether the server is running on that host by executing telnet some_host 3306 and pressing the Enter key a couple of times. If there is a MySQL server running and listening to the port, you should get a response that includes the server's version number. If you get an error such as telnet: Unable to connect to remote host: Connection refused, then there is no server running on the given port.

Unfortunately this all what i found. Read also: https://answers.yahoo.com/question/index?qid=20140714042757AAqezy3
it might help

View solution in original post