16 Dec
2011
16 Dec
'11
1:15 a.m.
Hello,
This is still happening - I've tweaked almost all kernel networking /
tcp and mysql configurations to see if I can isolate / resolve this matter
-- however it seems that this error is still persistent.
Any thoughts / suggestions? Move to postgresql? :P
Sincerely,
Brandon Armstead
On Sat, Dec 10, 2011 at 9:03 PM, Brandon Armstead <brandon(a)cryy.com> wrote:
Daniel,
Just confirming again - that I am still very very frequently seeing
these syslog events posted ---- I still am unable to locate any plausible
reason for such events occurring.
The crash that was happening was related to me moving a piece of code down
into the error block to see what the exact query was that it was failing on
(during query). It seemed most queries were related to dialog - however
not all. All queries were referencing the same database server (different
databases).
Any other ideas why this may be happening? Or any suggestions on how I
can further track it down / isolate the matter?
Look forward to hearing back from you, thanks!
Sincerely,
Brandon Armstead
On Thu, Dec 8, 2011 at 10:51 PM, Daniel-Constantin Mierla <
miconda(a)gmail.com> wrote:
Hello,
was it related to the item in the bug tracker (which I just closed due to
PM on tracker from you)? What was the cause for it?
Thanks,
Daniel
On 12/8/11 11:53 PM, Brandon Armstead wrote:
Timo,
Let me also add
max_allowed_packet = 512M.
On Thu, Dec 8, 2011 at 2:52 PM, Brandon Armstead <brandon(a)cryy.com>wrote;wrote:
Timo,
Thanks for this reference - I actually have been playing /
tweaking with various mentioned items in this reference earlier.
My current settings are as follows:
connect_timeout = 30
net_read_timeout = 180
net_write_timeout = 180
The issue still seems to be quite prevalent. I will say that the
amount of aborted connects currently (41) is way lower than the actual
amount of syslog lost connection errors.
Sincerely,
Brandon Armstead
On Thu, Dec 8, 2011 at 2:48 PM, Timo Reimann <sr(a)foo-lounge.de> wrote:
_______________________________________________
sr-dev mailing
listsr-dev@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla -- http://www.asipto.comhttp://linkedin.com/in/miconda --
http://twitter.com/miconda
Hey Brandon,
Am 08.12.2011 um 20:32 schrieb Brandon Armstead:
> I am very very very frequently seeing in logs "Lost connection
to MySQL Server" --- the MySQL server that it is connecting to is less than
1 ms away (essentially sitting in the same rack).
>
> Dec 8 19:21:15 /usr/local/sbin/kamailio[4149]: INFO: dialog
[dlg_db_handler.c:584]: trying to remove dialog [
c9d5ed0-13c4-4ee10778-92e3eb21-a90244c(a)XXX.XXX.XXX.XXX], update_flag
is 4
> Dec 8 19:21:16 /usr/local/sbin/kamailio[4149]: ERROR: db_mysql
[km_dbase.c:122]: driver error on query: Lost connection to MySQL server
during query
> Dec 8 19:21:16 /usr/local/sbin/kamailio[4149]: ERROR: <core>
[db_query.c:242]: error while submitting query
> Dec 8 19:21:16 /usr/local/sbin/kamailio[4149]: ERROR: dialog
[dlg_db_handler.c:598]: failed to delete database information
>
> *** MOD PARAM CONFIG ***
>
> # database ping
> modparam("db_mysql", "ping_interval", 150)
> modparam("db_mysql", "auto_reconnect", 1)
>
> Any thoughts on what may be happening? It seems the overall
connection (network) between the two servers is great.
The MySQL documentation enumerates a number of reasons:
http://dev.mysql.com/doc/refman/5.1/en/error-lost-connection.html
(This is the URL to MySQL version 5.1 documentation.)
You may want to check those for possible matchings.
Cheers,
--Timo