<div dir="ltr">Hi Bogdan,<div><br></div><div>I had not, that's a new concept for me. I'll see what I can do. Changing from localhost to LAN IPs did solve the problem of processes not shutting down properly, however. Just the <a href="https://github.com/OpenSIPS/opensips/issues/126">already freed memory crash</a> remains.</div>
<div><br></div><div><br></div><div>- Jeff</div><div><br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Nov 14, 2013 at 5:29 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div text="#000000" bgcolor="#ffffff">
<tt>Hi Jeff,<br>
<br>
Have you tried to attach with gdb to the remaining process and to
get a backtrace ?<br>
<br>
Regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre><div><div class="h5">
<br>
On 11/12/2013 06:03 AM, Jeff Pyle wrote:
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>
<div dir="ltr">
<div>Hello,</div>
<div><br>
</div>
<div>In one particular configuration on 1.10 a standard
Opensips shutdown isn't ending all the processes...if
calls have passed through the system. If no calls have
passed, everything shuts down fine.</div>
<div><br>
</div>
<div>At one particular moment in time with everything
running I have:</div>
<div><br>
</div>
<div>
<div>Process:: ID=0 PID=26283 Type=attendant</div>
<div>Process:: ID=1 PID=26284 Type=MI XMLRPC</div>
<div>Process:: ID=2 PID=26285 Type=MI FIFO</div>
<div>Process:: ID=3 PID=26286 Type=RTPP timeout receiver</div>
<div>Process:: ID=4 PID=26287 Type=SIP receiver udp:<a href="http://127.0.0.1:5002" target="_blank">127.0.0.1:5002</a> </div>
<div>Process:: ID=5 PID=26288 Type=SIP receiver udp:<a href="http://127.0.0.1:5002" target="_blank">127.0.0.1:5002</a> </div>
<div>Process:: ID=6 PID=26289 Type=time_keeper</div>
<div>Process:: ID=7 PID=26290 Type=timer</div>
</div>
<div><br>
</div>
<div>But after /etc/init.d/opensips stop, it's always the
attendant (26283) and the second SIP receiver (26288)
hanging around. It requires a kill -9 to get them to go
away.</div>
<div><br>
</div>
<div>A full debug isn't showing anything obvious:</div>
<div><br>
</div>
<div>
<div>Nov 11 22:51:29 [26283] DBG:core:handle_sigs: SIGTERM
received, program terminates</div>
<div>Nov 11 22:51:29 [26289] INFO:core:sig_usr: signal 15
received</div>
<div>Nov 11 22:51:29 [26288] INFO:core:sig_usr: signal 15
received</div>
<div>Nov 11 22:51:29 [26290] INFO:core:sig_usr: signal 15
received</div>
<div>Nov 11 22:51:29 [26287] INFO:core:sig_usr: signal 15
received</div>
<div>
Nov 11 22:51:29 [26286] INFO:core:sig_usr: signal 15
received</div>
<div>Nov 11 22:51:29 [26285] INFO:core:sig_usr: signal 15
received</div>
<div>Nov 11 22:51:29 [26284] INFO:core:sig_usr: signal 15
received</div>
</div>
<div>
<br>
</div>
<div>But not everything has terminated:</div>
<div><br>
</div>
<div># ps ax | grep opensips</div>
<div>26283 ? S< 0:00 /usr/sbin/opensips -f
/etc/opensips/opensips.cfg -P
/var/run/opensips/opensips.pid -m 8 -M 1 -u opensips -g
opensips</div>
<div>26288 ? R< 0:21 /usr/sbin/opensips -f
/etc/opensips/opensips.cfg -P
/var/run/opensips/opensips.pid -m 8 -M 1 -u opensips -g
opensips</div>
<div><br>
</div>
<div>Any suggestions on where to continue investigating?</div>
<div><br>
</div>
<div><br>
</div>
<div>- Jeff</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div></div><pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</div>
</blockquote></div><br></div></div>