<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
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.<br>
<br>
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.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 04/06/15 16:55, Al S wrote:<br>
</div>
<blockquote cite="mid:BAY167-W105F236CB7B543FCE414E0BD4B30@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><font color="#000000" face="Arial, sans-serif"
size="3">Hi,</font>
<div><font color="#000000" face="Arial, sans-serif" size="3"><br>
</font></div>
<div><font face="Arial, sans-serif" size="3"><font
color="#000000">We have verified if MySQL s</font>erver is
offline when Kamailio is starting, Kamailio fails to start
correctly.</font></div>
<div><font face="Arial, sans-serif" size="3">Is this a bug?</font></div>
<div><font face="Arial, sans-serif" size="3"><br>
</font></div>
<div><font face="Arial, sans-serif" size="3"><br>
</font></div>
<div><font face="Arial, sans-serif" size="3">
<div><span style="font-size: 12pt;">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)</span></div>
<div>Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR:
<core> [db.c:320]: could not add connection to the
pool</div>
<div>Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR:
usrloc [dlist.c:518]: failed to open database connection</div>
<div>Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR:
registrar [reg_mod.c:472]: failed to register domain</div>
<div>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</div>
<div>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</div>
<div>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</div>
<div><br>
</div>
<div><br>
</div>
<div>We are running kamailio 3.3.7.</div>
<div><br>
</div>
</font></div>
<div><font face="Arial, sans-serif" size="3">Thanks,</font></div>
<div><font face="Arial, sans-serif" size="3">Al</font></div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Book: SIP Routing With Kamailio - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a></pre>
</body>
</html>