Bogdan,<div>In the interest of the mailing list archives....</div><div><br></div><div>I increased my server memory from 2G to 4G and increased the SHM using the -m param on the cmd line to 2048 (!!). And the problems seem to have gone away.. opensipsctl fifo dr_reload does take about a minute to complete. It would be fantastic to see in the server logs "dr_reload complete!" :D</div>
<div><br></div><div>I thikn it was just suffering from serious memory starvation. Question.. are the route tables compiled out (dr_rules and dr_gateways) or are they seperate memory lookups (ie: if I add a dr_gateway, does my 1 million row table now become 2 million?)</div>
<div><br></div><div>Thanks,</div><div>Brett</div><div><br></div><div><div><br><div class="gmail_quote">On Thu, Jun 11, 2009 at 2:50 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Brett,<br>
<br>
What it happens is the attendant process spending too much time in doing shutdown - this trigger the CRITICAL message you see after 60 seconds. So if the shutdown is longer than 60 seconds, opensips will brutally stop with this error.<br>
<br>
Why it happens ? my guess is it takes longer than 60 secs to free from mem all the 1M of rules from drouting :)....This is the optimist guess. The pessimist one is maybe some end looping (bug?) happens and opensips never stops.....<div class="im">
<br>
<br>
Regards,<br>
Bogdan<br>
<br>
Brett Nemeroff wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
This may be a hint?<br>
Jun 9 09:32:31 voicefoxtelephony /usr/local/sbin/opensips[5358]: INFO:core:sig_usr: signal 15 received<br>
Jun 9 09:32:31 voicefoxtelephony /usr/local/sbin/opensips[5340]: INFO:core:sig_usr: signal 15 received<br>
Jun 9 09:32:31 voicefoxtelephony /usr/local/sbin/opensips[5338]: INFO:core:sig_usr: signal 15 received<br>
Jun 9 09:32:57 voicefoxtelephony ntpd[2123]: synchronized to 64.73.32.134, stratum 2<br>
Jun 9 09:33:31 voicefoxtelephony /usr/local/sbin/opensips[5326]: CRITICAL:core:sig_alarm_abort: BUG - shutdown timeout triggered, dying...<br>
<br>
I stopped the proc with opensipsctl stop<br>
<br>
<br></div><div class="im">
On Tue, Jun 9, 2009 at 9:31 AM, Brett Nemeroff <<a href="mailto:brett@nemeroff.com" target="_blank">brett@nemeroff.com</a> <mailto:<a href="mailto:brett@nemeroff.com" target="_blank">brett@nemeroff.com</a>>> wrote:<br>
<br>
This has actually just become a pretty serious issue for me....<br>
<br>
It seems that now when I restart opensips with opensipsctl<br>
stop/start one process hangs:<br>
ps ax|grep opensips<br>
4744 ? R 0:57 /usr/local/sbin/opensips -P<br>
/var/run/opensips.pid -m 512<br>
<br>
Which will eventually die in like 2-3 minutes.. but then I have to<br>
delete /var/run/opensips.pid<br>
<br>
Also, as of late, I'm getting the error that my dr_rules table is<br>
empty, which it certainly isn't..This all seems to be related to<br>
memory issues.. any ideas here??<br>
-Brett<br>
<br>
<br>
<br>
<br>
On Mon, Jun 8, 2009 at 9:15 PM, Brett Nemeroff <<a href="mailto:brett@nemeroff.com" target="_blank">brett@nemeroff.com</a><br></div><div class="im">
<mailto:<a href="mailto:brett@nemeroff.com" target="_blank">brett@nemeroff.com</a>>> wrote:<br>
<br>
management<br>
<br>
<br>
<br></div><div class="im">
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</div></blockquote>
<br>
</blockquote></div><br></div></div>