Hi all.<br><br> I've tried to update to Opensips 1.6.1, but encountered the following problem. Opensips starts successfully, but soon almost all it's processes die one by one and only two processes remain.<br>For example, if right after start we have:<br>
<br># ps ax | grep opens<br>26182 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26183 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26184 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>
26185 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26186 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26187 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26188 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>
26189 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26190 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26191 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26192 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>
26193 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26194 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26195 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26196 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>
26197 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26198 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26199 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26200 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>
26201 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26202 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26203 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26204 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>
26205 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26206 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26207 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26208 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>
<br> When processes die, we have only:<br><br>#ps ax | grep opens<br>26182 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br>26184 ? S 0:00 ./opensips -k 0x11110204 -u opensips<br><br> If I set debug=6, the following is written to /var/log/messages:<br>
<br>Dec 22 11:02:03 srv rtpproxy[17011]: INFO:rxmit_packets: caller's address filled in: <a href="http://195.182.195.206:1024">195.182.195.206:1024</a> (RTP)<br>Dec 22 11:02:03 srv opensips[26184]: Route 5 - NOTIFY<br>
Dec 22 11:02:05 srv opensips[26185]: Route 5 - PUBLISH<br>Dec 22 11:02:06 srv opensips[26183]: Route 5 - NOTIFY<br>Dec 22 11:02:06 srv opensips[26185]: Route 5 - NOTIFY<br>Dec 22 11:02:06 srv opensips[26185]: Route 5 - NOTIFY<br>
Dec 22 11:02:06 srv opensips[26186]: Route 5 - NOTIFY<br>Dec 22 11:02:06 srv opensips[26186]: Route 5 - NOTIFY<br>Dec 22 11:02:08 srv rtpproxy[17011]: INFO:handle_command: lookup on ports 36664/35096, session timer restarted<br>
Dec 22 11:02:08 srv rtpproxy[17011]: INFO:handle_command: pre-filling callee's address with <a href="http://87.251.142.50:5006">87.251.142.50:5006</a><br>Dec 22 11:02:08 srv opensips[26208]: CRITICAL:core:receive_fd: EOF on 13<br>
Dec 22 11:02:08 srv opensips[26182]: INFO:core:handle_sigs: child process 26186 exited by a signal 11<br>Dec 22 11:02:08 srv opensips[26182]: INFO:core:handle_sigs: core was not generated<br>Dec 22 11:02:08 srv opensips[26182]: INFO:core:handle_sigs: terminating due to SIGCHLD<br>
<br> As I see, the last message received by process with PID 26186 is NOTIFY, and then it crashes.<br><br>"Route 5 - NOTIFY" is in this block of configuration file:<br><br># SUBSCRIBE and PUBLISH Message Handling<br>
# --------------------------------------<br>route[5]<br>{<br> if (!t_newtran())<br> {<br> xlog("L_INFO", "Failed to create transaction\n");<br> sl_reply_error();<br> exit;<br>
}<br><br> if (is_method("PUBLISH"))<br> {<br> xlog("L_INFO", "Route 5 - PUBLISH \n");<br> handle_publish();<br> }<br> else if (is_method("SUBSCRIBE"))<br>
{<br> xlog("L_INFO", "Route 5 - SUBSCRIBE\n");<br> handle_subscribe();<br> }<br> else if (is_method("NOTIFY"))<br> {<br> xlog("L_INFO", "Route 5 - NOTIFY\n");<br>
t_reply("200", "OK");<br> exit;<br> }<br><br> exit;<br>}<br><br> In main routing logic:<br><br>if (method == "SUBSCRIBE" || method == "PUBLISH" || method == "NOTIFY")<br>
{<br> route(4);<br> return(0);<br>}<br><br> As I see, Opensips sets core dump limit, if it's turned off, but no core is produced (OS is CentOS 5.3).<br><br> What can be wrong? Version 1.6.0 did not crash like this.<br>