[SR-Users] Timer child process loosing MySQL connections

Henning Westerholt hw at kamailio.org
Mon Jun 18 21:50:52 CEST 2018


Am Montag, 18. Juni 2018, 11:15:43 CEST schrieb Tobias Lindgren:
> So I went with your suggestion to start a new Kamailio with just a few
> childs. Got the same issue after running for some time (again, with the
> timer process): 
> Jun 18 10:19:36  /usr/sbin/kamailio[25582]: DEBUG:
> db_cluster [dbcl_api.c:370]: db_cluster_raw_query(): executing db cluster
> raw query command Jun 18 10:19:36  /usr/sbin/kamailio[25582]: DEBUG:
> db_cluster [dbcl_api.c:371]: db_cluster_raw_query(): serial operation -
> cluster [k1] (9/0) Jun 18 10:19:36  /usr/sbin/kamailio[25582]: ERROR:
> db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query:
> Lost connection to MySQL server at 'waiting for initial communication
> packet', system error: 4 (2013) Jun 18 10:19:36  /usr/sbin/kamailio[25582]:
> ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting
> query Jun 18 10:19:36  /usr/sbin/kamailio[25582]: DEBUG: db_cluster
> [dbcl_api.c:371]: db_cluster_raw_query(): serial operation - failre on
> cluster [k1] (9/0) Jun 18 10:19:36  /usr/sbin/kamailio[25582]: DEBUG:
> db_cluster [dbcl_api.c:371]: db_cluster_raw_query(): serial operation -
> cluster [k1] (1/0)
> 
> Not really sure how perform a good debug beyond this point, any suggestions?

Hello Tobias,

I see. Regarding further debugging - not sure if this is easy feasible - what about just 
connecting the "debug" kamailio directly to the database without the firewall? If you still 
loosing connections in this setup, I would investigate the situation further on your side.

Do you use SSL? There has been a lengthy discussion with a similar issue at:
https://github.com/kamailio/kamailio/issues/406

It could be also something related to a machine with several network interfaces:
https://lists.kamailio.org/pipermail/sr-users/2015-October/090266.html

If this path does not bring you closer to a solution, I would try the debug kamailio against a 
different (maybe fresh installed) isolated database. Then I would try move the debug 
kamailio on a different (maybe fresh installed) machine. Basically just changing one thing 
at a time until the issue stops.

Another option would be to capture the TCP traffic of the debug kamailio against the 
database and look for strange things in the wireshark.

Best regards,

Henning


-- 
If you like my work in the Kamailio project, it would be great if you could consider 
supporting me on Patreon: https://www.patreon.com/henningw
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20180618/758ac317/attachment.html>


More information about the sr-users mailing list