mysql error too many connections

[striker]

vicidial 2.4|version BUILD: 101008-0349 | single box | no extra hardwares| vicibox -redux 3.0.6 |
FYI : 3 agents | 1:1| 2g ram pentium dual core

screen -list

~ # screen -list
There are screens on:
7800.Timeclock (Detached)
2434.ASTlisten (Detached)
6120.Timeclock (Detached)
7488.Timeclock (Detached)
8546.Timeclock (Detached)
6703.Timeclock (Detached)
6888.Timeclock (Detached)
6817.Timeclock (Detached)
8407.Timeclock (Detached)
6095.Timeclock (Detached)
6290.Timeclock (Detached)
7289.Timeclock (Detached)
7636.Timeclock (Detached)
5939.Timeclock (Detached)
8271.Timeclock (Detached)
7072.Timeclock (Detached)
6611.Timeclock (Detached)
7117.Timeclock (Detached)
6261.Timeclock (Detached)
8078.Timeclock (Detached)
7381.Timeclock (Detached)
7820.Timeclock (Detached)
6790.Timeclock (Detached)
6441.Timeclock (Detached)
2429.ASTupdate (Detached)
6194.Timeclock (Detached)
7142.Timeclock (Detached)
2438.ASTVDremote (Detached)
5349.Timeclock (Detached)
6631.Timeclock (Detached)
6961.Timeclock (Detached)
5298.Timeclock (Detached)
5815.Timeclock (Detached)
8498.Timeclock (Detached)
5895.Timeclock (Detached)
5661.Timeclock (Detached)
6053.Timeclock (Detached)
7240.Timeclock (Detached)
7938.Timeclock (Detached)
7336.Timeclock (Detached)
7003.Timeclock (Detached)
7729.Timeclock (Detached)
6074.Timeclock (Detached)
6236.Timeclock (Detached)
5919.Timeclock (Detached)
8380.Timeclock (Detached)
7520.Timeclock (Detached)
8519.Timeclock (Detached)
7358.Timeclock (Detached)
6589.Timeclock (Detached)
8427.Timeclock (Detached)
8122.Timeclock (Detached)
6006.Timeclock (Detached)
7567.Timeclock (Detached)
7267.Timeclock (Detached)
8477.Timeclock (Detached)
8102.Timeclock (Detached)
5554.Timeclock (Detached)
7777.Timeclock (Detached)
6910.Timeclock (Detached)
6839.Timeclock (Detached)
2442.ASTfastlog (Detached)
8033.Timeclock (Detached)
7452.Timeclock (Detached)
2338.astshell20101202102311 (Detached)
6387.Timeclock (Detached)
5507.Timeclock (Detached)
8202.Timeclock (Detached)
7166.Timeclock (Detached)
6561.Timeclock (Detached)
7608.Timeclock (Detached)
6365.Timeclock (Detached)
7982.Timeclock (Detached)
6659.Timeclock (Detached)
7197.Timeclock (Detached)
7856.Timeclock (Detached)
6463.Timeclock (Detached)
2432.ASTsend (Detached)
7750.Timeclock (Detached)
7408.Timeclock (Detached)
6026.Timeclock (Detached)
5610.Timeclock (Detached)
7960.Timeclock (Detached)
8054.Timeclock (Detached)
8011.Timeclock (Detached)
7707.Timeclock (Detached)
6983.Timeclock (Detached)
6216.Timeclock (Detached)
7220.Timeclock (Detached)
5398.Timeclock (Detached)
7678.Timeclock (Detached)
8171.Timeclock (Detached)
7538.Timeclock (Detached)
6862.Timeclock (Detached)
6933.Timeclock (Detached)
5984.Timeclock (Detached)
7052.Timeclock (Detached)
5763.Timeclock (Detached)
8449.Timeclock (Detached)
7310.Timeclock (Detached)
7658.Timeclock (Detached)
7907.Timeclock (Detached)
5864.Timeclock (Detached)
6143.Timeclock (Detached)
8150.Timeclock (Detached)
7887.Timeclock (Detached)
2343.asterisk (Detached)
6408.Timeclock (Detached)
7589.Timeclock (Detached)
2436.ASTVDauto (Detached)
6481.Timeclock (Detached)
6520.Timeclock (Detached)
6315.Timeclock (Detached)
6683.Timeclock (Detached)
6769.Timeclock (Detached)
7431.Timeclock (Detached)
6542.Timeclock (Detached)
6167.Timeclock (Detached)
8347.Timeclock (Detached)
6748.Timeclock (Detached)
5454.Timeclock (Detached)
25635.ASTVDadapt (Detached)
5708.Timeclock (Detached)
7030.Timeclock (Detached)
124 Sockets in /var/run/screens/S-root.

[williamconley]

Code: Select all

nano /etc/astguiclient.conf

turn off the timeclock keepalive script

reboot

[gardo]

Looks nasty.

[striker]

as usual reboot done the trick

[boiken]

Im having the same error.
MySQL Error:Too many connections.

I restarted the server and the problem happens again and again


I have made a cluster with vicibox 6.0.2 :
1 DB
1 Web
4 Telephonys

as i have noticed on the DB server i get a lot of timeclock(detached) screens.
and the cpu load keeps rising.
now the cpu load is 390.0 370.8 345.0

Do i have to modify the /etc/astguiclient.conf and remove the 9 from the VARactive_keepalives => 1234689 ???
After this i have to make a reboot right .
Does this solve the problem permanently ??

What is the timeclock used for ?

Thank you

[mflorell]

It can sometimes be caused by running out of Linux ports as well, we just ran into a client system that had this issue last week.

[boiken]

i have just read a part on the Vicidial Multi-Server Poundteam manual this line :

Recommended setting for a dedicated DB server (No dialer):
(Source: email from Matt Florell)
Change VARactive_keepalives value to “X”

[williamconley]

The timeclock script relates to the timeclock page and automated processes required for logging out agents automatically, I presume.

# 9 - Timeclock auto logout

When an agent logs in, there is a link on the page for timeclock. I'd assume that if you do not use the timeclock you can turn this off without any repercussions. And if you use the timeclock but do not use the auto-logout features, once again you can still turn this off without a problem.

However: You can also access the timeclock screen to see what's happening.

Code: Select all

screen -r {scriptname}

You can also manually activate the timeclock script to see what's happening.

/usr/share/astguiclient/ADMIN_timeclock_auto_logout.pl --debugX

[boiken]

Now the changes i have done are these :

VARactive_keepalives

DB was 579E i changed to X
Web was 1234568 i changed to 123468
Tel 1 was 123468 i left as it is
Tel 2 was 123468 i changed to 12345678
Tel 3 was 123468 i left as it is

Now i see if the problem will happen again.It was crazy,because when i can today morning at work i saw the CPU load 1891.0 .....i had to reboot the server manually by keeping the power key pressed.

Will this solve my problem ?

Thanks Williamconley and MFlorell

[williamconley]

If you never had "9" in the keepalives, that problem should never have occurred in the first place.

Moving the active scripts from one server to another is not in any way guaranteed to resolve an issue.

Do you reboot your servers nightly?

Are your servers whitelisted? (IE: Only those with pre-approved IPs have access?)

If it occurs again, you could try deleting the timeclock script (if you're not using it). That would guarantee it never runs again, LOL.

[boiken]

The issue of TimeClock seems to be resolved after this changes.

From now and on, i made a cron /sbin/shutdown at 2:00 o'clock and i turn them on at 8: 30.

Yes the servers are whitelisted.

Another thing that happen after making this changes is that the server, Tel 2 (the one that have 5 and 7 in the keep alives) cant make call.
I work with SIP accounts and it returns a error like (subscriber absent) with all of my VoIP providers.

Is this normal ??
Can i move back the 5 and 7 keepalive to the DB server?

Thanks

[williamconley]

If you had never rebooted the servers before, that's actually not as surprising as it could have been otherwise. LOL

When you reboot the servers, ensure that the DB server is fully online before rebooting the other servers. They all rely on the DB server for information during their startup process. Try rebooting that "doesn't want to work" server again now that the DB is online. If that does not resolve it, there is likely another issue. We've had some issues with power failures that cause asterisk to "partially" start up recently.

Moving the "run on only one server" process among servers is a personal choice. As the instructions say, each of those should run on only one server. Doesn't much matter which one, but we do usually run them on the DB server.