Re: [OpenSIPS-Users] Opensips crash

Denis via Users Tue, 04 Apr 2017 05:20:07 -0700

p shm_block->first_frag

$1 = (struct qm_frag *) 0x7fdf6b9d44f8

p shm_block->last_frag_end

$2 = (struct qm_frag_end *) 0x7fe02899efd0

p mem_block->first_frag

$3 = (struct qm_frag *) 0x7fe029214508

p mem_block->last_frag_end

$4 = (struct qm_frag_end *) 0x7fe0691defe0

С уважением, Денис.

Best regards, Denis

04.04.2017, 14:51, "Bogdan-Andrei Iancu" <[email protected]>:

OK,please enter gdb and print:
    p shm_block->first_frag
    p shm_block->last_frag_end

    p mem_block->first_frag
    p mem_block->last_frag_end

Thanks,
Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html
On 04/04/2017 01:42 PM, Denis wrote:
Hello, Bogdan!

No, i cannot see in the log any messages you mentioned it your letter.
The situation dealing with crash had such stage.

1. I prepared to migrate to 2.2.3 from 2.2.2. But do not have a time to restart Opensips
2. As a result "i waited" when Opensips have crashed. During crash of 2.2.2 no core file has been generated, but Opensips has been restarted using cron.
3. After 2) Opensips became 2.2.3. It was working about 1 minute and crashed again, but in that time, core file has been generated and i attached information from it.
So, between 2) and 3) , as i mentioned above, there were no messages about memory, but i see many messages like
'WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled for 71500 ms
WARNING:core:timer_ticker: timer task <pike-clean> already scheduled for 72400 ms
WARNING:core:timer_ticker: timer task <nh-timer> already scheduled for 72400 ms
WARNING:core:timer_ticker: timer task <dlg-timer> already scheduled for 72400 ms
WARNING:core:timer_ticker: timer task <blcore-expire> already scheduled for 72400 ms'
and so on

As for about version

version: opensips 2.2.3 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
git revision: 7922417
main.c compiled on 06:29:28 Mar 23 2017 with gcc 5.4.0

--
С уважением, Денис.
Best regards, Denis

04.04.2017, 12:43, "Bogdan-Andrei Iancu" <[email protected]>:
Hello Denis,

Thank you for the report. Do you see any CRITICAL log just before the crash, something like:
"bad pointer 0xxxxxxxx (out of memory block!) - aborting"
?
If yes, please post here the exact line.

Also, do you use the latest OpenSIPS 2.2 from GIT repo ? (run "opensips -v")

Regards,
Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html
On 04/04/2017 10:58 AM, Denis via Users wrote:
Hello!

Server:: OpenSIPS (2.2.3 (x86_64/linux))

Thank you for any help.

P.S. Opensips has been compiled with QM_MALLOC and DBG_MALLOC flags

--
С уважением, Денис.
Best regards, Denis
_______________________________________________
Users mailing list
[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

Re: [OpenSIPS-Users] Opensips crash

Reply via email to