Edit /usr/local/opensips2.1/sbin/opensipsctl (line ~1878) and add the "ulimit" command before OpenSIPS starts, like so:

  ulimit -c unlimited
  if [ $SYSLOG = 1 ] ; then
    $OSIPSBIN -P $PID_FILE $STARTOPTIONS 1>/dev/null 2>/dev/null
  else
    $OSIPSBIN -P $PID_FILE -E $STARTOPTIONS
  fi

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 22.08.2016 16:25, Denis wrote:
Re: [OpenSIPS-Users] Opensips 2.1 crash Hello, Liviu!

Where does this option, i mean "ulimit -c unlimited", used? In opensipsctlrc "startoptions"?

When i tried restart Opensips i just used opensipsctl stop and start.

Without core analyze is there any suggestions about the problem (logs from opensipslog and syslog)?

/--
/mailto:[email protected] <mailto:[email protected]>


        Hi, Denis!
Thank you for reporting the crash! Unfortunately, OpenSIPS was not able to finish writing the corefile, which was truncated, as gdb points out:
/opensipscore/core  ... <F4><E0><E9><EB><E0>  >= 2158587904
The size of a corefile is equal to PKG+SHM memory size. Provided that you have enough disk space (> 2 GB), could you add a "ulimit -c unlimited" command in your startup script, before launching OpenSIPS? We should be able to obtain a clear backtrace afterwards.
Cheers,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 22.08.2016 14:20, Denis wrote:

        Opensips 2.1 crash Hello!

Today i have a big problem with my opensips.
I wanted to insert some modification to opensips.cfg but after restart opensips it has died and i was not able to resuscitate him at all. I have been saved only that i was planning to migrate from 2.1 to 2.2 and i already have opensips.cfg for 2.2 (db migration not spend much time).
I.e. only with 2.2. i could restore the service!

Changes that i made to configuration of 2.1:
i added
if (t_check_status("3[0-9][0-9]")) {
 t_reply("404","Not Found");
 exit;
}
to the failure route. That is all.

Everything i could gather about the problem is here: https://cloud.mail.ru/public/4Hhj/TcotVSA7w.
In syslog, at each time when i tried to restart Opensips, i saw
[ 140.300956] opensips[2688]: segfault at 0 ip 00007f69f92db144 sp 00007fff6328e7b8 error 4 in drouting.so[7f69f92d4000+46000]

And one more. I have two servers for running Opensips (active/standby). On both servers i have the same Opensips version. And on both servers, while restarting Opensips, i saw [ 140.300956] opensips[2688]: segfault at 0 ip 00007f69f92db144 sp 00007fff6328e7b8 error 4 in drouting.so[7f69f92d4000+46000]

Thank you for any help! I am afraid that there are some identical problems and with 2.2.

mailto:[email protected]


_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to