You got a core file, logs show that:
2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: <core> [main.c:764]: handle_sigs(): core was generated
Locate it and send the full backtrace with gdb from it.
Cheers,
Daniel
On 27.11.19 16:03, Daniel Greenwald wrote:
I'm sorry you are correct, the version we are running is 5.2.5. I've just run ulimit -c unlimited to hopefully get a core dump next time since I don't see one in /var/lib/systemd/coredump/. Not sure if there is anything I need to do to get a coredump.
The log just shows:
2019-11-27T14:04:22.298010+00:00,ip-10-0-33-149: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 33
2019-11-27T14:04:22.299092+00:00,ip-10-0-33-149: ALERT: <core> [main.c:761]: handle_sigs(): child process 12674 exited by a signal 11
2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: <core> [main.c:764]: handle_sigs(): core was generated
2019-11-27T14:04:22.299564+00:00,ip-10-0-33-149: INFO: <core> [main.c:787]: handle_sigs(): terminating due to SIGCHLD
2019-11-27T14:04:22.299892+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.300298+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.300569+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.300820+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.301070+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.301315+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.301564+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.301823+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.302056+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.302277+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.302525+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.302773+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
2019-11-27T14:04:22.303020+00:00,ip-10-0-33-149: INFO: <core> [main.c:842]: sig_usr(): signal 15 received
On Wed, Nov 27, 2019 at 9:49 AM Daniel-Constantin Mierla <miconda@gmail.com> wrote:
If you use the repo listed at http://deb.kamailio.org/ , then it should be 5.2.5, and there is also option to install 5.2 branch debs built nightly.
Cheers,
Daniel
On 27.11.19 15:37, Daniel Greenwald wrote:
I'm using ubuntu packages, I believe 5.2.3 is latest?
On Wed, Nov 27, 2019 at 9:34 AM Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hello,
that log message is irrelevant for actual crash. Did you get core files? Or other log messages before the one you pasted?
You should upgrade first to latest 5.2.x, either 5.2.5 or latest branch 5.2.
Cheers,
Daniel
On 27.11.19 15:22, Daniel Greenwald wrote:
I'm seeing this in the log and kamailio is crashing every hour or so:CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 33/var/log/kamailio/kamailio.log
Any ideas? Should I emergency upgrade to 5.3.1?
_______________________________________________ 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 - April 27-29, 2020, in Berlin -- www.kamailioworld.com-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com