Hello,

either is a failed start of kamailio that gets blocked or something else is killing it, because the signal is 9 -- sigkill. The message from jsonrpcs is from start up, then nothing until the signal 9.

If it is at startup, maybe if you run with debug=3 can give you more hints about what happens there.

Cheers,
Daniel

On 13.09.18 21:00, Sergey Safarov wrote:
Is possible to restart kamailio when is critical errors is happens?

Now in log
```

Sep 13 18:50:38 ca-edm-sw3.phonebox.work sh[1171]: 81(85) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/85

Sep 13 18:52:21 ca-edm-sw3.phonebox.work sh[1171]: 0(1) ALERT: <core> [main.c:743]: handle_sigs(): child process 5 exited by a signal 9

Sep 13 18:52:21 ca-edm-sw3.phonebox.work sh[1171]: 0(1) ALERT: <core> [main.c:746]: handle_sigs(): core was not generated

Sep 13 18:52:21 ca-edm-sw3.phonebox.work sh[1171]: 0(1) ALERT: <core> [main.c:743]: handle_sigs(): child process 80 exited by a signal 9

Sep 13 18:52:21 ca-edm-sw3.phonebox.work sh[1171]: 0(1) ALERT: <core> [main.c:746]: handle_sigs(): core was not generated

Sep 13 18:52:21 ca-edm-sw3.phonebox.work sh[1171]: 0(1) ALERT: <core> [main.c:743]: handle_sigs(): child process 110 exited by a signal 9

Sep 13 18:52:21 ca-edm-sw3.phonebox.work sh[1171]: 0(1) ALERT: <core> [main.c:746]: handle_sigs(): core was not generated

```

Some of childs is died but main kamailio process is still active. SIP traffic is not processed because TCP socket is died.
When i core is generated i can force restart process.
But i cannot parse logs to catch such event. May exist other way?

Sergey  


_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com