11 Apr
2012
11 Apr
'12
12:46 p.m.
Daniel-Constantin Mierla writes:
the last commit should fix it, it was just pushed to
master. An inverted
condition was not properly done.
now sip proxy started using db_cluster, but i'm still getting errors to
syslog when i stopped higher priority mysql server at 192.98.102.13:
Apr 11 13:38:54 sip /usr/sbin/sip-proxy[1351]: ERROR: <core> [db_query.c:156]: error
while submitting query
Apr 11 13:38:54 sip /usr/sbin/sip-proxy[1349]: ERROR: db_mysql [km_dbase.c:122]: driver
error on query: Can't connect to MySQL server on '192.98.102.13' (115)
Apr 11 13:38:54 sip /usr/sbin/sip-proxy[1349]: ERROR: <core> [db_query.c:156]: error
while submitting query
Apr 11 13:38:54 sip /usr/sbin/sip-proxy[1349]: ERROR: db_mysql [km_dbase.c:122]: driver
error on query: Lost connection to MySQL server at 'reading initial communication
packet', system error: 111
Apr 11 13:38:54 sip /usr/sbin/sip-proxy[1349]: ERROR: <core> [db_query.c:127]: error
while submitting query
sip proxy does work by using lower priority mysql server.
so it looks like disabling of higher priority server is not working.
i have not added inactive_interval parameter, so the default 300 should
be in effect.
-- juha