Hi @miconda We have 2 instances of this crash from two different servers. If it
helps I'm attaching the 2 backtraces. At the time of the crash we had the
following.
`# ----- siptrace params -----
modparam("siptrace", "duplicate_uri","sip:REDACTED:9060")
modparam("siptrace", "hep_mode_on",1)
modparam("siptrace", "hep_version", 2)
modparam("siptrace", "hep_capture_id", 11)
modparam("siptrace", "trace_to_database",0)
modparam("siptrace", "trace_flag",22)
modparam("siptrace", "trace_on", 1)
...
sip_trace("", "", "d");
`
And the syslog looked like this.
`Jul 1 11:37:21 REDACTED kernel: [19379376.973389] kamailio[20796]: segfault
at c0c0c110 ip 00007fb91985c3b7 sp 00007ffc3a691cd0 error 4 in
siptrace.so[7fb919831000+4e000]
Jul 1 11:37:21 REDACTED /usr/local/sbin/kamailio[20697]: ALERT: <core>
[main.c:788]: handle_sigs(): child process 20796 exited by a signal 11
Jul 1 11:37:21 REDACTED /usr/local/sbin/kamailio[20697]: ALERT: <core>
[main.c:791]: handle_sigs(): core was generated
Jul 1 11:37:21 REDACTED /usr/local/sbin/kamailio[20697]: INFO: <core>
[main.c:813]: handle_sigs(): terminating due to SIGCHLD`
Hopefully that is helpful. I'm also happy to provide any other info if needed.
Thanks!
[kamailio-bt-5-5-1-ServerA.txt](https://github.com/kamailio/kamailio/files/6748649/kamailio-bt-5-5-1-ServerA.txt)
[kamailio-bt-5-5-1-ServerB.txt](https://github.com/kamailio/kamailio/files/6748650/kamailio-bt-5-5-1-ServerB.txt)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2718#issuecomment-872266876_______________________________________________
Kamailio (SER) - Development Mailing List
[email protected]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
