Hello,
at startup all needed components for proper functionality must be available. This was the design from the beginning with many modules. At runtime, Kamailio does the best to recover from fault situations. But it needs to start and have the init state properly build to detect anomalies afterwards.
Changing this behaviour requires to aproach each module one by one. For example, if usrloc is not able to load the location records at startup, then it doesn't know if an incoming register is an update or a new registration, so it has to keep sort of backlog in order to sync with database when it becomes available. Also, restriction such as max_contacts will be invalidated by an improper init state of usrloc module.
Cheers, Daniel
On 04/06/15 16:55, Al S wrote:
Hi,
We have verified if MySQL server is offline when Kamailio is starting, Kamailio fails to start correctly. Is this a bug?
Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: db_mysql [km_my_con.c:109]: driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: <core> [db.c:320]: could not add connection to the pool Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: usrloc [dlist.c:518]: failed to open database connection Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: registrar [reg_mod.c:472]: failed to register domain Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: <core> [route.c:1216]: fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:858 Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: <core> [route.c:1216]: fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:861 Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: <core> [route.c:1216]: fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:863
We are running kamailio 3.3.7.
Thanks, Al
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users