[OpenSIPS-Users] segfault at the opensips 2.4.5 (Liviu Chircu)

Sun Mar 15 17:05:24 EST 2020

Do a backtrace and post the output please.

Outlook voor iOS<https://aka.ms/o0ukef> downloaden
________________________________
Van: Users <users-bounces at lists.opensips.org> namens Oleg Podguyko via Users <users at lists.opensips.org>
Verzonden: Sunday, March 15, 2020 5:32:58 PM
Aan: users at lists.opensips.org <users at lists.opensips.org>
Onderwerp: Re: [OpenSIPS-Users] segfault at the opensips 2.4.5 (Liviu Chircu)

Hi Liviu!

 I installed version 2.4.7 but continue to have problems with segfault…
These are the lines from opensips.log

Mar 15 15:53:01 xx-spx-2 /usr/sbin/opensips[25271]: CRITICAL:core:sig_usr: segfault in process pid: 25271, id: 11
Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[25258]: NOTICE:event_jsonrpc:destroy: destroy module ...
Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[30598]: NOTICE:core:main: version: opensips 2.4.7 (x86_64/linux)
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)
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
Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[30598]: NOTICE:signaling:mod_init: initializing module ...
Mar 15 15:53:02 xx-spx-2 /usr/sbin/opensips[30598]: NOTICE:event_jsonrpc:mod_init: initializing module ...

These are the lines from  /var/log/messages

Mar 15 15:53:01 xx-spx-2 kernel: opensips[25271]: segfault at 3836312e58 ip 00000000004fd108 sp 00007fff71716b20 error 4 in opensips[400000+1ae000]
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: [])
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}
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}
Mar 15 15:53:02 xx-spx-2 systemd: opensips.service: main process exited, code=exited, status=11/n/a
Mar 15 15:53:02 xx-spx-2 pkill: pkill: pidfile not valid
Mar 15 15:53:02 xx-spx-2 pkill: Try `pkill --help' for more information.
Mar 15 15:53:02 xx-spx-2 systemd: opensips.service: control process exited, code=exited status=1
Mar 15 15:53:02 xx-spx-2 systemd: Unit opensips.service entered failed state.
Mar 15 15:53:02 xx-spx-2 systemd: opensips.service failed.
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}
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}
Mar 15 15:53:02 xx-spx-2 systemd: opensips.service holdoff time over, scheduling restart.
Mar 15 15:53:02 xx-spx-2 systemd: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
Mar 15 15:53:02 xx-spx-2 systemd: Starting OpenSIPS is a very fast and flexible SIP (RFC3261) server...
Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: Mar 15 15:53:02 [30587] NOTICE:core:main: config file ok, exiting...
Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: Listening on
Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: udp: 192.168.9.38 [192.168.9.38]:5060
Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: sctp: 10.161.20.226 [10.161.20.226]:5060
Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: hep_udp: 192.168.9.38 [192.168.9.38]:6060
Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: Aliases:
Mar 15 15:53:02 xx-spx-2 opensips-m4cfg: sctp: XXX-XXXXX:5060
Mar 15 15:53:02 xx-spx-2 opensips: Listening on
Mar 15 15:53:02 xx-spx-2 opensips: udp: 192.168.9.38 [192.168.9.38]:5060
Mar 15 15:53:02 xx-spx-2 opensips: sctp: 10.161.20.226 [10.161.20.226]:5060
Mar 15 15:53:02 xx-spx-2 opensips: hep_udp: 192.168.9.38 [192.168.9.38]:6060
Mar 15 15:53:02 xx-spx-2 opensips: Aliases:
Mar 15 15:53:02 xx-spx-2 opensips: sctp: VMS-STAGE:5060
Mar 15 15:53:02 xx-spx-2 systemd: Started OpenSIPS is a very fast and flexible SIP (RFC3261) server.

What’s wrong?
Четверг, 12 марта 2020, 20:00 +03:00 от users-request at lists.opensips.org:

Send Users mailing list submissions to
users at lists.opensips.org</compose?To=users at lists.opensips.org>

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
users-request at lists.opensips.org</compose?To=users%2drequest at lists.opensips.org>

You can reach the person managing the list at
users-owner at lists.opensips.org</compose?To=users%2downer at lists.opensips.org>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."

Today's Topics:

   1. Re: segfault at the opensips 2.4.5 (Liviu Chircu)

----------------------------------------------------------------------

Message: 1
Date: Thu, 12 Mar 2020 18:43:42 +0200
From: Liviu Chircu <liviu at opensips.org</compose?To=liviu at opensips.org>>
To: OpenSIPS users mailling list <users at lists.opensips.org</compose?To=users at lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] segfault at the opensips 2.4.5
Message-ID: <de7e2af8-687e-58da-1804-5d42af260436 at opensips.org</compose?To=de7e2af8%2d687e%2d58da%2d1804%2d5d42af260436 at opensips.org>>
Content-Type: text/plain; charset=utf-8; format=flowed

On 12.03.2020 18:32, Oleg Podguyko via Users wrote:
>
> How opensips handles segfault?  And what needs to be done so that he
> does not die just like in the latter case?

Hi Oleg,

If one of the workers segfaults, OpenSIPS will perform a graceful
shutdown to the best of its ability, in the following order:

* each remaining SIP worker gets sent a high-priority termination job.
Once they finish processing the current SIP message, they will run this
job and terminate
* once all workers are stopped:
   * the dialog module will synchronize all in-memory dialogs to the
"dialog" table one last time
   * the usrloc module will synchronize all in-memory contacts to the
"location" table, etc.

Seeing that you are running 2.4.5, my advice would be to update to 2.4.7
nightly [1] as soon as possible.  You are missing roughly 1 year worth
of fixes, which is huge!

Best regards,

[1]: https://apt.opensips.org/packages.php?v=2.4

--
Liviu Chircu
www.twitter.com/liviuchircu<http://www.twitter.com/liviuchircu> | www.opensips-solutions.com<http://www.opensips-solutions.com>

OpenSIPS Summit, Amsterdam, May 2020
   www.opensips.org/events<http://www.opensips.org/events>

------------------------------

Subject: Digest Footer

_______________________________________________
Users mailing list
Users at lists.opensips.org</compose?To=Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

------------------------------

End of Users Digest, Vol 140, Issue 48
**************************************

--
Олег Подгуйко

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200315/bfceb182/attachment.html>