Page 1 of 1

mysql error

PostPosted: Wed Sep 01, 2010 4:41 pm
by kla
VERSION: 2.0.5-173
BUILD: 90320-0424
Asterisk 1.2.30.2
Multi-Server


we are getting this error "MySQL connect ERROR: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11)" when our 2nd shift is running with 100 agents dialing and if this error appeared the agents in our monitoring was on paused but to their side they are still talking to the customer. please help

this is the settings inside the my.cnf

[mysqld]
port=3306
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
skip-name-resolve
skip-host-cache
max_connections=200

[client]
port=3306
socket=/var/lib/mysql/mysql.sock

[mysql.server]
user=mysql
basedir=/var/lib

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid



thanks,

kla

PostPosted: Wed Sep 01, 2010 8:42 pm
by williamconley
when giving an error reading it is VERY important to give the error verbatim (thank you for that, it's quite helpful!) it is also helpful to tell us where you are seeing this error (Asterisk CLI? Manager Login? Agent Login?)

Please also post your method of installation.

the agents in our monitoring was on paused
are you saying that the agent who sees this error is then auto-paused? or are you seeing this on a screen somewhere?

when did this begin happening? (I get the impression that it only happens under heavy load, and otherwise the system is operating normally ... but i'd like confirmation on that as well)

What is the system load (from htop or Admin->Servers->[select server on which error occurs]) when this happens (on all the servers if possible)?

And the idea behind listing your Cluster information is not to simply state "multi-server", but to describe the nature of the multi-server installation. You can even give your local IP addresses for each to help with understanding as that is not critical information to be kept secret.

Since you have a multi-server installation, we'll also need to know how this relates to our error reading: which of the servers is the agent who gets paused logged in to, and what is the system load on THAT server when the error occurs?

No Digium
Sangoma Hardware
No Extra Software After Installation
model number for the sangoma hardware would also be appreciated (not likely to be related, but it never hurts to list it now and each time you post IN CASE it turns out to be related).