<HTML><BODY><div><div>Hi Liviu!</div><div> </div><div><div> I installed version 2.4.7 but continue to have problems with segfault…</div><div>These are the lines from opensips.log</div><div> </div><div>Mar 15 15:53:01 xx-spx-2 /usr/sbin/opensips[25271]: CRITICAL:core:sig_usr: segfault in process pid: 25271, id: 11<br>Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[25258]: NOTICE:event_jsonrpc:destroy: destroy module ...<br>Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[30598]: NOTICE:core:main: version: opensips 2.4.7 (x86_64/linux)<br>Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[30598]: WARNING:core:init_reactor_size: shrinking reactor size from 262144 (autodetected via rlimit) to 52428 (limited by memory of 10% from 16Mb)<br>Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[30598]: WARNING:core:init_reactor_size: use 'open_files_limit' to enforce other limit or increase pkg memory<br>Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[30598]: NOTICE:signaling:mod_init: initializing module ...<br>Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[30598]: NOTICE:event_jsonrpc:mod_init: initializing module ...</div><div> </div><div> </div><div> </div><div>These are the lines from /var/log/messages </div><div><br>Mar 15 15:53:01 xx-spx-2 kernel: opensips[25271]: segfault at 3836312e58 ip 00000000004fd108 sp 00007fff71716b20 error 4 in opensips[400000+1ae000]<br>Mar 15 15:53:01 xx-spx-2 spx: 2020-03-15T15:53:01.962556+00:00 [warning] <0.1372.0>@sf_osip_mi:handle_event/4:416 <0.20248.5575> connection down: closed (killed: [], unprocessed: [])<br>Mar 15 15:53:01 xx-spx-2 spx: 2020-03-15T15:53:01.975763+00:00 [warning] <0.1372.0>@sf_osip_mi:handle_event/4:426 connection failed, reason {shutdown,econnrefused}<br>Mar 15 15:53:01 xx-spx-2 spx: 2020-03-15T15:53:01.978919+00:00 [warning] <0.1372.0>@sf_osip_mi:handle_event/4:422 connection failed, reason {shutdown,econnrefused}<br>Mar 15 15:53:02 xx-spx-2 systemd: opensips.service: main process exited, code=exited, status=11/n/a<br>Mar 15 15:53:02 xx-spx-2 pkill: pkill: pidfile not valid<br>Mar 15 15:53:02 xx-spx-2 pkill: Try `pkill --help' for more information.<br>Mar 15 15:53:02 xx-spx-2 systemd: opensips.service: control process exited, code=exited status=1<br>Mar 15 15:53:02 xx-spx-2 systemd: Unit opensips.service entered failed state.<br>Mar 15 15:53:02 xx-spx-2 systemd: opensips.service failed.<br>Mar 15 15:53:02 xx-spx-2 spx: 2020-03-15T15:53:02.081992+00:00 [warning] <0.1372.0>@sf_osip_mi:handle_event/4:422 connection failed, reason {shutdown,econnrefused}<br>Mar 15 15:53:02 xx-spx-2 spx: 2020-03-15T15:53:02.184911+00:00 [warning] <0.1372.0>@sf_osip_mi:handle_event/4:422 connection failed, reason {shutdown,econnrefused}<br>Mar 15 15:53:02 xx-spx-2 systemd: opensips.service holdoff time over, scheduling restart.<br>Mar 15 15:53:02 xx-spx-2 systemd: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.<br>Mar 15 15:53:02 xx-spx-2 systemd: Starting OpenSIPS is a very fast and flexible SIP (RFC3261) server...<br>Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: Mar 15 15:53:02 [30587] NOTICE:core:main: config file ok, exiting...<br>Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: Listening on<br>Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: udp: 192.168.9.38 [192.168.9.38]:5060<br>Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: sctp: 10.161.20.226 [10.161.20.226]:5060<br>Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: hep_udp: 192.168.9.38 [192.168.9.38]:6060<br>Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: Aliases:<br>Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: sctp: XXX-XXXXX:5060<br>Mar 15 15:53:02 xx-spx-2 opensips: Listening on<br>Mar 15 15:53:02 xx-spx-2 opensips: udp: 192.168.9.38 [192.168.9.38]:5060<br>Mar 15 15:53:02 xx-spx-2 opensips: sctp: 10.161.20.226 [10.161.20.226]:5060<br>Mar 15 15:53:02 xx-spx-2 opensips: hep_udp: 192.168.9.38 [192.168.9.38]:6060<br>Mar 15 15:53:02 xx-spx-2 opensips: Aliases:<br>Mar 15 15:53:02 xx-spx-2 opensips: sctp: VMS-STAGE:5060<br>Mar 15 15:53:02 xx-spx-2 systemd: Started OpenSIPS is a very fast and flexible SIP (RFC3261) server.</div></div><div> </div><div> </div><div> </div><div>What’s wrong?</div><blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">Четверг, 12 марта 2020, 20:00 +03:00 от users-request@lists.opensips.org:<br> <div id=""><div class="js-helper js-readmsg-msg"><style type="text/css"></style><div><div id="style_15840324330583186945_BODY">Send Users mailing list submissions to<br><a href="/compose?To=users@lists.opensips.org">users@lists.opensips.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>or, via email, send a message with subject or body 'help' to<br><a href="/compose?To=users%2drequest@lists.opensips.org">users-request@lists.opensips.org</a><br><br>You can reach the person managing the list at<br><a href="/compose?To=users%2downer@lists.opensips.org">users-owner@lists.opensips.org</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Users digest..."<br><br><br>Today's Topics:<br><br> 1. Re: segfault at the opensips 2.4.5 (Liviu Chircu)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 12 Mar 2020 18:43:42 +0200<br>From: Liviu Chircu <<a href="/compose?To=liviu@opensips.org">liviu@opensips.org</a>><br>To: OpenSIPS users mailling list <<a href="/compose?To=users@lists.opensips.org">users@lists.opensips.org</a>><br>Subject: Re: [OpenSIPS-Users] segfault at the opensips 2.4.5<br>Message-ID: <<a href="/compose?To=de7e2af8%2d687e%2d58da%2d1804%2d5d42af260436@opensips.org">de7e2af8-687e-58da-1804-5d42af260436@opensips.org</a>><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>On 12.03.2020 18:32, Oleg Podguyko via Users wrote:<br>><br>> How opensips handles segfault? And what needs to be done so that he<br>> does not die just like in the latter case?<br><br>Hi Oleg,<br><br>If one of the workers segfaults, OpenSIPS will perform a graceful<br>shutdown to the best of its ability, in the following order:<br><br>* each remaining SIP worker gets sent a high-priority termination job. <br>Once they finish processing the current SIP message, they will run this<br>job and terminate<br>* once all workers are stopped:<br> * the dialog module will synchronize all in-memory dialogs to the<br>"dialog" table one last time<br> * the usrloc module will synchronize all in-memory contacts to the<br>"location" table, etc.<br><br>Seeing that you are running 2.4.5, my advice would be to update to 2.4.7<br>nightly [1] as soon as possible. You are missing roughly 1 year worth<br>of fixes, which is huge!<br><br>Best regards,<br><br>[1]: <a href="https://apt.opensips.org/packages.php?v=2.4" target="_blank">https://apt.opensips.org/packages.php?v=2.4</a><br><br>--<br>Liviu Chircu<br><a href="http://www.twitter.com/liviuchircu" target="_blank">www.twitter.com/liviuchircu</a> | <a href="http://www.opensips-solutions.com" target="_blank">www.opensips-solutions.com</a><br><br>OpenSIPS Summit, Amsterdam, May 2020<br> <a href="http://www.opensips.org/events" target="_blank">www.opensips.org/events</a><br><br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Users mailing list<br><a href="/compose?To=Users@lists.opensips.org">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br><br><br>------------------------------<br><br>End of Users Digest, Vol 140, Issue 48<br>**************************************</div></div></div></div></blockquote> <div> </div><div data-signature-widget="container"><div data-signature-widget="content"><div>--<br>Олег Подгуйко</div></div></div><div> </div></div></BODY></HTML>