astguiclient processes bring down mysql too many connection

[garfunct]

Have been running 3 boxes for couple of months.

1 http and mysql on centos

2 asterisk 1.2.17 load balanced

guess we must have changed something...

now astguiclient processes bring down mysql with too many connections

have tried max wait time in my.cnf and up max connections to 300 but really the only thing that stops mysql from becoming non functional is to turn of options
1,5 and 7 in astguiclient.conf

phones eventually ring on client end but not before interface times out...
really weird.

hopin someone can help

[williamconley]

The last time I had a sql crash on a vicidial install it was that sql didn't have room to run because the drive ran out of space. it looked like a sql problem, but "df" showed my hard drive was full. I had all my drive space taken up by log files. cleaned out the logs. *poof* system worked again.

may not be related, but i don't see any other responses and if it *is* related you could be up in 2 minutes.

Good luck.

[mcargile]

First off, I agree with williamconley, please make sure the parition where mysql is stored is not full. This can cause MySQL to crash.

Second, check that there is not something funny on the network. I once had a customer who's DNS server stopped resolving localhost to 127.0.0.1 (not your problem as you have a multi server setup). Had another customer in which it took three seconds to establish a connection to the DB even though the asterisk server and the DB were on the same switch. Come to find out they had a windows virus clogging their network.

If neither of those are the problem I would check that the scripts have not been altered in some way. Do a diff between source files and the ones that are running on the system. It is possible that there was file corruption or someone edited something they should not have.

[garfunct]

I have been looking at all these points and have currently found nothing wrong.

My guess is I have not looked hard enough however so i will be looking again..

Thnx for the support however.

[mflorell]

try starting mysql without name lookups:

/usr/local/mysql/bin/mysqld_safe --user=mysql --skip-name-resolve --skip-host-cache &

[garfunct]

consider this case closed the box was hacked...

any hooo gave me a chance to try the vicinow disk

and is great to see for users like ourselves

recommend it to all newbies and will try to post our experience on vicidialnow website