Re: [OpenSIPS-Users] opensips crash while using siprec module

[Răzvan Crainea]

Hi, Hitesh!

You are using both dialog and B2B for the same call - this is not 
supported in OpenSIPS. Moreover, SIPREC is not working with B2B.
So you either have a setup with dialog (where siprec can be enabled) or 
b2b (siprec is not available).


Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 8/29/22 17:15, Hitesh Menghani wrote:

Hi All,

opensips ver 2.4

Note: Same issue is there with opensips 3.3 ver

We are trying to use siprec module and observed a crash while processing 
200ok from remote while siprec module is being used.


Below is the opensips config snapshot for using siprec

if (is_method("INVITE")) {

   create_dialog();

           rtpproxy_engage();

   xlog("Engage SIPREC call recording to 
sip:10.57.1.110:5060  for $ci\n");


   
siprec_start_recording(sip:10.57.1.110:5060 );


       b2b_init_request("b2bua", 
sip:sa@10.57.1.198:5060 );


   do_accounting("log");

   exit;

    }

Also find below backtrace of a crash –

#0  0x004dcc1a in parse_headers (msg=0x,

 flags=18446744073709551615, next=0) at parser/msg_parser.c:302

302    parser/msg_parser.c: No such file or directory.

Missing separate debuginfos, use: debuginfo-install 
glibc-2.17-157.el7.x86_64 libuuid-2.23.2-33.el7.x86_64 
libxml2-2.9.1-6.el7_2.3.x86_64 xz-libs-5.2.2-1.el7.x86_64 
zlib-1.2.7-17.el7.x86_64


(gdb) bt

#0  0x004dcc1a in parse_headers (msg=0x,

 flags=18446744073709551615, next=0) at parser/msg_parser.c:302

#1  0x7f8bb9f271e1 in get_body ()

    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/siprec.so

#2  0x7f8bb9f2a430 in tm_start_recording ()

    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/siprec.so

#3  0x7f8bbc3dbd89 in run_trans_callbacks ()

    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so

#4  0x7f8bbc3dc0af in run_trans_callbacks_locked ()

    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so

#5  0x7f8bbc3a90de in _reply_light ()

    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so

#6  0x7f8bbc3ad4d2 in t_reply_with_body ()

    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so

#7  0x7f8bbae25de3 in b2b_send_reply ()

    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/b2b_entities.so

#8  0x7f8bbabf5931 in b2b_logic_notify_reply ()

---Type  to continue, or q  to quit---q

Thanks,

Hitesh


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] opensips crash while using siprec module

[Hitesh Menghani]

Hi All,

opensips ver 2.4

Note: Same issue is there with opensips 3.3 ver

We are trying to use siprec module and observed a crash while processing 200ok 
from remote while siprec module is being used.

Below is the opensips config snapshot for using siprec

if (is_method("INVITE")) {
  create_dialog();
  rtpproxy_engage();
  xlog("Engage SIPREC call recording to 
sip:10.57.1.110:5060 for $ci\n");
  siprec_start_recording(sip:10.57.1.110:5060);
  b2b_init_request("b2bua", 
sip:sa@10.57.1.198:5060);
  do_accounting("log");
  exit;
   }

Also find below backtrace of a crash -

#0  0x004dcc1a in parse_headers (msg=0x,
flags=18446744073709551615, next=0) at parser/msg_parser.c:302
302parser/msg_parser.c: No such file or directory.
Missing separate debuginfos, use: debuginfo-install glibc-2.17-157.el7.x86_64 
libuuid-2.23.2-33.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 
xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-17.el7.x86_64
(gdb) bt
#0  0x004dcc1a in parse_headers (msg=0x,
flags=18446744073709551615, next=0) at parser/msg_parser.c:302
#1  0x7f8bb9f271e1 in get_body ()
   from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/siprec.so
#2  0x7f8bb9f2a430 in tm_start_recording ()
   from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/siprec.so
#3  0x7f8bbc3dbd89 in run_trans_callbacks ()
   from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so
#4  0x7f8bbc3dc0af in run_trans_callbacks_locked ()
   from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so
#5  0x7f8bbc3a90de in _reply_light ()
   from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so
#6  0x7f8bbc3ad4d2 in t_reply_with_body ()
   from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so
#7  0x7f8bbae25de3 in b2b_send_reply ()
   from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/b2b_entities.so
#8  0x7f8bbabf5931 in b2b_logic_notify_reply ()
---Type  to continue, or q  to quit---q

Thanks,
Hitesh


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] OpenSIPs Crash on reporting delay.

[Diptesh Patel]

Hello,

My OpenSIPS crashed once in heavy load. I don't know the exact reason and
it does not usually happen. can you please suggest what is wrong with it?

Please find gdb backtrace in attachment. Let me know If you need anything
else.

version: opensips 2.4.1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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, sigio_rt, select.
git revision: 5d042cffc
main.c compiled on 02:09:27 Feb 24 2020 with gcc 4.8.5

Thanks & Regards
*Diptesh Patel*
Software Developer
Ecosmob Technologies Ltd,
Ahmedabad
Mo:*+919898962659*

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.



*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-115.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/local/sbin/opensips...done.
[New LWP 13167]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/sbin/opensips -P 
/var/run/opensips/opensips.pid -f /usr/local/etc/op'.
Program terminated with signal 11, Segmentation fault.
#0  0x00462bbf in log_expiry (func_info=0x60fc5a "msg processing", 
tcp=0, dbg_len=1056, 
extra_dbg=0x89e5a0  "INVITE 
sip:6042352637@216.123.235.115:5060;user=phone SIP/2.0\r\nVia: SIP/2.0/UDP 
209.91.94.6:5060;branch=z9hG4bKketago30306suciqkm90.1\r\nFrom: \"PRABHJOT 
KAUR\", 
time_diff=60635)
at ut.h:1085
1085LM_WARN("#%i is a module action 
: %s - %dus - line %d\n",i+1,
Missing separate debuginfos, use: debuginfo-install 
MariaDB-shared-10.1.43-1.el7.centos.x86_64 glibc-2.17-292.el7.x86_64 
gmp-6.0.0-15.el7.x86_64 gnutls-3.3.29-9.el7_6.x86_64 
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-37.el7_7.2.x86_64 
libcom_err-1.42.9-16.el7.x86_64 libffi-3.0.13-18.el7.x86_64 
libgcc-4.8.5-39.el7.x86_64 libgcrypt-1.5.3-14.el7.x86_64 
libgpg-error-1.12-3.el7.x86_64 libmicrohttpd-0.9.33-2.el7.x86_64 
librabbitmq-0.8.0-2.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 
libstdc++-4.8.5-39.el7.x86_64 libtasn1-4.10-1.el7.x86_64 
libxml2-2.9.1-6.el7_2.3.x86_64 nettle-2.7.1-8.el7.x86_64 
openssl-libs-1.0.2k-19.el7.x86_64 p11-kit-0.23.5-3.el7.x86_64 
pcre-8.32-17.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64
(gdb) bt full
#0  0x00462bbf in log_expiry (func_info=0x60fc5a "msg processing", 
tcp=0, dbg_len=1056, 
extra_dbg=0x89e5a0  "INVITE 
sip:6042352637@216.123.235.115:5060;user=phone SIP/2.0\r\nVia: SIP/2.0/UDP 
209.91.94.6:5060;branch=z9hG4bKketago30306suciqkm90.1\r\nFrom: \"PRABHJOT 
KAUR\", 
time_diff=60635)
at ut.h:1085
param = {s = 0x5f639328 , len = 
100387}
list = 
i = 0
func_str = {s = 0x60fca1 "source", len = 6}
time_str = {s = 0x63935d "time", len = 4}
extra_str = {s = 0x61a8a6 "extra", len = 5}
#1  receive_msg (
buf=0x89e5a0  "INVITE 
sip:6042352637@216.123.235.115:5060;user=phone SIP/2.0\r\nVia: SIP/2.0/UDP 
209.91.94.6:5060;branch=z9hG4bKketago30306suciqkm90.1\r\nFrom: \"PRABHJOT 
KAUR\", 
rcv_info=rcv_info@entry=0x7ffeb7285fa0, 

[OpenSIPS-Users] opensips crash help

[Vic Jolin]

Helo,

Can anyone help me know why opensips crashing? The last core dump backtrace
is as follows...


#0  0x7f6cc4be5786 in shm_str_dup (src=0x7f6d78ed64d8, dst=) at ../../ut.h:736
No locals.
#1  dlg_clone_callee_leg (dlg=dlg@entry=0x7f6d72b45050,
cloned_leg_idx=cloned_leg_idx@entry=6) at dlg_hash.c:381
leg = 
src_leg = 0x7f6d78ed6430
__FUNCTION__ = "dlg_clone_callee_leg"
#2  0x7f6cc4bc0789 in push_reply_in_dialog (mangled_to=0x7ffe582be640,
mangled_from=0x7ffe582be630, dlg=, t=,
rpl=) at dlg_handlers.c:378
tag = {
  s = 0x9fa969  "9vSgcj14FDcgK\r\
ni:79d3534763616c6c035dce54@204.12.243.26\r\nCSeq:2140 INVITE\r\nm:<
sip:121715033630830@68.232.175.241;did=64f.ada21875>\r\nUser-Agent:VeriSwitch
3.1\r\nAccept:application/sdp\r\nAllow:INVITE,ACK,"..., len = 13}
contact = {s = 0x0, len = 0}
rr_set = {s = 0x0, len = 0}
skip_rrs = 0
cseq_no = 
leg = 6
#3  dlg_onreply (t=, type=, param=) at dlg_handlers.c:482
rpl = 
req = 
dlg = 
new_state = 0
old_state = 10463593
unref = 0
event = 
mangled_from = {s = 0x0, len = 0}
mangled_to = {s = 0x0, len = 0}
req_out_buff = 
__FUNCTION__ = "dlg_onreply"
#4  0x7f6cc8e1114d in run_trans_callbacks (type=type@entry=8,
trans=trans@entry=0x7f6d77bf7bd8, req=,
rpl=rpl@entry=0x7f6d86b01b18,
code=code@entry=180) at t_hooks.c:209
params = {req = 0x7f6d771a42b0, rpl = 0x7f6d86b01b18, code = 180,
param = 0x7f6d11618c88, extra1 = 0x0, extra2 = 0x0}
cbp = 0x7f6d11618c78
backup = 0x9d3b18 
trans_backup = 0x7f6d77bf7bd8
__FUNCTION__ = "run_trans_callbacks"
#5  0x7f6cc8dc4cc0 in relay_reply (t=0x7f6d77bf7bd8, p_msg=, branch=5, msg_status=180, cancel_bitmap=0x7ffe582be8b0) at
t_reply.c:1275
relay = 5
save_clone = 0
buf = 0x0
res_len = 0
relayed_code = 0
relayed_msg = 0x7f6d86b01b18
bm = {to_tag_val = {s = 0x7f6d86b01b18 "=\345\036", len =
-203238}}
totag_retr = 0
uas_rb = 0x7f6d77bf7cd8
cb_s = {s = 0x0, len = 0}
text = {s = 0x7f6d86b01b18 "=\345\036", len = 0}
__FUNCTION__ = "relay_reply"
#6  0x7f6cc8dc890c in reply_received (p_msg=0x7f6d86b01b18) at
t_reply.c:1638
msg_status = 180
last_uac_status = 100
branch = 5
reply_status = 
timer = 0
cancel_bitmap = 0
uac = 0x7f6d77bf87b0
t = 0x7f6d77bf7bd8
backup_list = 
has_reply_route = 
__FUNCTION__ = "reply_received"
#7  0x004997cd in forward_reply (msg=msg@entry=0x7f6d86b01b18) at
forward.c:499
new_buf = 0x0
---Type  to continue, or q  to quit---
to = 0x0
new_len = 2259688216
mod = 0x7f6d86a98588
proto = 
id = 0
send_sock = 
s = 
len = 
__FUNCTION__ = "forward_reply"
#8  0x00470b67 in receive_msg (
buf=0x9fa820  "SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP
104.237.1.164:5060;branch=z9hG4bK0052.21e14e5.5\r\nVia: SIP/2.0/UDP
204.12.243.26:5060;branch=z9hG4bK48d9fd741d6c5597\r\nRecord-Route:
,
rcv_info=rcv_info@entry=0x7ffe582bea70,
existing_context=existing_context@entry=0x0, flags=flags@entry=0) at
receive.c:259
ctx = 0x7f6d86b00db8
msg = 0x7f6d86b01b18
start = {tv_sec = 24, tv_usec = 13858426}
rc = 3
in_buff = {
  s = 0x9fa820  "SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP
104.237.1.164:5060;branch=z9hG4bK0052.21e14e5.5\r\nVia: SIP/2.0/UDP
204.12.243.26:5060;branch=z9hG4bK48d9fd741d6c5597\r\nRecord-Route:
,
bytes_read=) at net/proto_udp/proto_udp.c:184
ri = {src_ip = {af = 2, len = 4, u = {addrl = {4054837316, 0},
addr32 = {4054837316, 0, 0, 0}, addr16 = {59460, 61871, 0, 0, 0, 0, 0, 0},
addr = "D\350\257\361", '\000' }}, dst_ip = {af = 2, len
= 4, u = {
  addrl = {2751589736, 0}, addr32 = {2751589736, 0, 0, 0},
addr16 = {60776, 41985, 0, 0, 0, 0, 0, 0}, addr = "h\355\001\244", '\000'
}}, src_port = 5060, dst_port = 5060, proto = 1,
proto_reserved1 = 0,
  proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data =
"\023\304D\350\257\361\000\000\000\000\000\000\000"}, sin = {sin_family =
2, sin_port = 50195, sin_addr = {s_addr = 4054837316},
  sin_zero = "\000\000\000\000\000\000\000"}, sin6 =
{sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4054837316, sin6_addr
= {__in6_u = {__u6_addr8 =
"\000\000\000\000\000\000\000\000\377\377\377\377\000\000\000",
  __u6_addr16 = {0, 0, 0, 0, 65535, 65535, 0, 0},
__u6_addr32 = {0, 0, 4294967295, 0}}}, sin6_scope_id = 1}}, bind_address =
0x7f6d86a97cf8}
len = 
buf = "SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP
104.237.1.164:5060;branch=z9hG4bK0052.21e14e5.5\r\nVia:
SIP/2.0/UDP 204.12.243.26:5060;branch=z9hG4bK48d9fd741d6c5597\r\nRecord-Route:

msg = {
  s = 0x9fa820  "SIP/2.0 

[OpenSIPS-Users] Opensips crash while connecting mariadb

[Virendra Bhati]

Dear Team,

We are using opensips 3.0.1 with mariadb 10.4.8 . We are facing issue at
starting opensips. As opensips crash with below given message:

Oct 15 03:27:17 [22849] DBG:core:find_mod_export: found  in
module db_mysql [/usr/local/lib64/opensips/modules/]
Oct 15 03:27:17 [22849] DBG:core:db_bind_mod: using db bind api for db_mysql
Oct 15 03:27:17 [22849] DBG:core:db_do_init: connection 0x7fba0e093510 not
found in pool
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno:
2000

I have attached logs and backtrace from core  so please provide your
suggestions. Please note credentials given in db_url are working while
using from mysql client


--
Regards
Virendra Bhati
Lead- Architecture and Software Solutions
Oct 15 03:27:17 [22849] INFO:core:evi_publish_event: Registered event 

Oct 15 03:27:17 [22849] DBG:core:find_cmd_export_t: found  in module 
tm [/usr/local/lib64/opensips/modules/]
Oct 15 03:27:17 [22849] DBG:core:find_cmd_export_t: found  in module 
rr [/usr/local/lib64/opensips/modules/]
Oct 15 03:27:17 [22849] DBG:core:find_mod_export: found  in module 
db_mysql [/usr/local/lib64/opensips/modules/]
Oct 15 03:27:17 [22849] DBG:core:db_bind_mod: using db bind api for db_mysql
Oct 15 03:27:17 [22849] DBG:core:db_do_init: connection 0x7fba0e093510 not 
found in pool
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000

Got ERROR: "InnoDB: Operating system error number 11 in a file operation." 
errno: 2000
Got ERROR: "InnoDB: Error number 11 means 'Resource temporarily unavailable'" 
errno: 2000
Got ERROR: "InnoDB: Cannot open datafile '/var/lib/mysql/ibdata1'" errno: 2000
Got ERROR: "InnoDB: Could not open or create the system tablespace. If you 
tried to add new data files to the system tablespace, and it failed here, you 
should now edit innodb_data_file_path in my.cnf back to what it was, and remove 
the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote 
those files full of zeros, but did not yet use them in any way. But be careful: 
do not remove old data files which contain your precious data!" errno: 2000
Got ERROR: "InnoDB: Plugin initialization aborted with error Cannot open a 
file" errno: 2000
Got ERROR: "Plugin 'InnoDB' init function returned error." errno: 2000
Got ERROR: "Plugin 'InnoDB' registration as a STORAGE ENGINE failed." errno: 
2000
Got ERROR: "unknown: Can't lock aria control file 
'/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 
30 seconds" errno: 2000



^C^CGot ERROR: "unknown: Got error 'Could not get an exclusive lock; file is 
probably in use by another process' when trying to use aria control file 
'/var/lib/mysql/aria_log_control'" errno: 2000
Got ERROR: "Plugin 'Aria' init function returned error." errno: 2000
Got ERROR: "Plugin 'Aria' registration as a STORAGE ENGINE failed." errno: 2000
Got ERROR: "Unknown/unsupported storage engine: InnoDB" errno: 2000
 DBG:db_mysql:db_mysql_connect: opening connection: 
mysql://:@localhost/cc_master
CRITICAL:core:sig_usr: segfault in attendant (starter) process!
DBG:core:restore_segv_handler: restoring SIGSEGV handler...
 DBG:core:restore_segv_handler: successfully restored system SIGSEGV handler
^CSegmentation fault (core dumped)

(gdb) bt full
#0  intern_plugin_lock (lex=0x0, state_mask=14, rc=0x0)
at /usr/src/debug/MariaDB-10.3.18/src_0/sql/sql_plugin.cc:948
pi = 0x0
#1  plugin_thdvar_init (thd=0x28af578) at 
/usr/src/debug/MariaDB-10.3.18/src_0/sql/sql_plugin.cc:3155
old_table_plugin = 0x0
old_tmp_table_plugin = 0x0
old_enforced_table_plugin = 0x0
#2  0x7fc7d58722b1 in THD::init (this=this@entry=0x28af578)
at /usr/src/debug/MariaDB-10.3.18/src_0/sql/sql_class.cc:1177
No locals.
#3  0x7fc7d587310a in THD::THD (this=0x28af578, id=, 
is_wsrep_applier=)
at /usr/src/debug/MariaDB-10.3.18/src_0/sql/sql_class.cc:798
tmp = 
#4  0x7fc7d57f2bdc in create_embedded_thd 
(client_flag=client_flag@entry=-2143837683)
at /usr/src/debug/MariaDB-10.3.18/src_0/libmysqld/lib_sql.cc:685
thd = 0x7fff689c20b0
#5  0x7fc7d57fa1e4 in mysql_real_connect (mysql=0x7fc7da7190b0, 
host=, user=, 
passwd=, db=0x7fc7da717620 "cc_master", port=port@entry=0, 
unix_socket=unix_socket@entry=0x0, 
client_flag=2151129613, client_flag@entry=2147549184)
at /usr/src/debug/MariaDB-10.3.18/src_0/libmysqld/libmysqld.c:179
name_buff = 

[OpenSIPS-Users] Opensips crash while connecting mariadb

[RAVI bhatt]

Hello all,
i am using opensips 3.0.1 with mariadb 10.4.8 and i am facing issue  in
starting opensips. As opensips crash with below given message:
ct 15 03:27:17 [22849] DBG:core:find_mod_export: found  in
module db_mysql [/usr/local/lib64/opensips/modules/]
Oct 15 03:27:17 [22849] DBG:core:db_bind_mod: using db bind api for db_mysql
Oct 15 03:27:17 [22849] DBG:core:db_do_init: connection 0x7fba0e093510 not
found in pool
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno:
2000

i have attached logs and back  trace from core  so please provide your
suggestions.
please note credentials given in db_url are working while using from msyql
client

Thanks in advance.
Ravindra Bhatt
Oct 15 03:27:17 [22849] INFO:core:evi_publish_event: Registered event 

Oct 15 03:27:17 [22849] DBG:core:find_cmd_export_t: found  in module 
tm [/usr/local/lib64/opensips/modules/]
Oct 15 03:27:17 [22849] DBG:core:find_cmd_export_t: found  in module 
rr [/usr/local/lib64/opensips/modules/]
Oct 15 03:27:17 [22849] DBG:core:find_mod_export: found  in module 
db_mysql [/usr/local/lib64/opensips/modules/]
Oct 15 03:27:17 [22849] DBG:core:db_bind_mod: using db bind api for db_mysql
Oct 15 03:27:17 [22849] DBG:core:db_do_init: connection 0x7fba0e093510 not 
found in pool
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000
Got ERROR: "InnoDB: Unable to lock /var/lib/mysql/ibdata1 error: 11" errno: 2000

Got ERROR: "InnoDB: Operating system error number 11 in a file operation." 
errno: 2000
Got ERROR: "InnoDB: Error number 11 means 'Resource temporarily unavailable'" 
errno: 2000
Got ERROR: "InnoDB: Cannot open datafile '/var/lib/mysql/ibdata1'" errno: 2000
Got ERROR: "InnoDB: Could not open or create the system tablespace. If you 
tried to add new data files to the system tablespace, and it failed here, you 
should now edit innodb_data_file_path in my.cnf back to what it was, and remove 
the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote 
those files full of zeros, but did not yet use them in any way. But be careful: 
do not remove old data files which contain your precious data!" errno: 2000
Got ERROR: "InnoDB: Plugin initialization aborted with error Cannot open a 
file" errno: 2000
Got ERROR: "Plugin 'InnoDB' init function returned error." errno: 2000
Got ERROR: "Plugin 'InnoDB' registration as a STORAGE ENGINE failed." errno: 
2000
Got ERROR: "unknown: Can't lock aria control file 
'/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 
30 seconds" errno: 2000



^C^CGot ERROR: "unknown: Got error 'Could not get an exclusive lock; file is 
probably in use by another process' when trying to use aria control file 
'/var/lib/mysql/aria_log_control'" errno: 2000
Got ERROR: "Plugin 'Aria' init function returned error." errno: 2000
Got ERROR: "Plugin 'Aria' registration as a STORAGE ENGINE failed." errno: 2000
Got ERROR: "Unknown/unsupported storage engine: InnoDB" errno: 2000
 DBG:db_mysql:db_mysql_connect: opening connection: 
mysql://:@localhost/cc_master
CRITICAL:core:sig_usr: segfault in attendant (starter) process!
DBG:core:restore_segv_handler: restoring SIGSEGV handler...
 DBG:core:restore_segv_handler: successfully restored system SIGSEGV handler
^CSegmentation fault (core dumped)

(gdb) bt full
#0  intern_plugin_lock (lex=0x0, state_mask=14, rc=0x0)
at /usr/src/debug/MariaDB-10.3.18/src_0/sql/sql_plugin.cc:948
pi = 0x0
#1  plugin_thdvar_init (thd=0x28af578) at 
/usr/src/debug/MariaDB-10.3.18/src_0/sql/sql_plugin.cc:3155
old_table_plugin = 0x0
old_tmp_table_plugin = 0x0
old_enforced_table_plugin = 0x0
#2  0x7fc7d58722b1 in THD::init (this=this@entry=0x28af578)
at /usr/src/debug/MariaDB-10.3.18/src_0/sql/sql_class.cc:1177
No locals.
#3  0x7fc7d587310a in THD::THD (this=0x28af578, id=, 
is_wsrep_applier=)
at /usr/src/debug/MariaDB-10.3.18/src_0/sql/sql_class.cc:798
tmp = 
#4  0x7fc7d57f2bdc in create_embedded_thd 
(client_flag=client_flag@entry=-2143837683)
at /usr/src/debug/MariaDB-10.3.18/src_0/libmysqld/lib_sql.cc:685
thd = 0x7fff689c20b0
#5  0x7fc7d57fa1e4 in mysql_real_connect (mysql=0x7fc7da7190b0, 
host=, user=, 
passwd=, db=0x7fc7da717620 "cc_master", port=port@entry=0, 
unix_socket=unix_socket@entry=0x0, 
client_flag=2151129613, client_flag@entry=2147549184)
at /usr/src/debug/MariaDB-10.3.18/src_0/libmysqld/libmysqld.c:179
name_buff = "\200\314|\326\307\177\000\000\060!\234h\377\177\000\000 

Re: [OpenSIPS-Users] opensips crash

[volga629]

And another one for udp.

[root@aitossbc03 ccpp-2018-08-15-23:31:53.377618-11025]# gdb coredump
GNU gdb (GDB) Fedora 8.0.1-36.fc27
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show 
copying"

and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
[New LWP 11025]
Reading symbols from /usr/sbin/opensips...Reading symbols from 
/usr/lib/debug/usr/sbin/opensips-3.0.0.b33b7a7e7-2.fc27.x86_64.debug...done.

done.

warning: Ignoring non-absolute filename: 
Missing separate debuginfo for linux-vdso.so.1
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/f9/61d796c26168fae4f7c8c3d20d229ec61e97a7
Missing separate debuginfo for 
/usr/lib64/opensips/modules/db_postgres.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/af/a6d95e187d5dcba1eb023bbc63c262201ad79a
Missing separate debuginfo for 
/usr/lib64/opensips/modules/cachedb_mongodb.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/b6/396b906d1cbb1a0dfba6e55d9403c5ef3203c4

Missing separate debuginfo for /usr/lib64/opensips/modules/presence.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/9b/91e940f23ccd73dd8d85c3cba662ad053d41f9
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_mwi.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/0f/71857a5f102128ec9271834c5c50fbbb489eaa
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_xml.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/d5/c0541f0d0dc673a4c1471a29002ada102b4b4f
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_dialoginfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/65/838cc25cb0cc95909a38c8740e2a5eca50ea50
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_callinfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/5b/e9f008d233d92f83f94ec0a22804d9f3f42f97

Missing separate debuginfo for /usr/lib64/opensips/modules/pua.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/bf/bb7811d4410f272fba13e1bd3d55162cc8a570
Missing separate debuginfo for 
/usr/lib64/opensips/modules/pua_dialoginfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/cb/9844b685005e0d892755305f4112ba4b87ef0b

Missing separate debuginfo for /usr/lib64/opensips/modules/xcap.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/a3/72d49769b2d1beac896874ee6b727e7d9f65e9
Missing separate debuginfo for 
/usr/lib64/opensips/modules/db_postgres.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/af/a6d95e187d5dcba1eb023bbc63c262201ad79a.debug

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for 
/usr/lib64/opensips/modules/cachedb_mongodb.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/b6/396b906d1cbb1a0dfba6e55d9403c5ef3203c4.debug

Missing separate debuginfo for /usr/lib64/opensips/modules/presence.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/9b/91e940f23ccd73dd8d85c3cba662ad053d41f9.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_mwi.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/0f/71857a5f102128ec9271834c5c50fbbb489eaa.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_xml.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/d5/c0541f0d0dc673a4c1471a29002ada102b4b4f.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_dialoginfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/65/838cc25cb0cc95909a38c8740e2a5eca50ea50.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_callinfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/5b/e9f008d233d92f83f94ec0a22804d9f3f42f97.debug

Missing separate debuginfo for /usr/lib64/opensips/modules/pua.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/bf/bb7811d4410f272fba13e1bd3d55162cc8a570.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/pua_dialoginfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/cb/9844b685005e0d892755305f4112ba4b87ef0b.debug

Missing separate debuginfo for /usr/lib64/opensips/modules/xcap.so
Try: dnf --enablerepo='*debug*' install 

Re: [OpenSIPS-Users] opensips crash

[volga629]

Hello Bogdan,
I was be able catch the crash and presence module is segfault the 
opensips.



[root@aitossbc03 ccpp-2018-08-15-23:20:51.377819-10036]# gdb coredump
GNU gdb (GDB) Fedora 8.0.1-36.fc27
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show 
copying"

and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
[New LWP 10036]
Reading symbols from /usr/sbin/opensips...Reading symbols from 
/usr/lib/debug/usr/sbin/opensips-3.0.0.b33b7a7e7-2.fc27.x86_64.debug...done.

done.

warning: Ignoring non-absolute filename: 
Missing separate debuginfo for linux-vdso.so.1
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/f9/61d796c26168fae4f7c8c3d20d229ec61e97a7
Missing separate debuginfo for 
/usr/lib64/opensips/modules/db_postgres.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/af/a6d95e187d5dcba1eb023bbc63c262201ad79a
Missing separate debuginfo for 
/usr/lib64/opensips/modules/cachedb_mongodb.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/b6/396b906d1cbb1a0dfba6e55d9403c5ef3203c4

Missing separate debuginfo for /usr/lib64/opensips/modules/presence.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/9b/91e940f23ccd73dd8d85c3cba662ad053d41f9
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_mwi.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/0f/71857a5f102128ec9271834c5c50fbbb489eaa
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_xml.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/d5/c0541f0d0dc673a4c1471a29002ada102b4b4f
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_dialoginfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/65/838cc25cb0cc95909a38c8740e2a5eca50ea50
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_callinfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/5b/e9f008d233d92f83f94ec0a22804d9f3f42f97

Missing separate debuginfo for /usr/lib64/opensips/modules/pua.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/bf/bb7811d4410f272fba13e1bd3d55162cc8a570
Missing separate debuginfo for 
/usr/lib64/opensips/modules/pua_dialoginfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/cb/9844b685005e0d892755305f4112ba4b87ef0b

Missing separate debuginfo for /usr/lib64/opensips/modules/xcap.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/a3/72d49769b2d1beac896874ee6b727e7d9f65e9
Missing separate debuginfo for 
/usr/lib64/opensips/modules/db_postgres.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/af/a6d95e187d5dcba1eb023bbc63c262201ad79a.debug

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for 
/usr/lib64/opensips/modules/cachedb_mongodb.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/b6/396b906d1cbb1a0dfba6e55d9403c5ef3203c4.debug

Missing separate debuginfo for /usr/lib64/opensips/modules/presence.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/9b/91e940f23ccd73dd8d85c3cba662ad053d41f9.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_mwi.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/0f/71857a5f102128ec9271834c5c50fbbb489eaa.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_xml.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/d5/c0541f0d0dc673a4c1471a29002ada102b4b4f.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_dialoginfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/65/838cc25cb0cc95909a38c8740e2a5eca50ea50.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/presence_callinfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/5b/e9f008d233d92f83f94ec0a22804d9f3f42f97.debug

Missing separate debuginfo for /usr/lib64/opensips/modules/pua.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/bf/bb7811d4410f272fba13e1bd3d55162cc8a570.debug
Missing separate debuginfo for 
/usr/lib64/opensips/modules/pua_dialoginfo.so
Try: dnf --enablerepo='*debug*' install 
/usr/lib/debug/.build-id/cb/9844b685005e0d892755305f4112ba4b87ef0b.debug

Missing separate debuginfo for /usr/lib64/opensips/modules/xcap.so
Try: dnf 

Re: [OpenSIPS-Users] opensips crash

[Bogdan-Andrei Iancu]

Hi,

See http://www.opensips.org/Documentation/TroubleShooting-Crash for how 
to extract the backtrace from the corefile.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
  http://opensips.org/training/OpenSIPS_Bootcamp_2018/

On 07/26/2018 08:53 PM, volga...@networklab.ca wrote:

Hello Everyone,
Opensips crashing randomly how possible find what the issue


Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6297]: 
CRITICAL:core:handle_tcp_worker: dead tcp worker 4 (EOF received), pid 
6292
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
child process 6292 exited by a signal 11
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
core was generated
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
terminating due to SIGCHLD
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6265]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6266]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6267]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 15(6279) [SIP receiver 
udp:private_ip_interface:5060 ] terminated, still waiting for 31 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 18(6282) [SIP receiver 
udp:public_ip_interface:5082 ] terminated, still waiting for 30 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 20(6284) [SIP receiver 
udp:public_ip_interface:5060 ] terminated, still waiting for 29 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 22(6286) [SIP receiver 
udp:public_ip_interface:5060 ] terminated, still waiting for 28 more


volga629


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] opensips crash

[volga629]

Hello Everyone,
Opensips crashing randomly how possible find what the issue


Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6297]: 
CRITICAL:core:handle_tcp_worker: dead tcp worker 4 (EOF received), pid 
6292
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
child process 6292 exited by a signal 11
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
core was generated
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
terminating due to SIGCHLD
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6265]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6266]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6267]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 15(6279) [SIP receiver 
udp:private_ip_interface:5060 ] terminated, still waiting for 31 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 18(6282) [SIP receiver 
udp:public_ip_interface:5082 ] terminated, still waiting for 30 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 20(6284) [SIP receiver 
udp:public_ip_interface:5060 ] terminated, still waiting for 29 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 22(6286) [SIP receiver 
udp:public_ip_interface:5060 ] terminated, still waiting for 28 more


volga629


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS Crash

[Liviu Chircu]

That we already know, dear sir! But before simply fixing this issue and 
moving on, my question is: How many more OpenSIPS functions (sip_trace() 
included) are still subject to such a basic vulnerability?


(probably this will turn into a GitHub ticket that will be assigned to 
me. Oh well, at least it's for the better good of the community)


Cheers,

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

On 08.06.2018 18:58, Schneur Rosenberg wrote:

A malformed sip packet should not crash OpenSIPS it should just give
an error and move on

On Fri, Jun 8, 2018 at 3:00 PM, Ben Newlin  wrote:

Liviu,



I am very impressed! I was indeed sending a malformed invite just like the
one you posted, specifically with the missing line termination before the
Call-ID.



Thanks,

Ben Newlin





From: Users  on behalf of Liviu Chircu

Reply-To: OpenSIPS users mailling list 
Date: Friday, June 8, 2018 at 5:17 AM
To: "users@lists.opensips.org" 
Subject: Re: [OpenSIPS-Users] OpenSIPS Crash



Hi Ben,

Excellent report! I managed to reproduce the crash on first try:

Core was generated by `./opensips -m64 -M16 -f
cfg/opensips-2.4-sipp-siptrace.cfg -w .'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f7987cd7f2a in sip_trace (msg=0x7f799817fd20,
info=0x7f799468d5e0) at siptrace.c:1646
1646db_vals[1].val.str_val.s = msg->callid->body.s;
(gdb) bt
#0  0x7f7987cd7f2a in sip_trace (msg=0x7f799817fd20,
info=0x7f799468d5e0) at siptrace.c:1646
#1  0x7f7987cd7c8d in sip_trace_w (msg=0x7f799817fd20,
param1=0x7f7998169110 "\001", param2=0x2 , param3=0x7f79981691f8 "\001", param4=0x0) at siptrace.c:1590
#2  0x00445082 in do_action (a=0x7f79981589a0, msg=0x7f799817fd20)
at action.c:1864
#3  0x0043ccf7 in run_action_list (a=0x7f79981589a0,
msg=0x7f799817fd20) at action.c:172

Quick question for you: you are sending a malformed INVITE, correct? Here is
how mine looked like:

INVITE sip:sipp@127.0.0.1:5060 SIP/2.0.
Via: SIP/2.0/UDP 127.0.0.1:7000;branch=z9hG4bK-1988-1-0.
From: sipp ;tag=123456789.
To: sut .
CSeq: 1 INVITE.
Contact:Call-ID: 1-1988@127.0.0.1.
Max-Forwards: 70.
Subject: Performance Test.
Content-Type: application/sdp.
Content-Length:   129.
.
v=0.
o=user1 53655765 2353687637 IN IP4 127.0.0.1.
s=-.
c=IN IP4 127.0.0.1.
t=0 0.
m=audio 6001 RTP/AVP 0.
a=rtpmap:0 PCMU/8000.

Notice how OpenSIPS will be unable to parse the Call-ID header field, hence
the immediate crash in sip_trace(), as it's unable to handle a NULL Call-ID.

Best regards,

Liviu Chircu

OpenSIPS Developer

http://www.opensips-solutions.com

On 07.06.2018 22:24, Ben Newlin wrote:

Hi,



While running a new test scenario I encountered an OpenSIPS crash.



version: opensips 2.3.3 (x86_64/linux)

flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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: a0bed9d

main.c compiled on 21:08:28 May 16 2018 with gcc 4.8.5



Logs: https://pastebin.com/3vL3rbG4

BT: https://pastebin.com/tTp32ASC



Let me know if anything else is needed.



Thanks,

Ben Newlin






___

Users mailing list

Users@lists.opensips.org

http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS Crash

[Schneur Rosenberg]

A malformed sip packet should not crash OpenSIPS it should just give
an error and move on

On Fri, Jun 8, 2018 at 3:00 PM, Ben Newlin  wrote:
> Liviu,
>
>
>
> I am very impressed! I was indeed sending a malformed invite just like the
> one you posted, specifically with the missing line termination before the
> Call-ID.
>
>
>
> Thanks,
>
> Ben Newlin
>
>
>
>
>
> From: Users  on behalf of Liviu Chircu
> 
> Reply-To: OpenSIPS users mailling list 
> Date: Friday, June 8, 2018 at 5:17 AM
> To: "users@lists.opensips.org" 
> Subject: Re: [OpenSIPS-Users] OpenSIPS Crash
>
>
>
> Hi Ben,
>
> Excellent report! I managed to reproduce the crash on first try:
>
> Core was generated by `./opensips -m64 -M16 -f
> cfg/opensips-2.4-sipp-siptrace.cfg -w .'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x7f7987cd7f2a in sip_trace (msg=0x7f799817fd20,
> info=0x7f799468d5e0) at siptrace.c:1646
> 1646db_vals[1].val.str_val.s = msg->callid->body.s;
> (gdb) bt
> #0  0x7f7987cd7f2a in sip_trace (msg=0x7f799817fd20,
> info=0x7f799468d5e0) at siptrace.c:1646
> #1  0x7f7987cd7c8d in sip_trace_w (msg=0x7f799817fd20,
> param1=0x7f7998169110 "\001", param2=0x2  address 0x2>, param3=0x7f79981691f8 "\001", param4=0x0) at siptrace.c:1590
> #2  0x00445082 in do_action (a=0x7f79981589a0, msg=0x7f799817fd20)
> at action.c:1864
> #3  0x0043ccf7 in run_action_list (a=0x7f79981589a0,
> msg=0x7f799817fd20) at action.c:172
>
> Quick question for you: you are sending a malformed INVITE, correct? Here is
> how mine looked like:
>
> INVITE sip:sipp@127.0.0.1:5060 SIP/2.0.
> Via: SIP/2.0/UDP 127.0.0.1:7000;branch=z9hG4bK-1988-1-0.
> From: sipp ;tag=123456789.
> To: sut .
> CSeq: 1 INVITE.
> Contact:Call-ID: 1-1988@127.0.0.1.
> Max-Forwards: 70.
> Subject: Performance Test.
> Content-Type: application/sdp.
> Content-Length:   129.
> .
> v=0.
> o=user1 53655765 2353687637 IN IP4 127.0.0.1.
> s=-.
> c=IN IP4 127.0.0.1.
> t=0 0.
> m=audio 6001 RTP/AVP 0.
> a=rtpmap:0 PCMU/8000.
>
> Notice how OpenSIPS will be unable to parse the Call-ID header field, hence
> the immediate crash in sip_trace(), as it's unable to handle a NULL Call-ID.
>
> Best regards,
>
> Liviu Chircu
>
> OpenSIPS Developer
>
> http://www.opensips-solutions.com
>
> On 07.06.2018 22:24, Ben Newlin wrote:
>
> Hi,
>
>
>
> While running a new test scenario I encountered an OpenSIPS crash.
>
>
>
> version: opensips 2.3.3 (x86_64/linux)
>
> flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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: a0bed9d
>
> main.c compiled on 21:08:28 May 16 2018 with gcc 4.8.5
>
>
>
> Logs: https://pastebin.com/3vL3rbG4
>
> BT: https://pastebin.com/tTp32ASC
>
>
>
> Let me know if anything else is needed.
>
>
>
> Thanks,
>
> Ben Newlin
>
>
>
>
>
>
> ___
>
> Users mailing list
>
> Users@lists.opensips.org
>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS Crash

[Ben Newlin]

Liviu,

I am very impressed! I was indeed sending a malformed invite just like the one 
you posted, specifically with the missing line termination before the Call-ID.

Thanks,
Ben Newlin


From: Users  on behalf of Liviu Chircu 

Reply-To: OpenSIPS users mailling list 
Date: Friday, June 8, 2018 at 5:17 AM
To: "users@lists.opensips.org" 
Subject: Re: [OpenSIPS-Users] OpenSIPS Crash


Hi Ben,

Excellent report! I managed to reproduce the crash on first try:

Core was generated by `./opensips -m64 -M16 -f 
cfg/opensips-2.4-sipp-siptrace.cfg -w .'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f7987cd7f2a in sip_trace (msg=0x7f799817fd20, info=0x7f799468d5e0) 
at siptrace.c:1646
1646db_vals[1].val.str_val.s = msg->callid->body.s;
(gdb) bt
#0  0x7f7987cd7f2a in sip_trace (msg=0x7f799817fd20, info=0x7f799468d5e0) 
at siptrace.c:1646
#1  0x7f7987cd7c8d in sip_trace_w (msg=0x7f799817fd20, 
param1=0x7f7998169110 "\001", param2=0x2 , param3=0x7f79981691f8 "\001", param4=0x0) at siptrace.c:1590
#2  0x00445082 in do_action (a=0x7f79981589a0, msg=0x7f799817fd20) at 
action.c:1864
#3  0x0043ccf7 in run_action_list (a=0x7f79981589a0, 
msg=0x7f799817fd20) at action.c:172
Quick question for you: you are sending a malformed INVITE, correct? Here is 
how mine looked like:

INVITE sip:sipp@127.0.0.1:5060 SIP/2.0.
Via: SIP/2.0/UDP 127.0.0.1:7000;branch=z9hG4bK-1988-1-0.
From: sipp ;tag=123456789.
To: sut .
CSeq: 1 INVITE.
Contact:Call-ID: 
1-1988@127.0.0.1<mailto:1-1988@127.0.0.1>.
Max-Forwards: 70.
Subject: Performance Test.
Content-Type: application/sdp.
Content-Length:   129.
.
v=0.
o=user1 53655765 2353687637 IN IP4 127.0.0.1.
s=-.
c=IN IP4 127.0.0.1.
t=0 0.
m=audio 6001 RTP/AVP 0.
a=rtpmap:0 PCMU/8000.

Notice how OpenSIPS will be unable to parse the Call-ID header field, hence the 
immediate crash in sip_trace(), as it's unable to handle a NULL Call-ID.

Best regards,

Liviu Chircu

OpenSIPS Developer

http://www.opensips-solutions.com
On 07.06.2018 22:24, Ben Newlin wrote:
Hi,

While running a new test scenario I encountered an OpenSIPS crash.

version: opensips 2.3.3 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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: a0bed9d
main.c compiled on 21:08:28 May 16 2018 with gcc 4.8.5

Logs: https://pastebin.com/3vL3rbG4
BT: https://pastebin.com/tTp32ASC

Let me know if anything else is needed.

Thanks,
Ben Newlin





___

Users mailing list

Users@lists.opensips.org<mailto:Users@lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS Crash

[Liviu Chircu]

Hi Ben,

Excellent report! I managed to reproduce the crash on first try:

Core was generated by `./opensips -m64 -M16 -f 
cfg/opensips-2.4-sipp-siptrace.cfg -w .'.

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f7987cd7f2a in sip_trace (msg=0x7f799817fd20, 
info=0x7f799468d5e0) at siptrace.c:1646

1646        db_vals[1].val.str_val.s = msg->callid->body.s;
(gdb) bt
#0  0x7f7987cd7f2a in sip_trace (msg=0x7f799817fd20, 
info=0x7f799468d5e0) at siptrace.c:1646
#1  0x7f7987cd7c8d in sip_trace_w (msg=0x7f799817fd20, 
param1=0x7f7998169110 "\001", param2=0x2 address 0x2>, param3=0x7f79981691f8 "\001", param4=0x0) at siptrace.c:1590
#2  0x00445082 in do_action (a=0x7f79981589a0, 
msg=0x7f799817fd20) at action.c:1864
#3  0x0043ccf7 in run_action_list (a=0x7f79981589a0, 
msg=0x7f799817fd20) at action.c:172


Quick question for you: you are sending a malformed INVITE, correct? 
Here is how mine looked like:


INVITE sip:sipp@127.0.0.1:5060 SIP/2.0.
Via: SIP/2.0/UDP 127.0.0.1:7000;branch=z9hG4bK-1988-1-0.
From: sipp ;tag=123456789.
To: sut .
CSeq: 1 INVITE.
Contact:    Call-ID: 1-1988@127.0.0.1.
Max-Forwards: 70.
Subject: Performance Test.
Content-Type: application/sdp.
Content-Length:   129.
.
v=0.
o=user1 53655765 2353687637 IN IP4 127.0.0.1.
s=-.
c=IN IP4 127.0.0.1.
t=0 0.
m=audio 6001 RTP/AVP 0.
a=rtpmap:0 PCMU/8000.

Notice how OpenSIPS will be unable to parse the Call-ID header field, 
hence the immediate crash in sip_trace(), as it's unable to handle a 
NULL Call-ID.


Best regards,

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

On 07.06.2018 22:24, Ben Newlin wrote:


Hi,

While running a new test scenario I encountered an OpenSIPS crash.

version: opensips 2.3.3 (x86_64/linux)

flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, 
F_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: a0bed9d

main.c compiled on 21:08:28 May 16 2018 with gcc 4.8.5

Logs: https://pastebin.com/3vL3rbG4 

BT: https://pastebin.com/tTp32ASC 

Let me know if anything else is needed.

Thanks,

Ben Newlin



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] OpenSIPS Crash

[Ben Newlin]

Hi,

While running a new test scenario I encountered an OpenSIPS crash.

version: opensips 2.3.3 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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: a0bed9d
main.c compiled on 21:08:28 May 16 2018 with gcc 4.8.5

Logs: https://pastebin.com/3vL3rbG4
BT: https://pastebin.com/tTp32ASC

Let me know if anything else is needed.

Thanks,
Ben Newlin

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Opensips crash 2.2

[Denis via Users]

Hello! 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_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.git revision: ef09a3fmain.c compiled on 07:49:47 Apr  6 2017 with gcc 5.4.0 Core file is herehttps://yadi.sk/i/dHHtQ8-s3NiyiD -- С уважением, Денис.Best regards, Denis   

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Denis,

please check https://github.com/OpenSIPS/opensips/issues/1132

Regards,

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

On 09/22/2017 07:53 AM, Denis via Users wrote:

Hello, Brian
Opensips 2.2. (i have a problem with 2.3)? And what should i rebuilt, 
what node?

--
С уважением, Денис.
Best regards, Denis
22.09.2017, 01:04, "Brian :" :

Hi Denis

We had similar issue recently with radius accounting in a single node 
in a 2.2 cluster. Rebuilding the node from scratch made the issue go 
away.





On Thursday, September 21, 2017, Denis via Users 
> wrote:

> In addition
>
> "
> make[2]: Entering directory '/distr/opensips-2.2/modules/aaa_radius'
> Compiling rad.c
> Compiling aaa_radius.c
> Linking aaa_radius.so
> make[2]: Leaving directory '/distr/opensips-2.2/modules/aaa_radius'
>
> "
>
> During opensips 2.2 installation procedure on the backup.
>
> --
> С уважением, Денис.
> Best regards, Denis
>
>
>
>
>
> 21.09.2017, 16:39, "Denis via Users" >:

>
> Bogdan,
>
> Prehistory. I decided to migrate Opensips from 2.2. to 2.3.
> Using my test VirtualBox (ubuntu server) i installed 2.3., prepare 
opensips.cfg an so on. On VB 2.3. started without any problem.
> I have two production servers with Opensips 2.2 instance. One main, 
and the second backup.
> All necessary packages for Opensips had been installed on these two 
servers early, including libradius library.

>
> So i installed Opensips2.3., both on main and backup (there were no 
error dialing with it), to a different directory as Opensips2.2, 
changed some opensips.cfg parameters (not dialing with radius) and 
tried to start opensips.
> First i tried to start on backup and got the crash. Crash occurs at 
start time.

> Second i tried to start on main and got success.
>
> I tried to reinstall Opensips on backup and during installation 
process i get such information dialing with radius

> "
> make[2]: Entering directory '/distr/opensips-2.3/modules/aaa_radius'
> /bin/sh: 1: pkg-config: not found
> /bin/sh: 1: pkg-config: not found
> Compiling rad.c
> Compiling aaa_radius.c
> Linking aaa_radius.so
> make[2]: Leaving directory '/distr/opensips-2.3/modules/aaa_radius'
> "
>
> Something like this)).
>
> --
> С уважением, Денис.
> Best regards, Denis
>
>
>
> 21.09.2017, 15:46, "Bogdan-Andrei Iancu" >:

>
> Hi Denis,
>
> So, when did the crash start ? What was the change that trigger 
this kind of crash ?

>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com 
>
> On 09/21/2017 01:00 PM, Denis wrote:
>
> Hello, Bogdan!
>
> It is real strange.
>
> First of all i have Opensips 2.2 on the same server ("backup" 
server) which is started without any problem using aaa_radius module.
> I have another server ("main" server) where opensips 2.3 is started 
without any problem using aaa_radius module.

>
> Yes, /etc/radiusclient-ng/radiusclient.conf exits on backup, it has 
the same rights as the same file on main server. I can read this file 
and write into it ,i.e. it is not "broken".

>
> libradius has been installed from ubuntu`s repo.
>
> --
> С уважением, Денис.
> Best regards, Denis
>
>
>
> 21.09.2017, 12:44, "Bogdan-Andrei Iancu" >:

>
> Hi Denis,
>
> Not sure if there is something we can do about in OpenSIPS. As we 
see, in frame 2:

>
> #2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0 
"/etc/radiusclient-ng/radiusclient.conf") at config.c:457

>
> opensips triggers the libradius for reading the config file (for 
radius). And there is only one parameter, the name of the radius 
config file.

>
> The crash is inside the libradius without having opensips to pass 
any wrong data. So the bug is in the libradius.

>
> Does the /etc/radiusclient-ng/radiusclient.conf file exists ?
>
> How did you install the libradius ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com 
>
> On 09/20/2017 06:04 PM, Denis via Users wrote:
>
> Hello!
>
> Opensips 2.3.
> Core file in attachment
>
> The problem with aaa_radius module.
>
> Thank you for any help.
>
> --
> С уважением, Денис.
> Best regards, Denis
>
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org 
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ,
>
> ___
> Users mailing list
> Users@lists.opensips.org 
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Hello, Brian Opensips 2.2. (i have a problem with 2.3)? And what should i rebuilt, what node?  -- С уважением, Денис.Best regards, Denis   22.09.2017, 01:04, "Brian :" :Hi DenisWe had similar issue recently with radius accounting in a single node in a 2.2 cluster. Rebuilding the node from scratch made the issue go away.On Thursday, September 21, 2017, Denis via Users  wrote:> In addition>  > "> make[2]: Entering directory '/distr/opensips-2.2/modules/aaa_radius'> Compiling rad.c> Compiling aaa_radius.c> Linking aaa_radius.so> make[2]: Leaving directory '/distr/opensips-2.2/modules/aaa_radius'>  > ">  > During opensips 2.2 installation procedure on the backup.>  > -- > С уважением, Денис.> Best regards, Denis>  >  >  >  >  > 21.09.2017, 16:39, "Denis via Users" :>> Bogdan,>  > Prehistory. I decided to migrate Opensips from 2.2. to 2.3.> Using my test VirtualBox (ubuntu server) i installed 2.3., prepare opensips.cfg an so on. On VB 2.3. started without any problem.> I have two production servers with Opensips 2.2 instance. One main, and the second backup.> All necessary packages for Opensips had been installed on these two servers early, including libradius library.>  > So i installed Opensips2.3., both on main and backup (there were no error dialing with it), to a different directory as Opensips2.2, changed some opensips.cfg parameters (not dialing with radius) and tried to start opensips.> First i tried to start on backup and got the crash. Crash occurs at start time.> Second i tried to start on main and got success.>  > I tried to reinstall Opensips on backup and during installation process i get such information dialing with radius> "> make[2]: Entering directory '/distr/opensips-2.3/modules/aaa_radius'> /bin/sh: 1: pkg-config: not found> /bin/sh: 1: pkg-config: not found> Compiling rad.c> Compiling aaa_radius.c> Linking aaa_radius.so> make[2]: Leaving directory '/distr/opensips-2.3/modules/aaa_radius'> ">  > Something like this)).>  > -- > С уважением, Денис.> Best regards, Denis>  >  >  > 21.09.2017, 15:46, "Bogdan-Andrei Iancu" :>> Hi Denis,>> So, when did the crash start ? What was the change that trigger this kind of crash ?>> Regards,>> Bogdan-Andrei Iancu> OpenSIPS Founder and Developer> http://www.opensips-solutions.com>> On 09/21/2017 01:00 PM, Denis wrote:>> Hello, Bogdan!>  > It is real strange.>  > First of all i have Opensips 2.2 on the same server ("backup" server) which is started without any problem using aaa_radius module.> I have another server ("main" server) where opensips 2.3 is started without any problem using aaa_radius module.>  > Yes, /etc/radiusclient-ng/radiusclient.conf exits on backup, it has the same rights as the same file on main server. I can read this file and write into it ,i.e. it is not "broken".>  > libradius has been installed from ubuntu`s repo.>  > -- > С уважением, Денис.> Best regards, Denis>  >  >  > 21.09.2017, 12:44, "Bogdan-Andrei Iancu" :>> Hi Denis,>> Not sure if there is something we can do about in OpenSIPS. As we see, in frame 2:>> #2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0 "/etc/radiusclient-ng/radiusclient.conf") at config.c:457>> opensips triggers the libradius for reading the config file (for radius). And there is only one parameter, the name of the radius config file.>> The crash is inside the libradius without having opensips to pass any wrong data. So the bug is in the libradius.>> Does the /etc/radiusclient-ng/radiusclient.conf file exists ?>> How did you install the libradius ?>> Regards,>> Bogdan-Andrei Iancu> OpenSIPS Founder and Developer> http://www.opensips-solutions.com>> On 09/20/2017 06:04 PM, Denis via Users wrote:>> Hello!>  > Opensips 2.3.> Core file in attachment>  > The problem with aaa_radius module.>  > Thank you for any help.>  > -- > С уважением, Денис.> Best regards, Denis>  >  >  >  >> ___> Users mailing list> Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users>> ,>> ___> Users mailing list> Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Brian :]

Hi Denis

We had similar issue recently with radius accounting in a single node in a
2.2 cluster. Rebuilding the node from scratch made the issue go away.




On Thursday, September 21, 2017, Denis via Users 
wrote:
> In addition
>
> "
> make[2]: Entering directory '/distr/opensips-2.2/modules/aaa_radius'
> Compiling rad.c
> Compiling aaa_radius.c
> Linking aaa_radius.so
> make[2]: Leaving directory '/distr/opensips-2.2/modules/aaa_radius'
>
> "
>
> During opensips 2.2 installation procedure on the backup.
>
> --
> С уважением, Денис.
> Best regards, Denis
>
>
>
>
>
> 21.09.2017, 16:39, "Denis via Users" :
>
> Bogdan,
>
> Prehistory. I decided to migrate Opensips from 2.2. to 2.3.
> Using my test VirtualBox (ubuntu server) i installed 2.3., prepare
opensips.cfg an so on. On VB 2.3. started without any problem.
> I have two production servers with Opensips 2.2 instance. One main, and
the second backup.
> All necessary packages for Opensips had been installed on these two
servers early, including libradius library.
>
> So i installed Opensips2.3., both on main and backup (there were no error
dialing with it), to a different directory as Opensips2.2, changed some
opensips.cfg parameters (not dialing with radius) and tried to start
opensips.
> First i tried to start on backup and got the crash. Crash occurs at start
time.
> Second i tried to start on main and got success.
>
> I tried to reinstall Opensips on backup and during installation process i
get such information dialing with radius
> "
> make[2]: Entering directory '/distr/opensips-2.3/modules/aaa_radius'
> /bin/sh: 1: pkg-config: not found
> /bin/sh: 1: pkg-config: not found
> Compiling rad.c
> Compiling aaa_radius.c
> Linking aaa_radius.so
> make[2]: Leaving directory '/distr/opensips-2.3/modules/aaa_radius'
> "
>
> Something like this)).
>
> --
> С уважением, Денис.
> Best regards, Denis
>
>
>
> 21.09.2017, 15:46, "Bogdan-Andrei Iancu" :
>
> Hi Denis,
>
> So, when did the crash start ? What was the change that trigger this kind
of crash ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 09/21/2017 01:00 PM, Denis wrote:
>
> Hello, Bogdan!
>
> It is real strange.
>
> First of all i have Opensips 2.2 on the same server ("backup" server)
which is started without any problem using aaa_radius module.
> I have another server ("main" server) where opensips 2.3 is started
without any problem using aaa_radius module.
>
> Yes, /etc/radiusclient-ng/radiusclient.conf exits on backup, it has the
same rights as the same file on main server. I can read this file and write
into it ,i.e. it is not "broken".
>
> libradius has been installed from ubuntu`s repo.
>
> --
> С уважением, Денис.
> Best regards, Denis
>
>
>
> 21.09.2017, 12:44, "Bogdan-Andrei Iancu" :
>
> Hi Denis,
>
> Not sure if there is something we can do about in OpenSIPS. As we see, in
frame 2:
>
> #2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0
"/etc/radiusclient-ng/radiusclient.conf") at config.c:457
>
> opensips triggers the libradius for reading the config file (for radius).
And there is only one parameter, the name of the radius config file.
>
> The crash is inside the libradius without having opensips to pass any
wrong data. So the bug is in the libradius.
>
> Does the /etc/radiusclient-ng/radiusclient.conf file exists ?
>
> How did you install the libradius ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 09/20/2017 06:04 PM, Denis via Users wrote:
>
> Hello!
>
> Opensips 2.3.
> Core file in attachment
>
> The problem with aaa_radius module.
>
> Thank you for any help.
>
> --
> С уважением, Денис.
> Best regards, Denis
>
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ,
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

In addition "make[2]: Entering directory '/distr/opensips-2.2/modules/aaa_radius'Compiling rad.cCompiling aaa_radius.cLinking aaa_radius.somake[2]: Leaving directory '/distr/opensips-2.2/modules/aaa_radius' " During opensips 2.2 installation procedure on the backup. -- С уважением, Денис.Best regards, Denis 21.09.2017, 16:39, "Denis via Users" :Bogdan, Prehistory. I decided to migrate Opensips from 2.2. to 2.3.Using my test VirtualBox (ubuntu server) i installed 2.3., prepare opensips.cfg an so on. On VB 2.3. started without any problem.I have two production servers with Opensips 2.2 instance. One main, and the second backup.All necessary packages for Opensips had been installed on these two servers early, including libradius library. So i installed Opensips2.3., both on main and backup (there were no error dialing with it), to a different directory as Opensips2.2, changed some opensips.cfg parameters (not dialing with radius) and tried to start opensips.First i tried to start on backup and got the crash. Crash occurs at start time.Second i tried to start on main and got success. I tried to reinstall Opensips on backup and during installation process i get such information dialing with radius"make[2]: Entering directory '/distr/opensips-2.3/modules/aaa_radius'/bin/sh: 1: pkg-config: not found/bin/sh: 1: pkg-config: not foundCompiling rad.cCompiling aaa_radius.cLinking aaa_radius.somake[2]: Leaving directory '/distr/opensips-2.3/modules/aaa_radius'" Something like this)). -- С уважением, Денис.Best regards, Denis   21.09.2017, 15:46, "Bogdan-Andrei Iancu" :Hi Denis,So, when did the crash start ? What was the change that trigger this kind of crash ?Regards,Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
On 09/21/2017 01:00 PM, Denis wrote:Hello, Bogdan! It is real strange. First of all i have Opensips 2.2 on the same server ("backup" server) which is started without any problem using aaa_radius module.I have another server ("main" server) where opensips 2.3 is started without any problem using aaa_radius module. Yes, /etc/radiusclient-ng/radiusclient.conf exits on backup, it has the same rights as the same file on main server. I can read this file and write into it ,i.e. it is not "broken". libradius has been installed from ubuntu`s repo. -- С уважением, Денис.Best regards, Denis   21.09.2017, 12:44, "Bogdan-Andrei Iancu" :Hi Denis,Not sure if there is something we can do about in OpenSIPS. As we see, in frame 2:#2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0 "/etc/radiusclient-ng/radiusclient.conf") at config.c:457opensips triggers the libradius for reading the config file (for radius). And there is only one parameter, the name of the radius config file.The crash is inside the libradius without having opensips to pass any wrong data. So the bug is in the libradius.Does the /etc/radiusclient-ng/radiusclient.conf file exists ?How did you install the libradius ?Regards,Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
On 09/20/2017 06:04 PM, Denis via Users wrote:Hello! Opensips 2.3.Core file in attachment The problem with aaa_radius module. Thank you for any help. -- С уважением, Денис.Best regards, Denis___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
,___Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Bogdan, Prehistory. I decided to migrate Opensips from 2.2. to 2.3.Using my test VirtualBox (ubuntu server) i installed 2.3., prepare opensips.cfg an so on. On VB 2.3. started without any problem.I have two production servers with Opensips 2.2 instance. One main, and the second backup.All necessary packages for Opensips had been installed on these two servers early, including libradius library. So i installed Opensips2.3., both on main and backup (there were no error dialing with it), to a different directory as Opensips2.2, changed some opensips.cfg parameters (not dialing with radius) and tried to start opensips.First i tried to start on backup and got the crash. Crash occurs at start time.Second i tried to start on main and got success. I tried to reinstall Opensips on backup and during installation process i get such information dialing with radius"make[2]: Entering directory '/distr/opensips-2.3/modules/aaa_radius'/bin/sh: 1: pkg-config: not found/bin/sh: 1: pkg-config: not foundCompiling rad.cCompiling aaa_radius.cLinking aaa_radius.somake[2]: Leaving directory '/distr/opensips-2.3/modules/aaa_radius'" Something like this)). -- С уважением, Денис.Best regards, Denis   21.09.2017, 15:46, "Bogdan-Andrei Iancu" :Hi Denis,So, when did the crash start ? What was the change that trigger this kind of crash ?Regards,Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
On 09/21/2017 01:00 PM, Denis wrote:Hello, Bogdan! It is real strange. First of all i have Opensips 2.2 on the same server ("backup" server) which is started without any problem using aaa_radius module.I have another server ("main" server) where opensips 2.3 is started without any problem using aaa_radius module. Yes, /etc/radiusclient-ng/radiusclient.conf exits on backup, it has the same rights as the same file on main server. I can read this file and write into it ,i.e. it is not "broken". libradius has been installed from ubuntu`s repo. -- С уважением, Денис.Best regards, Denis   21.09.2017, 12:44, "Bogdan-Andrei Iancu" :Hi Denis,Not sure if there is something we can do about in OpenSIPS. As we see, in frame 2:#2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0 "/etc/radiusclient-ng/radiusclient.conf") at config.c:457opensips triggers the libradius for reading the config file (for radius). And there is only one parameter, the name of the radius config file.The crash is inside the libradius without having opensips to pass any wrong data. So the bug is in the libradius.Does the /etc/radiusclient-ng/radiusclient.conf file exists ?How did you install the libradius ?Regards,Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
On 09/20/2017 06:04 PM, Denis via Users wrote:Hello! Opensips 2.3.Core file in attachment The problem with aaa_radius module. Thank you for any help. -- С уважением, Денис.Best regards, Denis___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Hi Denis,

So, when did the crash start ? What was the change that trigger this 
kind of crash ?


Regards,

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

On 09/21/2017 01:00 PM, Denis wrote:

Hello, Bogdan!
It is real strange.
First of all i have Opensips 2.2 on the same server ("backup" server) 
which is started without any problem using aaa_radius module.
I have another server ("main" server) where opensips 2.3 is started 
without any problem using aaa_radius module.
Yes, /etc/radiusclient-ng/radiusclient.conf exits on backup, it has 
the same rights as the same file on main server. I can read this file 
and write into it ,i.e. it is not "broken".

libradius has been installed from ubuntu`s repo.
--
С уважением, Денис.
Best regards, Denis
21.09.2017, 12:44, "Bogdan-Andrei Iancu" :

Hi Denis,

Not sure if there is something we can do about in OpenSIPS. As we 
see, in frame 2:


#2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0 
"/etc/radiusclient-ng/radiusclient.conf") at config.c:457


opensips triggers the libradius for reading the config file (for 
radius). And there is only one parameter, the name of the radius 
config file.


The crash is inside the libradius without having opensips to pass any 
wrong data. So the bug is in the libradius.


Does the /etc/radiusclient-ng/radiusclient.conf file exists ?

How did you install the libradius ?

Regards,
Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer
   http://www.opensips-solutions.com 
On 09/20/2017 06:04 PM, Denis via Users wrote:

Hello!
Opensips 2.3.
Core file in attachment
The problem with aaa_radius module.
Thank you for any help.
--
С уважением, Денис.
Best regards, Denis
___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Hello, Bogdan! It is real strange. First of all i have Opensips 2.2 on the same server ("backup" server) which is started without any problem using aaa_radius module.I have another server ("main" server) where opensips 2.3 is started without any problem using aaa_radius module. Yes, /etc/radiusclient-ng/radiusclient.conf exits on backup, it has the same rights as the same file on main server. I can read this file and write into it ,i.e. it is not "broken". libradius has been installed from ubuntu`s repo. -- С уважением, Денис.Best regards, Denis   21.09.2017, 12:44, "Bogdan-Andrei Iancu" :Hi Denis,Not sure if there is something we can do about in OpenSIPS. As we see, in frame 2:#2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0 "/etc/radiusclient-ng/radiusclient.conf") at config.c:457opensips triggers the libradius for reading the config file (for radius). And there is only one parameter, the name of the radius config file.The crash is inside the libradius without having opensips to pass any wrong data. So the bug is in the libradius.Does the /etc/radiusclient-ng/radiusclient.conf file exists ?How did you install the libradius ?Regards,Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
On 09/20/2017 06:04 PM, Denis via Users wrote:Hello! Opensips 2.3.Core file in attachment The problem with aaa_radius module. Thank you for any help. -- С уважением, Денис.Best regards, Denis___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Hi Denis,

Not sure if there is something we can do about in OpenSIPS. As we see, 
in frame 2:


#2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0 
"/etc/radiusclient-ng/radiusclient.conf") at config.c:457


opensips triggers the libradius for reading the config file (for 
radius). And there is only one parameter, the name of the radius config 
file.


The crash is inside the libradius without having opensips to pass any 
wrong data. So the bug is in the libradius.


Does the /etc/radiusclient-ng/radiusclient.conf file exists ?

How did you install the libradius ?

Regards,

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

On 09/20/2017 06:04 PM, Denis via Users wrote:

Hello!
Opensips 2.3.
Core file in attachment
The problem with aaa_radius module.
Thank you for any help.
--
С уважением, Денис.
Best regards, Denis


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Opensips crash

[Denis via Users]

Hello! Opensips 2.3.Core file in attachment The problem with aaa_radius module. Thank you for any help. -- С уважением, Денис.Best regards, Denis   [BEGIN] 20.09.2017 18:01:52
root@opensips-reserv:/opensipscore# gdb /usr/local/opensips2.3/sbin/opensips 
core
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/opensips2.3/sbin/opensips...done.
[New LWP 1339]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/opensips2.3/sbin/opensips -P 
/sock/opensipstest.pid -u opensips -w /'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f3622d99bc8 in rc_conf_int (rh=, optname=) at config.c:500
500 config.c: No such file or directory.
(gdb) bt full
#0  0x7f3622d99bc8 in rc_conf_int (rh=, optname=) at config.c:500
option = 
#1  0x7f3622d99d98 in test_config (rh=rh@entry=0x1bd4990, 
filename=filename@entry=0x1bc83b0 "/etc/radiusclient-ng/radiusclient.conf") at 
config.c:563
No locals.
#2  0x7f3622d9a1e7 in rc_read_config (filename=0x1bc83b0 
"/etc/radiusclient-ng/radiusclient.conf") at config.c:457
configfd = 0x1bd45b0
buffer = "login_local\000/bin/login\000\000 flag for preauthenticated 
login\n\000\000ver\n\000 
leave\n\000\003\000\000\000\000\000\000\000\320.A\000\000\000\000\000\070\205 
f6\177\000\000\000\264!f\000\000\000\000(|*f6\177\000\000\260?\376\377\177\000\000N\277I\000\000\000\000\000\220?\376\377\177\000\000s;L\000\000\000\000\000\070\205
 
f6\177\000\000\060\340\233\376\377\177\000\000\227\350Bf6\177\000\000P|*f6\177\000\000\345\255@f6\177\000\000\064\005\000\000\000\000\000\000\320.A\000\000\000\000\000\220\346"...
p = 
option = 
line = 81
pos = 
rh = 0x1bd4990
#3  0x7f3622fa6cd8 in init_radius_handle () at aaa_radius.c:764
i = 0
da = 0x3
name = 
"i\351Bf6\177\000\000\003\000\000\000\066\177\000\000\000\341\233\376\377\177\000\000\r\b\000\000\001\000\000\000\360>If6\177\000\000\000\376\325+\225_\347\230\000\000\000\000\001\000\000\000\064\005\000\000\000\000\000\000\320.A\000\000\000\000\000\220\346\233\376\377\177",
 '\000' , 
"\341\233\376\377\177\000\000\\\223E\000\000\000\000\000\a\000\000\000\a\000\000\000\240\352Bf6\177\000\000\260=If6\177\000\000
 
?If6\177\000\000h\351Bf6\177\000\000\t\000\000\000\000\000\000\000\320.A\000\000\000\000\000\000\376\325+\225_\347\230\064\005\000\000\000\000\000\000\320.A\000\000\000\000\000\240\341\233\376\377\177\000\000"...
mp = 0x7f366642e96d
__FUNCTION__ = "init_radius_handle"
#4  0x7f3622fa65a1 in send_auth_fixup (param=0x7f366642ee38, param_no=1) at 
aaa_radius.c:571
s = 0x534
__FUNCTION__ = "send_auth_fixup"
#5  0x004a536e in fix_actions (a=0x7f366642e5a0) at route.c:460
t = 0x7f366642ee10
ret = 0
cmd = 0x7f36231aa1b0 
acmd = 0x4a5923 
he = 0x591988
ip = {af = 0, len = 0, u = {addrl = {139871620620168, 1716074840}, 
addr32 = {1715658632, 32566, 1716074840, 0}, addr16 = {57224, 26178, 32566, 0, 
14680, 26185, 0, 0}, 
addr = "\210\337Bf6\177\000\000X9If\000\000\000"}}
si = 0x98e75f952bd5fe00
host = {s = 0x7e9be690 "\v", len = 0}
proto = 0
port = 1332
p = 0x412ed0 <_start>
blh = 0x534
i = 1
s = {s = 0x7e9be280 "\300\342\233\376\377\177", len = 4866230}
---Type  to continue, or q  to quit--- 
model = 0x0
models = {0x534, 0x412ed0 <_start>, 0x7e9be2c0, 0x4a3db7 
, 0x596bd0 <__FUNCTION__.9323>}
xlp = 0x534
ev_id = 32767
__FUNCTION__ = "fix_actions"
#6  0x004a4d9e in fix_actions (a=0x7f3666439330) at route.c:387
t = 0x7f3666439330
ret = 0
cmd = 0x7e9be360
acmd = 0x4a40b6 
he = 0x7f366642d969
ip = {af = 4271629352, len = 32767, u = {addrl = {139871620619568, 
4271629280}, addr32 = {1715658032, 32566, 4271629280, 0}, addr16 = {56624, 
26178, 32566, 0, 58336, 65179, 0, 0}, 
addr = "0\335Bf6\177\000\000\340\343\233\376\000\000\000"}}
si = 0x7f366642dc98
host = {s = 0x534 , len = 

Re: [OpenSIPS-Users] OpenSIPS crash with core dump

[Bogdan-Andrei Iancu]

Hi Sammy,

If the debs were properly built, you should also have an opensips-dbg 
pacakge, holding the debug symbols - be sure you have that installed too.


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 05/09/2017 08:47 PM, SamyGo wrote:

Hi Bogdan,
They were build by us using checkinstall.

Regards,
Sammy

On Tue, May 9, 2017 at 9:21 AM, Bogdan-Andrei Iancu 
> wrote:


Hi Sammy,

Do you have the OpenSIPS packages from the official repo or you
built them by yourself ?

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 05/02/2017 11:57 PM, SamyGo wrote:

Hi Razvan,
Can you guide me on how to do that ? which option from "make
menuconfig" should I check from compile options. Meanwhile trying
to figure out the same for openssl.
Will get back to you with these debug symbols in place and core
re-read.
Regards,
Sammy
On Tue, May 2, 2017 at 3:22 AM, Răzvan Crainea
> wrote:

Hi, Sammy! Can you install the debugging symbols for both
opensips and openssl? After you install them, inspect the
core file again and run a 'bt full' command. It will help us
figure out the stack trace to see what happened. Best
regards, Răzvan Crainea OpenSIPS Core Developer
http://www.opensips-solutions.com
On 05/02/2017 02:22 AM,
SamyGo wrote:

Hi All, I've been seeing some crashes in my opensips
servers: *_version:_* opensips 2.2.1 (x86_64/linux)flags:
STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP,
PKG_MALLOC, F_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. main.c compiled on 16:33:09 Jan 12 2017 with gcc
4.8 *Operatin System:* Ubuntu 14.04.5 LTS *_Core
File:_*(gdb) bt full #0  strlen () at
../sysdeps/x86_64/strlen.S:106 No locals. #1 
0x7f55a8a32f59 in i2d_SSL_SESSION () from

/lib/x86_64-linux-gnu/libssl.so.1.0.0 No symbol table
info available. #2  0x7f55a8a07bd5 in ?? () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0 No symbol table
info available. #3  0x7f55a8a08960 in ?? () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0 No symbol table
info available. #4  0x7f55a83f5a7f in ?? () from

/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so
No symbol table info available. #5  0x7f55a83fe880 in
?? () from

/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so
No symbol table info available. #6  0x005a372d in
?? () No symbol table info available. #7 
0x005a4dcb in tcp_worker_proc () No symbol table

info available. #8  0x0059cbb9 in
tcp_start_processes () No symbol table info available.
#9  0x00419cda in main () No symbol table info
available. *_Another Crash trace:_*
(gdb) bt full #0  0x7fc0abe039da in strtok () at
../sysdeps/x86_64/strtok.S:186 No locals. #1 
0x0024 in ?? () No symbol table info

available. #2  0x00020004 in ?? () No symbol
table info available. #3  0x7ffe32a6f9c0 in ?? () No
symbol table info available. #4  0x7fbf8baef57c in ??
() No symbol table info available. #5  0x00020002
in ?? () No symbol table info available. #6 
0x7ffe32a6f9d0 in ?? () No symbol table info

available. #7  0x7fbf8aa8bf00 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 No symbol table
info available. #8  0x7fbf8b53f000 in ?? () No symbol
table info available. #9  0x0014 in ?? () No
symbol table info available. #10 0x in ??
() No symbol table info available. (gdb) (gdb) bt full
#0  0x7fe03fc9cc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0 pid = 36112 selftid = 36112
#1  0x7fe03fca0028 in __GI_abort () at abort.c:89
 

Re: [OpenSIPS-Users] OpenSIPS crash with core dump

[SamyGo]

Hi Bogdan,
They were build by us using checkinstall.

Regards,
Sammy

On Tue, May 9, 2017 at 9:21 AM, Bogdan-Andrei Iancu 
wrote:

> Hi Sammy,
>
> Do you have the OpenSIPS packages from the official repo or you built them
> by yourself ?
>
> 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 05/02/2017 11:57 PM, SamyGo wrote:
>
> Hi Razvan,
> Can you guide me on how to do that ? which option from "make menuconfig"
> should I check from compile options. Meanwhile trying to figure out the
> same for openssl.
>
> Will get back to you with these debug symbols in place and core re-read.
>
> Regards,
> Sammy
>
> On Tue, May 2, 2017 at 3:22 AM, Răzvan Crainea 
> wrote:
>
>> Hi, Sammy!
>>
>> Can you install the debugging symbols for both opensips and openssl?
>> After you install them, inspect the core file again and run a 'bt full'
>> command.
>> It will help us figure out the stack trace to see what happened.
>>
>> Best regards,
>>
>> Răzvan Crainea
>> OpenSIPS Core Developer
>> http://www.opensips-solutions.com
>>
>> On 05/02/2017 02:22 AM, SamyGo wrote:
>>
>>> Hi All,
>>> I've been seeing some crashes in my opensips servers:
>>>
>>>
>>> *_version:_* opensips 2.2.1 (x86_64/linux)
>>> flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,
>>> F_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.
>>> main.c compiled on 16:33:09 Jan 12 2017 with gcc 4.8
>>>
>>> *Operatin System:* Ubuntu 14.04.5 LTS
>>>
>>> *_Core File:_*
>>>
>>> (gdb) bt full
>>>
>>> #0  strlen () at ../sysdeps/x86_64/strlen.S:106
>>>
>>> No locals.
>>>
>>> #1  0x7f55a8a32f59 in i2d_SSL_SESSION () from
>>> /lib/x86_64-linux-gnu/libssl.so.1.0.0
>>>
>>> No symbol table info available.
>>>
>>> #2  0x7f55a8a07bd5 in ?? () from /lib/x86_64-linux-gnu/libssl.s
>>> o.1.0.0
>>>
>>> No symbol table info available.
>>>
>>> #3  0x7f55a8a08960 in ?? () from /lib/x86_64-linux-gnu/libssl.s
>>> o.1.0.0
>>>
>>> No symbol table info available.
>>>
>>> #4  0x7f55a83f5a7f in ?? () from
>>> /home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so
>>>
>>> No symbol table info available.
>>>
>>> #5  0x7f55a83fe880 in ?? () from
>>> /home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so
>>>
>>> No symbol table info available.
>>>
>>> #6  0x005a372d in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #7  0x005a4dcb in tcp_worker_proc ()
>>>
>>> No symbol table info available.
>>>
>>> #8  0x0059cbb9 in tcp_start_processes ()
>>>
>>> No symbol table info available.
>>>
>>> #9  0x00419cda in main ()
>>>
>>> No symbol table info available.
>>>
>>>
>>>
>>>
>>> *_Another Crash trace:_*
>>>
>>>
>>>
>>> (gdb) bt full
>>>
>>> #0  0x7fc0abe039da in strtok () at ../sysdeps/x86_64/strtok.S:186
>>>
>>> No locals.
>>>
>>> #1  0x0024 in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #2  0x00020004 in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #3  0x7ffe32a6f9c0 in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #4  0x7fbf8baef57c in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #5  0x00020002 in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #6  0x7ffe32a6f9d0 in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #7  0x7fbf8aa8bf00 in ?? () from
>>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>>>
>>> No symbol table info available.
>>>
>>> #8  0x7fbf8b53f000 in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #9  0x0014 in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> #10 0x in ?? ()
>>>
>>> No symbol table info available.
>>>
>>> (gdb)
>>>
>>>
>>>
>>>
>>>
>>> (gdb) bt full
>>>
>>> #0  0x7fe03fc9cc37 in __GI_raise (sig=sig@entry=6) at
>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
>>>
>>> resultvar = 0
>>>
>>> pid = 36112
>>>
>>> selftid = 36112
>>>
>>> #1  0x7fe03fca0028 in __GI_abort () at abort.c:89
>>>
>>> save_stage = 2
>>>
>>> act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction =
>>> 0x0}, sa_mask = {__val = {140596270402586, 8589934592, 64, 3, 33,
>>> 140596283430288,
>>>
>>>   140596283430040, 18446744073709551614, 140596264663692,
>>> 140596282823192, 3, 33, 140596264116466, 3, 8885408, 1}}, sa_flags =
>>> 8885408,
>>>
>>>   sa_restorer = 0x1}
>>>
>>> sigs = {__val = {32, 0 }}
>>>
>>> #2  0x7fdf1ebfaa62 in ?? () from
>>> /home/opensips/local/opensips/2_21/lib64/opensips/modules/tls_mgm.so
>>>
>>> No symbol table info available.
>>>
>>> #3  0x7fdf1e610fcd in CRYPTO_free () from
>>> 

Re: [OpenSIPS-Users] OpenSIPS crash with core dump

[Bogdan-Andrei Iancu]

Hi Sammy,

Do you have the OpenSIPS packages from the official repo or you built 
them by yourself ?


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 05/02/2017 11:57 PM, SamyGo wrote:

Hi Razvan,
Can you guide me on how to do that ? which option from "make 
menuconfig" should I check from compile options. Meanwhile trying to 
figure out the same for openssl.


Will get back to you with these debug symbols in place and core re-read.

Regards,
Sammy

On Tue, May 2, 2017 at 3:22 AM, Răzvan Crainea > wrote:


Hi, Sammy!

Can you install the debugging symbols for both opensips and
openssl? After you install them, inspect the core file again and
run a 'bt full' command.
It will help us figure out the stack trace to see what happened.

Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com 

On 05/02/2017 02:22 AM, SamyGo wrote:

Hi All,
I've been seeing some crashes in my opensips servers:


*_version:_* opensips 2.2.1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,
F_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.
main.c compiled on 16:33:09 Jan 12 2017 with gcc 4.8

*Operatin System:* Ubuntu 14.04.5 LTS

*_Core File:_*

(gdb) bt full

#0  strlen () at ../sysdeps/x86_64/strlen.S:106

No locals.

#1  0x7f55a8a32f59 in i2d_SSL_SESSION () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#2  0x7f55a8a07bd5 in ?? () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#3  0x7f55a8a08960 in ?? () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#4  0x7f55a83f5a7f in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so

No symbol table info available.

#5  0x7f55a83fe880 in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so

No symbol table info available.

#6  0x005a372d in ?? ()

No symbol table info available.

#7  0x005a4dcb in tcp_worker_proc ()

No symbol table info available.

#8  0x0059cbb9 in tcp_start_processes ()

No symbol table info available.

#9  0x00419cda in main ()

No symbol table info available.




*_Another Crash trace:_*



(gdb) bt full

#0  0x7fc0abe039da in strtok () at
../sysdeps/x86_64/strtok.S:186

No locals.

#1  0x0024 in ?? ()

No symbol table info available.

#2  0x00020004 in ?? ()

No symbol table info available.

#3  0x7ffe32a6f9c0 in ?? ()

No symbol table info available.

#4  0x7fbf8baef57c in ?? ()

No symbol table info available.

#5  0x00020002 in ?? ()

No symbol table info available.

#6  0x7ffe32a6f9d0 in ?? ()

No symbol table info available.

#7  0x7fbf8aa8bf00 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

No symbol table info available.

#8  0x7fbf8b53f000 in ?? ()

No symbol table info available.

#9  0x0014 in ?? ()

No symbol table info available.

#10 0x in ?? ()

No symbol table info available.

(gdb)





(gdb) bt full

#0  0x7fe03fc9cc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56

resultvar = 0

pid = 36112

selftid = 36112

#1  0x7fe03fca0028 in __GI_abort () at abort.c:89

save_stage = 2

act = {__sigaction_handler = {sa_handler = 0x0,
sa_sigaction =
0x0}, sa_mask = {__val = {140596270402586, 8589934592, 64, 3, 33,
140596283430288,

  140596283430040, 18446744073709551614,
140596264663692,
140596282823192, 3, 33, 140596264116466, 3, 8885408, 1}},
sa_flags =
8885408,

  sa_restorer = 0x1}

sigs = {__val = {32, 0 }}

#2  0x7fdf1ebfaa62 in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/tls_mgm.so

No symbol table info available.

#3  0x7fdf1e610fcd in CRYPTO_free () from
  

Re: [OpenSIPS-Users] OpenSIPS crash with core dump

[SamyGo]

Hi Razvan,
Can you guide me on how to do that ? which option from "make menuconfig"
should I check from compile options. Meanwhile trying to figure out the
same for openssl.

Will get back to you with these debug symbols in place and core re-read.

Regards,
Sammy

On Tue, May 2, 2017 at 3:22 AM, Răzvan Crainea  wrote:

> Hi, Sammy!
>
> Can you install the debugging symbols for both opensips and openssl? After
> you install them, inspect the core file again and run a 'bt full' command.
> It will help us figure out the stack trace to see what happened.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
> On 05/02/2017 02:22 AM, SamyGo wrote:
>
>> Hi All,
>> I've been seeing some crashes in my opensips servers:
>>
>>
>> *_version:_* opensips 2.2.1 (x86_64/linux)
>> flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,
>> F_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.
>> main.c compiled on 16:33:09 Jan 12 2017 with gcc 4.8
>>
>> *Operatin System:* Ubuntu 14.04.5 LTS
>>
>> *_Core File:_*
>>
>> (gdb) bt full
>>
>> #0  strlen () at ../sysdeps/x86_64/strlen.S:106
>>
>> No locals.
>>
>> #1  0x7f55a8a32f59 in i2d_SSL_SESSION () from
>> /lib/x86_64-linux-gnu/libssl.so.1.0.0
>>
>> No symbol table info available.
>>
>> #2  0x7f55a8a07bd5 in ?? () from /lib/x86_64-linux-gnu/libssl.s
>> o.1.0.0
>>
>> No symbol table info available.
>>
>> #3  0x7f55a8a08960 in ?? () from /lib/x86_64-linux-gnu/libssl.s
>> o.1.0.0
>>
>> No symbol table info available.
>>
>> #4  0x7f55a83f5a7f in ?? () from
>> /home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so
>>
>> No symbol table info available.
>>
>> #5  0x7f55a83fe880 in ?? () from
>> /home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so
>>
>> No symbol table info available.
>>
>> #6  0x005a372d in ?? ()
>>
>> No symbol table info available.
>>
>> #7  0x005a4dcb in tcp_worker_proc ()
>>
>> No symbol table info available.
>>
>> #8  0x0059cbb9 in tcp_start_processes ()
>>
>> No symbol table info available.
>>
>> #9  0x00419cda in main ()
>>
>> No symbol table info available.
>>
>>
>>
>>
>> *_Another Crash trace:_*
>>
>>
>>
>> (gdb) bt full
>>
>> #0  0x7fc0abe039da in strtok () at ../sysdeps/x86_64/strtok.S:186
>>
>> No locals.
>>
>> #1  0x0024 in ?? ()
>>
>> No symbol table info available.
>>
>> #2  0x00020004 in ?? ()
>>
>> No symbol table info available.
>>
>> #3  0x7ffe32a6f9c0 in ?? ()
>>
>> No symbol table info available.
>>
>> #4  0x7fbf8baef57c in ?? ()
>>
>> No symbol table info available.
>>
>> #5  0x00020002 in ?? ()
>>
>> No symbol table info available.
>>
>> #6  0x7ffe32a6f9d0 in ?? ()
>>
>> No symbol table info available.
>>
>> #7  0x7fbf8aa8bf00 in ?? () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>>
>> No symbol table info available.
>>
>> #8  0x7fbf8b53f000 in ?? ()
>>
>> No symbol table info available.
>>
>> #9  0x0014 in ?? ()
>>
>> No symbol table info available.
>>
>> #10 0x in ?? ()
>>
>> No symbol table info available.
>>
>> (gdb)
>>
>>
>>
>>
>>
>> (gdb) bt full
>>
>> #0  0x7fe03fc9cc37 in __GI_raise (sig=sig@entry=6) at
>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
>>
>> resultvar = 0
>>
>> pid = 36112
>>
>> selftid = 36112
>>
>> #1  0x7fe03fca0028 in __GI_abort () at abort.c:89
>>
>> save_stage = 2
>>
>> act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction =
>> 0x0}, sa_mask = {__val = {140596270402586, 8589934592, 64, 3, 33,
>> 140596283430288,
>>
>>   140596283430040, 18446744073709551614, 140596264663692,
>> 140596282823192, 3, 33, 140596264116466, 3, 8885408, 1}}, sa_flags =
>> 8885408,
>>
>>   sa_restorer = 0x1}
>>
>> sigs = {__val = {32, 0 }}
>>
>> #2  0x7fdf1ebfaa62 in ?? () from
>> /home/opensips/local/opensips/2_21/lib64/opensips/modules/tls_mgm.so
>>
>> No symbol table info available.
>>
>> #3  0x7fdf1e610fcd in CRYPTO_free () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>>
>> No symbol table info available.
>>
>> #4  0x7fdf1e9c8c16 in SSL_SESSION_free () from
>> /lib/x86_64-linux-gnu/libssl.so.1.0.0
>>
>> No symbol table info available.
>>
>> #5  0x7fdf1e9c6f5d in SSL_free () from
>> /lib/x86_64-linux-gnu/libssl.so.1.0.0
>>
>> No symbol table info available.
>>
>> #6  0x7fdf1e38a327 in ?? () from
>> /home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so
>>
>> No symbol table info available.
>>
>> #7  0x00593114 in ?? ()
>>
>> No symbol table info available.
>>
>> #8  0x005933b0 in ?? ()
>>
>> No symbol table info available.
>>
>> #9  0x004147f4 in ?? ()
>>
>> No symbol table info available.
>>

Re: [OpenSIPS-Users] OpenSIPS crash with core dump

[Răzvan Crainea]

Hi, Sammy!

Can you install the debugging symbols for both opensips and openssl? 
After you install them, inspect the core file again and run a 'bt full' 
command.

It will help us figure out the stack trace to see what happened.

Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 05/02/2017 02:22 AM, SamyGo wrote:

Hi All,
I've been seeing some crashes in my opensips servers:


*_version:_* opensips 2.2.1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,
F_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.
main.c compiled on 16:33:09 Jan 12 2017 with gcc 4.8

*Operatin System:* Ubuntu 14.04.5 LTS

*_Core File:_*

(gdb) bt full

#0  strlen () at ../sysdeps/x86_64/strlen.S:106

No locals.

#1  0x7f55a8a32f59 in i2d_SSL_SESSION () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#2  0x7f55a8a07bd5 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#3  0x7f55a8a08960 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#4  0x7f55a83f5a7f in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so

No symbol table info available.

#5  0x7f55a83fe880 in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so

No symbol table info available.

#6  0x005a372d in ?? ()

No symbol table info available.

#7  0x005a4dcb in tcp_worker_proc ()

No symbol table info available.

#8  0x0059cbb9 in tcp_start_processes ()

No symbol table info available.

#9  0x00419cda in main ()

No symbol table info available.




*_Another Crash trace:_*


(gdb) bt full

#0  0x7fc0abe039da in strtok () at ../sysdeps/x86_64/strtok.S:186

No locals.

#1  0x0024 in ?? ()

No symbol table info available.

#2  0x00020004 in ?? ()

No symbol table info available.

#3  0x7ffe32a6f9c0 in ?? ()

No symbol table info available.

#4  0x7fbf8baef57c in ?? ()

No symbol table info available.

#5  0x00020002 in ?? ()

No symbol table info available.

#6  0x7ffe32a6f9d0 in ?? ()

No symbol table info available.

#7  0x7fbf8aa8bf00 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

No symbol table info available.

#8  0x7fbf8b53f000 in ?? ()

No symbol table info available.

#9  0x0014 in ?? ()

No symbol table info available.

#10 0x in ?? ()

No symbol table info available.

(gdb)





(gdb) bt full

#0  0x7fe03fc9cc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56

resultvar = 0

pid = 36112

selftid = 36112

#1  0x7fe03fca0028 in __GI_abort () at abort.c:89

save_stage = 2

act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction =
0x0}, sa_mask = {__val = {140596270402586, 8589934592, 64, 3, 33,
140596283430288,

  140596283430040, 18446744073709551614, 140596264663692,
140596282823192, 3, 33, 140596264116466, 3, 8885408, 1}}, sa_flags =
8885408,

  sa_restorer = 0x1}

sigs = {__val = {32, 0 }}

#2  0x7fdf1ebfaa62 in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/tls_mgm.so

No symbol table info available.

#3  0x7fdf1e610fcd in CRYPTO_free () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

No symbol table info available.

#4  0x7fdf1e9c8c16 in SSL_SESSION_free () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#5  0x7fdf1e9c6f5d in SSL_free () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#6  0x7fdf1e38a327 in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so

No symbol table info available.

#7  0x00593114 in ?? ()

No symbol table info available.

#8  0x005933b0 in ?? ()

No symbol table info available.

#9  0x004147f4 in ?? ()

No symbol table info available.

#10 0x004154db in ?? ()

No symbol table info available.

#11 0x0059d087 in tcp_start_processes ()

No symbol table info available.

#12 0x00419cda in main ()

No symbol table info available.





(gdb) bt full

#0  0x7fe03fc9cc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56

resultvar = 0

pid = 35939

selftid = 35939

#1  0x7fe03fca0028 in __GI_abort () at abort.c:89

save_stage = 2

act = {__sigaction_handler = {sa_handler = 0x1, sa_sigaction =
0x1}, sa_mask = {__val = {0, 140596279116408, 140601127703847, 1, 0,
6087545,

  140601119395120, 0, 140596279116408, 8739288,
140601127732437, 1, 140601120396285, 0, 0, 140601123293024}}, sa_flags =
0, sa_restorer = 0x0}

sigs = {__val = {32, 0 }}

#2  

[OpenSIPS-Users] OpenSIPS crash with core dump

[SamyGo]

Hi All,
I've been seeing some crashes in my opensips servers:


*version:* opensips 2.2.1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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.
main.c compiled on 16:33:09 Jan 12 2017 with gcc 4.8

*Operatin System:* Ubuntu 14.04.5 LTS

*Core File:*

(gdb) bt full

#0  strlen () at ../sysdeps/x86_64/strlen.S:106

No locals.

#1  0x7f55a8a32f59 in i2d_SSL_SESSION () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#2  0x7f55a8a07bd5 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#3  0x7f55a8a08960 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#4  0x7f55a83f5a7f in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so

No symbol table info available.

#5  0x7f55a83fe880 in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so

No symbol table info available.

#6  0x005a372d in ?? ()

No symbol table info available.

#7  0x005a4dcb in tcp_worker_proc ()

No symbol table info available.

#8  0x0059cbb9 in tcp_start_processes ()

No symbol table info available.

#9  0x00419cda in main ()

No symbol table info available.




*Another Crash trace:*


(gdb) bt full

#0  0x7fc0abe039da in strtok () at ../sysdeps/x86_64/strtok.S:186

No locals.

#1  0x0024 in ?? ()

No symbol table info available.

#2  0x00020004 in ?? ()

No symbol table info available.

#3  0x7ffe32a6f9c0 in ?? ()

No symbol table info available.

#4  0x7fbf8baef57c in ?? ()

No symbol table info available.

#5  0x00020002 in ?? ()

No symbol table info available.

#6  0x7ffe32a6f9d0 in ?? ()

No symbol table info available.

#7  0x7fbf8aa8bf00 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

No symbol table info available.

#8  0x7fbf8b53f000 in ?? ()

No symbol table info available.

#9  0x0014 in ?? ()

No symbol table info available.

#10 0x in ?? ()

No symbol table info available.

(gdb)





(gdb) bt full

#0  0x7fe03fc9cc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56

resultvar = 0

pid = 36112

selftid = 36112

#1  0x7fe03fca0028 in __GI_abort () at abort.c:89

save_stage = 2

act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction =
0x0}, sa_mask = {__val = {140596270402586, 8589934592, 64, 3, 33,
140596283430288,

  140596283430040, 18446744073709551614, 140596264663692,
140596282823192, 3, 33, 140596264116466, 3, 8885408, 1}}, sa_flags =
8885408,

  sa_restorer = 0x1}

sigs = {__val = {32, 0 }}

#2  0x7fdf1ebfaa62 in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/tls_mgm.so

No symbol table info available.

#3  0x7fdf1e610fcd in CRYPTO_free () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

No symbol table info available.

#4  0x7fdf1e9c8c16 in SSL_SESSION_free () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#5  0x7fdf1e9c6f5d in SSL_free () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0

No symbol table info available.

#6  0x7fdf1e38a327 in ?? () from
/home/opensips/local/opensips/2_21/lib64/opensips/modules/proto_tls.so

No symbol table info available.

#7  0x00593114 in ?? ()

No symbol table info available.

#8  0x005933b0 in ?? ()

No symbol table info available.

#9  0x004147f4 in ?? ()

No symbol table info available.

#10 0x004154db in ?? ()

No symbol table info available.

#11 0x0059d087 in tcp_start_processes ()

No symbol table info available.

#12 0x00419cda in main ()

No symbol table info available.





(gdb) bt full

#0  0x7fe03fc9cc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56

resultvar = 0

pid = 35939

selftid = 35939

#1  0x7fe03fca0028 in __GI_abort () at abort.c:89

save_stage = 2

act = {__sigaction_handler = {sa_handler = 0x1, sa_sigaction =
0x1}, sa_mask = {__val = {0, 140596279116408, 140601127703847, 1, 0,
6087545,

  140601119395120, 0, 140596279116408, 8739288,
140601127732437, 1, 140601120396285, 0, 0, 140601123293024}}, sa_flags = 0,
sa_restorer = 0x0}

sigs = {__val = {32, 0 }}

#2  0x00443a3b in ?? ()

No symbol table info available.

#3  

No locals.

#4  0x7fe03fd312a7 in sched_yield () at
../sysdeps/unix/syscall-template.S:81

No locals.

#5  0x0059b7ab in tcp_destroy ()

No symbol table info available.

#6  0x004441ab in cleanup ()

No symbol table info available.

#7  0x00444d67 in handle_sigs ()

No symbol 

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Denis,

Could you put in an archive the core file and corresponding opensips 
binary and modules - and have them available for download somewhere ? 
and I try to look into on my side.


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/12/2017 05:11 PM, Denis wrote:

Hello, Bogdan!
Is there any additional information that i should gather about problem?
Or everything is clear?
Thank you.
--
С уважением, Денис.
Best regards, Denis
06.04.2017, 15:18, "Denis via Users" :
Bogdan, I copied tar to the backup server and restore opensips from 
tar there (on the same path as in main was).
Now, when entering to the gdb on backup, it does not show any warning 
messages, but the result is the same

f 10
#0  0x in ?? ()
(gdb) p p_cell->method.s
No symbol "p_cell" in current context.
(gdb) p p_cell->uas.request
No symbol "p_cell" in current context.
(gdb) p p_cell->uas.status
No symbol "p_cell" in current context.
--
С уважением, Денис.
Best regards, Denis
06.04.2017, 14:38, "Bogdan-Andrei Iancu" >:

Oh, that is good !

When starting gdb, point to the old opensips binary. To solve the 
problem with the modules (which are libraries), see:

http://stackoverflow.com/questions/84341/how-do-i-prepend-a-directory-the-library-path-when-loading-a-core-file-in-gdb-on
(the first answer)

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/06/2017 12:31 PM, Denis wrote:
Before making upgrade i made tar archive of the directory where 
opensips has been installed. Can this help us?

It was crash on time only. I do not think, that o can reproduce it.
--
С уважением, Денис.
Best regards, Denis
06.04.2017, 12:27, "Bogdan-Andrei Iancu"  
:
yeah, the opensips binary and module libs do not match the 
corefile anymore :(.Do you have the old build ?  Also, was 
this crash on time only ? or can you reproduce it ?


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/06/2017 12:17 PM, Denis wrote:

Hello, Bogdan.
Probably i made a big mistake.
I have already updated Opensips from latest git (to solve another 
problem)

So, when i enter in gdb i get such warning message
[New LWP 14909]
warning: .dynamic section for 
"/usr/local/opensips2.2/lib64/opensips/modules/dialog.so" is not 
at the expected address (wrong library or version mismatch?)

Anyway,
f 10
#10 0x7fdf6c4ac158 in ?? ()
p p_cell->method.s
No symbol "p_cell" in current context.
p p_cell->uas.request
No symbol "p_cell" in current context.
p p_cell->uas.status
No symbol "p_cell" in current context.
--
С уважением, Денис.
Best regards, Denis
06.04.2017, 11:08, "Bogdan-Andrei Iancu"  
:

Hi Denis,

Please get some more info from the corefile :

f 10
p p_cell->method.s
p p_cell->uas.request
p p_cell->uas.status

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/05/2017 11:56 AM, Denis wrote:

Ok, Bogdan, I'll be waiting any result.
Thank you.
--
С уважением, Денис.
Best regards, Denis
05.04.2017, 11:53, "Bogdan-Andrei Iancu"  
:

Hi Denis,

Many thanks for the output - this confirm a suspicious of mine 
in regards to the cause of the crash - let me try to see if we 
can reproduce it on our side or if we need more info from your 
side.

Please do not delete the corefile for the moment :)

Best 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/05/2017 11:03 AM, Denis wrote:

Hello, Bogdan!
f 5
#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) 
at dlg_hash.c:183

183 destroy_dlg_callbacks_list(dlg->cbs.first);
p *dlg->cbs.first
$1 = {types = 96, callback = 0x7fdf67531300 
, param = 0x0, callback_param_free = 
0x7fdf675318fe , next = 0x7fdf84191080}

p *dlg->cbs.first->next
$2 = {types = 96, callback = 0x7fdf67531300 
, param = 0x7fdf83c9f340, 
callback_param_free = 0x7fdf675318fe , 
next = 0x0}

p *dlg->cbs.first->next->next
Cannot access memory at address 0x0
p *dlg->cbs.first->next->next->next
Cannot access memory at address 0x20

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Hello, Bogdan! Is there any additional information that i should gather about problem?Or everything is clear? Thank you. -- С уважением, Денис.Best regards, Denis 06.04.2017, 15:18, "Denis via Users" :Bogdan, I copied tar to the backup server and restore opensips from tar there (on the same path as in main was).Now, when entering to the gdb on backup, it does not show any warning messages, but the result is the same f 10#0  0x in ?? ()(gdb) p p_cell->method.sNo symbol "p_cell" in current context.(gdb) p p_cell->uas.requestNo symbol "p_cell" in current context.(gdb) p p_cell->uas.statusNo symbol "p_cell" in current context. -- С уважением, Денис.Best regards, Denis   06.04.2017, 14:38, "Bogdan-Andrei Iancu" :Oh, that is good !When starting gdb, point to the old opensips binary. To solve the problem with the modules (which are libraries), see:    http://stackoverflow.com/questions/84341/how-do-i-prepend-a-directory-the-library-path-when-loading-a-core-file-in-gdb-on(the first answer)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/06/2017 12:31 PM, Denis wrote:Before making upgrade i made tar archive of the directory where opensips has been installed. Can this help us?It was crash on time only. I do not think, that o can reproduce it. -- С уважением, Денис.Best regards, Denis   06.04.2017, 12:27, "Bogdan-Andrei Iancu" :yeah, the opensips binary and module libs do not match the corefile anymore :(.Do you have the old build ?  Also, was this crash on time only ? or can you reproduce it ?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/06/2017 12:17 PM, Denis wrote:Hello, Bogdan. Probably i made a big mistake.I have already updated Opensips from latest git (to solve another problem) So, when i enter in gdb i get such warning message [New LWP 14909]warning: .dynamic section for "/usr/local/opensips2.2/lib64/opensips/modules/dialog.so" is not at the expected address (wrong library or version mismatch?) Anyway, f 10#10 0x7fdf6c4ac158 in ?? () p p_cell->method.sNo symbol "p_cell" in current context. p p_cell->uas.requestNo symbol "p_cell" in current context. p p_cell->uas.statusNo symbol "p_cell" in current context. -- С уважением, Денис.Best regards, Denis   06.04.2017, 11:08, "Bogdan-Andrei Iancu" :Hi Denis,Please get some more info from the corefile :    f 10    p p_cell->method.s    p p_cell->uas.request    p p_cell->uas.statusThanks,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/05/2017 11:56 AM, Denis wrote:Ok, Bogdan, I'll be waiting any result. Thank you. -- С уважением, Денис.Best regards, Denis   05.04.2017, 11:53, "Bogdan-Andrei Iancu" :Hi Denis,Many thanks for the output - this confirm a suspicious of mine in regards to the cause of the crash - let me try to see if we can reproduce it on our side or if we need more info from your side.Please do not delete the corefile for the moment :)Best 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/05/2017 11:03 AM, Denis wrote:Hello, Bogdan! f 5#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at dlg_hash.c:183183                     destroy_dlg_callbacks_list(dlg->cbs.first); p *dlg->cbs.first$1 = {types = 96, callback = 0x7fdf67531300 , param = 0x0, callback_param_free = 0x7fdf675318fe , next = 0x7fdf84191080} p *dlg->cbs.first->next$2 = {types = 96, callback = 0x7fdf67531300 , param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe , next = 0x0} p *dlg->cbs.first->next->nextCannot access memory at address 0x0 p *dlg->cbs.first->next->next->nextCannot access memory at address 0x20 and so on with at address 0x20 -- С уважением, Денис.Best regards, Denis   04.04.2017, 18:43, "Bogdan-Andrei Iancu" :Super :)we got to something useful.Now, again in GDB please do:f 5p *dlg->cbs.firstp *dlg->cbs.first->nextp *dlg->cbs.first->next->nextand keep adding "->next" until you get error from gdb.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 06:07 PM, Денис Путято wrote:Sorry, Bogdan, i missed that I found such CRITICAL message"CRITICAL:core:qm_free: freeing already freed pointer, first free: acc_logic.c: dlg_free_acc_mask(211) - aborting" And after that and till 

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Bogdan, I copied tar to the backup server and restore opensips from tar there (on the same path as in main was).Now, when entering to the gdb on backup, it does not show any warning messages, but the result is the same f 10#0  0x in ?? ()(gdb) p p_cell->method.sNo symbol "p_cell" in current context.(gdb) p p_cell->uas.requestNo symbol "p_cell" in current context.(gdb) p p_cell->uas.statusNo symbol "p_cell" in current context. -- С уважением, Денис.Best regards, Denis   06.04.2017, 14:38, "Bogdan-Andrei Iancu" :Oh, that is good !When starting gdb, point to the old opensips binary. To solve the problem with the modules (which are libraries), see:    http://stackoverflow.com/questions/84341/how-do-i-prepend-a-directory-the-library-path-when-loading-a-core-file-in-gdb-on(the first answer)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/06/2017 12:31 PM, Denis wrote:Before making upgrade i made tar archive of the directory where opensips has been installed. Can this help us?It was crash on time only. I do not think, that o can reproduce it. -- С уважением, Денис.Best regards, Denis   06.04.2017, 12:27, "Bogdan-Andrei Iancu" :yeah, the opensips binary and module libs do not match the corefile anymore :(.Do you have the old build ?  Also, was this crash on time only ? or can you reproduce it ?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/06/2017 12:17 PM, Denis wrote:Hello, Bogdan. Probably i made a big mistake.I have already updated Opensips from latest git (to solve another problem) So, when i enter in gdb i get such warning message [New LWP 14909]warning: .dynamic section for "/usr/local/opensips2.2/lib64/opensips/modules/dialog.so" is not at the expected address (wrong library or version mismatch?) Anyway, f 10#10 0x7fdf6c4ac158 in ?? () p p_cell->method.sNo symbol "p_cell" in current context. p p_cell->uas.requestNo symbol "p_cell" in current context. p p_cell->uas.statusNo symbol "p_cell" in current context. -- С уважением, Денис.Best regards, Denis   06.04.2017, 11:08, "Bogdan-Andrei Iancu" :Hi Denis,Please get some more info from the corefile :    f 10    p p_cell->method.s    p p_cell->uas.request    p p_cell->uas.statusThanks,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/05/2017 11:56 AM, Denis wrote:Ok, Bogdan, I'll be waiting any result. Thank you. -- С уважением, Денис.Best regards, Denis   05.04.2017, 11:53, "Bogdan-Andrei Iancu" :Hi Denis,Many thanks for the output - this confirm a suspicious of mine in regards to the cause of the crash - let me try to see if we can reproduce it on our side or if we need more info from your side.Please do not delete the corefile for the moment :)Best 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/05/2017 11:03 AM, Denis wrote:Hello, Bogdan! f 5#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at dlg_hash.c:183183                     destroy_dlg_callbacks_list(dlg->cbs.first); p *dlg->cbs.first$1 = {types = 96, callback = 0x7fdf67531300 , param = 0x0, callback_param_free = 0x7fdf675318fe , next = 0x7fdf84191080} p *dlg->cbs.first->next$2 = {types = 96, callback = 0x7fdf67531300 , param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe , next = 0x0} p *dlg->cbs.first->next->nextCannot access memory at address 0x0 p *dlg->cbs.first->next->next->nextCannot access memory at address 0x20 and so on with at address 0x20 -- С уважением, Денис.Best regards, Denis   04.04.2017, 18:43, "Bogdan-Andrei Iancu" :Super :)we got to something useful.Now, again in GDB please do:f 5p *dlg->cbs.firstp *dlg->cbs.first->nextp *dlg->cbs.first->next->nextand keep adding "->next" until you get error from gdb.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 06:07 PM, Денис Путято wrote:Sorry, Bogdan, i missed that I found such CRITICAL message"CRITICAL:core:qm_free: freeing already freed pointer, first free: acc_logic.c: dlg_free_acc_mask(211) - aborting" And after that and till crash only "WARNING:core:utimer_ticker:" reports in syslog. (gdb)f 2#2  0x00515592 in qm_free (qm=, p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 "acc_logic.c",    func=func@entry=0x7fdf6753af90 

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Oh, that is good !

When starting gdb, point to the old opensips binary. To solve the 
problem with the modules (which are libraries), see:

http://stackoverflow.com/questions/84341/how-do-i-prepend-a-directory-the-library-path-when-loading-a-core-file-in-gdb-on
(the first answer)

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/06/2017 12:31 PM, Denis wrote:
Before making upgrade i made tar archive of the directory where 
opensips has been installed. Can this help us?

It was crash on time only. I do not think, that o can reproduce it.
--
С уважением, Денис.
Best regards, Denis
06.04.2017, 12:27, "Bogdan-Andrei Iancu" :
yeah, the opensips binary and module libs do not match the corefile 
anymore :(.Do you have the old build ?  Also, was this crash on 
time only ? or can you reproduce it ?


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/06/2017 12:17 PM, Denis wrote:

Hello, Bogdan.
Probably i made a big mistake.
I have already updated Opensips from latest git (to solve another 
problem)

So, when i enter in gdb i get such warning message
[New LWP 14909]
warning: .dynamic section for 
"/usr/local/opensips2.2/lib64/opensips/modules/dialog.so" is not at 
the expected address (wrong library or version mismatch?)

Anyway,
f 10
#10 0x7fdf6c4ac158 in ?? ()
p p_cell->method.s
No symbol "p_cell" in current context.
p p_cell->uas.request
No symbol "p_cell" in current context.
p p_cell->uas.status
No symbol "p_cell" in current context.
--
С уважением, Денис.
Best regards, Denis
06.04.2017, 11:08, "Bogdan-Andrei Iancu"  
:

Hi Denis,

Please get some more info from the corefile :

f 10
p p_cell->method.s
p p_cell->uas.request
p p_cell->uas.status

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/05/2017 11:56 AM, Denis wrote:

Ok, Bogdan, I'll be waiting any result.
Thank you.
--
С уважением, Денис.
Best regards, Denis
05.04.2017, 11:53, "Bogdan-Andrei Iancu"  
:

Hi Denis,

Many thanks for the output - this confirm a suspicious of mine in 
regards to the cause of the crash - let me try to see if we can 
reproduce it on our side or if we need more info from your side.

Please do not delete the corefile for the moment :)

Best 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/05/2017 11:03 AM, Denis wrote:

Hello, Bogdan!
f 5
#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at 
dlg_hash.c:183

183 destroy_dlg_callbacks_list(dlg->cbs.first);
p *dlg->cbs.first
$1 = {types = 96, callback = 0x7fdf67531300 , 
param = 0x0, callback_param_free = 0x7fdf675318fe 
, next = 0x7fdf84191080}

p *dlg->cbs.first->next
$2 = {types = 96, callback = 0x7fdf67531300 , 
param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe 
, next = 0x0}

p *dlg->cbs.first->next->next
Cannot access memory at address 0x0
p *dlg->cbs.first->next->next->next
Cannot access memory at address 0x20
and so on with at address 0x20
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 18:43, "Bogdan-Andrei Iancu"  
:

Super :)we got to something useful.

Now, again in GDB please do:

f 5
p *dlg->cbs.first
p *dlg->cbs.first->next
p *dlg->cbs.first->next->next

and keep adding "->next" until you get error from gdb.

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 06:07 PM, Денис Путято wrote:

Sorry, Bogdan, i missed that
I found such CRITICAL message
"CRITICAL:core:qm_free: freeing already freed pointer, first 
free: acc_logic.c: dlg_free_acc_mask(211) - aborting"
And after that and till crash only 
"WARNING:core:utimer_ticker:" reports in syslog.

(gdb)
f 2
#2  0x00515592 in qm_free (qm=, 
p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 
"acc_logic.c",
func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> 
"dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483

483 abort();
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))
$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Before making upgrade i made tar archive of the directory where opensips has been installed. Can this help us?It was crash on time only. I do not think, that o can reproduce it. -- С уважением, Денис.Best regards, Denis   06.04.2017, 12:27, "Bogdan-Andrei Iancu" :yeah, the opensips binary and module libs do not match the corefile anymore :(.Do you have the old build ?  Also, was this crash on time only ? or can you reproduce it ?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/06/2017 12:17 PM, Denis wrote:Hello, Bogdan. Probably i made a big mistake.I have already updated Opensips from latest git (to solve another problem) So, when i enter in gdb i get such warning message [New LWP 14909]warning: .dynamic section for "/usr/local/opensips2.2/lib64/opensips/modules/dialog.so" is not at the expected address (wrong library or version mismatch?) Anyway, f 10#10 0x7fdf6c4ac158 in ?? () p p_cell->method.sNo symbol "p_cell" in current context. p p_cell->uas.requestNo symbol "p_cell" in current context. p p_cell->uas.statusNo symbol "p_cell" in current context. -- С уважением, Денис.Best regards, Denis   06.04.2017, 11:08, "Bogdan-Andrei Iancu" :Hi Denis,Please get some more info from the corefile :    f 10    p p_cell->method.s    p p_cell->uas.request    p p_cell->uas.statusThanks,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/05/2017 11:56 AM, Denis wrote:Ok, Bogdan, I'll be waiting any result. Thank you. -- С уважением, Денис.Best regards, Denis   05.04.2017, 11:53, "Bogdan-Andrei Iancu" :Hi Denis,Many thanks for the output - this confirm a suspicious of mine in regards to the cause of the crash - let me try to see if we can reproduce it on our side or if we need more info from your side.Please do not delete the corefile for the moment :)Best 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/05/2017 11:03 AM, Denis wrote:Hello, Bogdan! f 5#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at dlg_hash.c:183183                     destroy_dlg_callbacks_list(dlg->cbs.first); p *dlg->cbs.first$1 = {types = 96, callback = 0x7fdf67531300 , param = 0x0, callback_param_free = 0x7fdf675318fe , next = 0x7fdf84191080} p *dlg->cbs.first->next$2 = {types = 96, callback = 0x7fdf67531300 , param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe , next = 0x0} p *dlg->cbs.first->next->nextCannot access memory at address 0x0 p *dlg->cbs.first->next->next->nextCannot access memory at address 0x20 and so on with at address 0x20 -- С уважением, Денис.Best regards, Denis   04.04.2017, 18:43, "Bogdan-Andrei Iancu" :Super :)we got to something useful.Now, again in GDB please do:f 5p *dlg->cbs.firstp *dlg->cbs.first->nextp *dlg->cbs.first->next->nextand keep adding "->next" until you get error from gdb.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 06:07 PM, Денис Путято wrote:Sorry, Bogdan, i missed that I found such CRITICAL message"CRITICAL:core:qm_free: freeing already freed pointer, first free: acc_logic.c: dlg_free_acc_mask(211) - aborting" And after that and till crash only "WARNING:core:utimer_ticker:" reports in syslog. (gdb)f 2#2  0x00515592 in qm_free (qm=, p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 "acc_logic.c",    func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483483                     abort();  p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 140597661320880}, file = 0x7fdf6753ad62 "acc_logic.c", func = 0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line = 211,  check = 17361641481138401520} -- С уважением, Денис.Best regards, Denis   04.04.2017, 17:58, "Bogdan-Andrei Iancu" :The RADIUS part is not relevant.Still you didn;t answer to my question on the CRITICAL error - according to the backtrace, you should have a CRITICAL message in the opensips log, just before the crash.In GDB, do:    f 2    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))  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 05:55 PM, Denis wrote:During crash there was another problem with LAN 

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

yeah, the opensips binary and module libs do not match the corefile 
anymore :(.Do you have the old build ?  Also, was this crash on time 
only ? or can you reproduce it ?


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/06/2017 12:17 PM, Denis wrote:

Hello, Bogdan.
Probably i made a big mistake.
I have already updated Opensips from latest git (to solve another problem)
So, when i enter in gdb i get such warning message
[New LWP 14909]
warning: .dynamic section for 
"/usr/local/opensips2.2/lib64/opensips/modules/dialog.so" is not at 
the expected address (wrong library or version mismatch?)

Anyway,
f 10
#10 0x7fdf6c4ac158 in ?? ()
p p_cell->method.s
No symbol "p_cell" in current context.
p p_cell->uas.request
No symbol "p_cell" in current context.
p p_cell->uas.status
No symbol "p_cell" in current context.
--
С уважением, Денис.
Best regards, Denis
06.04.2017, 11:08, "Bogdan-Andrei Iancu" :

Hi Denis,

Please get some more info from the corefile :

f 10
p p_cell->method.s
p p_cell->uas.request
p p_cell->uas.status

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/05/2017 11:56 AM, Denis wrote:

Ok, Bogdan, I'll be waiting any result.
Thank you.
--
С уважением, Денис.
Best regards, Denis
05.04.2017, 11:53, "Bogdan-Andrei Iancu"  
:

Hi Denis,

Many thanks for the output - this confirm a suspicious of mine in 
regards to the cause of the crash - let me try to see if we can 
reproduce it on our side or if we need more info from your side.

Please do not delete the corefile for the moment :)

Best 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/05/2017 11:03 AM, Denis wrote:

Hello, Bogdan!
f 5
#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at 
dlg_hash.c:183

183 destroy_dlg_callbacks_list(dlg->cbs.first);
p *dlg->cbs.first
$1 = {types = 96, callback = 0x7fdf67531300 , 
param = 0x0, callback_param_free = 0x7fdf675318fe 
, next = 0x7fdf84191080}

p *dlg->cbs.first->next
$2 = {types = 96, callback = 0x7fdf67531300 , 
param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe 
, next = 0x0}

p *dlg->cbs.first->next->next
Cannot access memory at address 0x0
p *dlg->cbs.first->next->next->next
Cannot access memory at address 0x20
and so on with at address 0x20
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 18:43, "Bogdan-Andrei Iancu"  
:

Super :)we got to something useful.

Now, again in GDB please do:

f 5
p *dlg->cbs.first
p *dlg->cbs.first->next
p *dlg->cbs.first->next->next

and keep adding "->next" until you get error from gdb.

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 06:07 PM, Денис Путято wrote:

Sorry, Bogdan, i missed that
I found such CRITICAL message
"CRITICAL:core:qm_free: freeing already freed pointer, first 
free: acc_logic.c: dlg_free_acc_mask(211) - aborting"
And after that and till crash only 
"WARNING:core:utimer_ticker:" reports in syslog.

(gdb)
f 2
#2  0x00515592 in qm_free (qm=, 
p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 
"acc_logic.c",
func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> 
"dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483

483 abort();
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))
$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 
140597661320880}, file = 0x7fdf6753ad62 "acc_logic.c", func = 
0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line = 211,

  check = 17361641481138401520}
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 17:58, "Bogdan-Andrei Iancu"  
:

The RADIUS part is not relevant.

Still you didn;t answer to my question on the CRITICAL error - 
according to the backtrace, you should have a CRITICAL message 
in the opensips log, just before the crash.


In GDB, do:
f 2
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))

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 05:55 PM, Denis wrote:

During 

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Hello, Bogdan. Probably i made a big mistake.I have already updated Opensips from latest git (to solve another problem) So, when i enter in gdb i get such warning message [New LWP 14909]warning: .dynamic section for "/usr/local/opensips2.2/lib64/opensips/modules/dialog.so" is not at the expected address (wrong library or version mismatch?) Anyway, f 10#10 0x7fdf6c4ac158 in ?? () p p_cell->method.sNo symbol "p_cell" in current context. p p_cell->uas.requestNo symbol "p_cell" in current context. p p_cell->uas.statusNo symbol "p_cell" in current context. -- С уважением, Денис.Best regards, Denis   06.04.2017, 11:08, "Bogdan-Andrei Iancu" :Hi Denis,Please get some more info from the corefile :    f 10    p p_cell->method.s    p p_cell->uas.request    p p_cell->uas.statusThanks,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/05/2017 11:56 AM, Denis wrote:Ok, Bogdan, I'll be waiting any result. Thank you. -- С уважением, Денис.Best regards, Denis   05.04.2017, 11:53, "Bogdan-Andrei Iancu" :Hi Denis,Many thanks for the output - this confirm a suspicious of mine in regards to the cause of the crash - let me try to see if we can reproduce it on our side or if we need more info from your side.Please do not delete the corefile for the moment :)Best 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/05/2017 11:03 AM, Denis wrote:Hello, Bogdan! f 5#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at dlg_hash.c:183183                     destroy_dlg_callbacks_list(dlg->cbs.first); p *dlg->cbs.first$1 = {types = 96, callback = 0x7fdf67531300 , param = 0x0, callback_param_free = 0x7fdf675318fe , next = 0x7fdf84191080} p *dlg->cbs.first->next$2 = {types = 96, callback = 0x7fdf67531300 , param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe , next = 0x0} p *dlg->cbs.first->next->nextCannot access memory at address 0x0 p *dlg->cbs.first->next->next->nextCannot access memory at address 0x20 and so on with at address 0x20 -- С уважением, Денис.Best regards, Denis   04.04.2017, 18:43, "Bogdan-Andrei Iancu" :Super :)we got to something useful.Now, again in GDB please do:f 5p *dlg->cbs.firstp *dlg->cbs.first->nextp *dlg->cbs.first->next->nextand keep adding "->next" until you get error from gdb.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 06:07 PM, Денис Путято wrote:Sorry, Bogdan, i missed that I found such CRITICAL message"CRITICAL:core:qm_free: freeing already freed pointer, first free: acc_logic.c: dlg_free_acc_mask(211) - aborting" And after that and till crash only "WARNING:core:utimer_ticker:" reports in syslog. (gdb)f 2#2  0x00515592 in qm_free (qm=, p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 "acc_logic.c",    func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483483                     abort();  p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 140597661320880}, file = 0x7fdf6753ad62 "acc_logic.c", func = 0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line = 211,  check = 17361641481138401520} -- С уважением, Денис.Best regards, Denis   04.04.2017, 17:58, "Bogdan-Andrei Iancu" :The RADIUS part is not relevant.Still you didn;t answer to my question on the CRITICAL error - according to the backtrace, you should have a CRITICAL message in the opensips log, just before the crash.In GDB, do:    f 2    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))  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 05:55 PM, Denis wrote:During crash there was another problem with LAN network.Because of this problem Opensips could not connect to radius server.rc_ip_hostname: couldn't look up host by addr: xxrc_send_server: no reply from RADIUS server unknown:1812 No more critical messages. Bogdan, i am sorry, but"in frame 2". What does it mean?  -- С уважением, Денис.Best regards, Denis   04.04.2017, 16:35, "Bogdan-Andrei Iancu" :Any CRITICAL message into the log before the crash ?also, in gdb in frame 2, please print:    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))   Thanks,Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Hi Denis,

Please get some more info from the corefile :

f 10
p p_cell->method.s
p p_cell->uas.request
p p_cell->uas.status

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/05/2017 11:56 AM, Denis wrote:

Ok, Bogdan, I'll be waiting any result.
Thank you.
--
С уважением, Денис.
Best regards, Denis
05.04.2017, 11:53, "Bogdan-Andrei Iancu" :

Hi Denis,

Many thanks for the output - this confirm a suspicious of mine in 
regards to the cause of the crash - let me try to see if we can 
reproduce it on our side or if we need more info from your side.

Please do not delete the corefile for the moment :)

Best 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/05/2017 11:03 AM, Denis wrote:

Hello, Bogdan!
f 5
#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at 
dlg_hash.c:183

183 destroy_dlg_callbacks_list(dlg->cbs.first);
p *dlg->cbs.first
$1 = {types = 96, callback = 0x7fdf67531300 , 
param = 0x0, callback_param_free = 0x7fdf675318fe 
, next = 0x7fdf84191080}

p *dlg->cbs.first->next
$2 = {types = 96, callback = 0x7fdf67531300 , 
param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe 
, next = 0x0}

p *dlg->cbs.first->next->next
Cannot access memory at address 0x0
p *dlg->cbs.first->next->next->next
Cannot access memory at address 0x20
and so on with at address 0x20
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 18:43, "Bogdan-Andrei Iancu"  
:

Super :)we got to something useful.

Now, again in GDB please do:

f 5
p *dlg->cbs.first
p *dlg->cbs.first->next
p *dlg->cbs.first->next->next

and keep adding "->next" until you get error from gdb.

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 06:07 PM, Денис Путято wrote:

Sorry, Bogdan, i missed that
I found such CRITICAL message
"CRITICAL:core:qm_free: freeing already freed pointer, first free: 
acc_logic.c: dlg_free_acc_mask(211) - aborting"
And after that and till crash only 
"WARNING:core:utimer_ticker:" reports in syslog.

(gdb)
f 2
#2  0x00515592 in qm_free (qm=, 
p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 
"acc_logic.c",
func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> 
"dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483

483 abort();
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))
$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 
140597661320880}, file = 0x7fdf6753ad62 "acc_logic.c", func = 
0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line = 211,

  check = 17361641481138401520}
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 17:58, "Bogdan-Andrei Iancu"  
:

The RADIUS part is not relevant.

Still you didn;t answer to my question on the CRITICAL error - 
according to the backtrace, you should have a CRITICAL message in 
the opensips log, just before the crash.


In GDB, do:
f 2
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))

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 05:55 PM, Denis wrote:

During crash there was another problem with LAN network.
Because of this problem Opensips could not connect to radius server.
rc_ip_hostname: couldn't look up host by addr: xx
rc_send_server: no reply from RADIUS server unknown:1812
No more critical messages.
Bogdan, i am sorry, but
"in frame 2". What does it mean?
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 16:35, "Bogdan-Andrei Iancu"  
:

Any CRITICAL message into the log before the crash ?

also, in gdb in frame 2, please print:
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))


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 03:19 PM, Denis wrote:

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
--
С уважением, 

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Ok, Bogdan, I'll be waiting any result. Thank you. -- С уважением, Денис.Best regards, Denis   05.04.2017, 11:53, "Bogdan-Andrei Iancu" :Hi Denis,Many thanks for the output - this confirm a suspicious of mine in regards to the cause of the crash - let me try to see if we can reproduce it on our side or if we need more info from your side.Please do not delete the corefile for the moment :)Best 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/05/2017 11:03 AM, Denis wrote:Hello, Bogdan! f 5#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at dlg_hash.c:183183                     destroy_dlg_callbacks_list(dlg->cbs.first); p *dlg->cbs.first$1 = {types = 96, callback = 0x7fdf67531300 , param = 0x0, callback_param_free = 0x7fdf675318fe , next = 0x7fdf84191080} p *dlg->cbs.first->next$2 = {types = 96, callback = 0x7fdf67531300 , param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe , next = 0x0} p *dlg->cbs.first->next->nextCannot access memory at address 0x0 p *dlg->cbs.first->next->next->nextCannot access memory at address 0x20 and so on with at address 0x20 -- С уважением, Денис.Best regards, Denis   04.04.2017, 18:43, "Bogdan-Andrei Iancu" :Super :)we got to something useful.Now, again in GDB please do:f 5p *dlg->cbs.firstp *dlg->cbs.first->nextp *dlg->cbs.first->next->nextand keep adding "->next" until you get error from gdb.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 06:07 PM, Денис Путято wrote:Sorry, Bogdan, i missed that I found such CRITICAL message"CRITICAL:core:qm_free: freeing already freed pointer, first free: acc_logic.c: dlg_free_acc_mask(211) - aborting" And after that and till crash only "WARNING:core:utimer_ticker:" reports in syslog. (gdb)f 2#2  0x00515592 in qm_free (qm=, p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 "acc_logic.c",    func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483483                     abort();  p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 140597661320880}, file = 0x7fdf6753ad62 "acc_logic.c", func = 0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line = 211,  check = 17361641481138401520} -- С уважением, Денис.Best regards, Denis   04.04.2017, 17:58, "Bogdan-Andrei Iancu" :The RADIUS part is not relevant.Still you didn;t answer to my question on the CRITICAL error - according to the backtrace, you should have a CRITICAL message in the opensips log, just before the crash.In GDB, do:    f 2    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))  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 05:55 PM, Denis wrote:During crash there was another problem with LAN network.Because of this problem Opensips could not connect to radius server.rc_ip_hostname: couldn't look up host by addr: xxrc_send_server: no reply from RADIUS server unknown:1812 No more critical messages. Bogdan, i am sorry, but"in frame 2". What does it mean?  -- С уважением, Денис.Best regards, Denis   04.04.2017, 16:35, "Bogdan-Andrei Iancu" :Any CRITICAL message into the log before the crash ?also, in gdb in frame 2, please print:    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))   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 03:19 PM, Denis wrote: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" :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_endThanks,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 Opensips2. As a 

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Hi Denis,

Many thanks for the output - this confirm a suspicious of mine in 
regards to the cause of the crash - let me try to see if we can 
reproduce it on our side or if we need more info from your side.

Please do not delete the corefile for the moment :)

Best 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/05/2017 11:03 AM, Denis wrote:

Hello, Bogdan!
f 5
#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at 
dlg_hash.c:183

183 destroy_dlg_callbacks_list(dlg->cbs.first);
p *dlg->cbs.first
$1 = {types = 96, callback = 0x7fdf67531300 , param 
= 0x0, callback_param_free = 0x7fdf675318fe , next 
= 0x7fdf84191080}

p *dlg->cbs.first->next
$2 = {types = 96, callback = 0x7fdf67531300 , param 
= 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe 
, next = 0x0}

p *dlg->cbs.first->next->next
Cannot access memory at address 0x0
p *dlg->cbs.first->next->next->next
Cannot access memory at address 0x20
and so on with at address 0x20
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 18:43, "Bogdan-Andrei Iancu" :

Super :)we got to something useful.

Now, again in GDB please do:

f 5
p *dlg->cbs.first
p *dlg->cbs.first->next
p *dlg->cbs.first->next->next

and keep adding "->next" until you get error from gdb.

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 06:07 PM, Денис Путято wrote:

Sorry, Bogdan, i missed that
I found such CRITICAL message
"CRITICAL:core:qm_free: freeing already freed pointer, first free: 
acc_logic.c: dlg_free_acc_mask(211) - aborting"
And after that and till crash only "WARNING:core:utimer_ticker:" 
reports in syslog.

(gdb)
f 2
#2  0x00515592 in qm_free (qm=, 
p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 "acc_logic.c",
func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> 
"dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483

483 abort();
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))
$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 
140597661320880}, file = 0x7fdf6753ad62 "acc_logic.c", func = 
0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line = 211,

  check = 17361641481138401520}
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 17:58, "Bogdan-Andrei Iancu"  
:

The RADIUS part is not relevant.

Still you didn;t answer to my question on the CRITICAL error - 
according to the backtrace, you should have a CRITICAL message in 
the opensips log, just before the crash.


In GDB, do:
f 2
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))

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 05:55 PM, Denis wrote:

During crash there was another problem with LAN network.
Because of this problem Opensips could not connect to radius server.
rc_ip_hostname: couldn't look up host by addr: xx
rc_send_server: no reply from RADIUS server unknown:1812
No more critical messages.
Bogdan, i am sorry, but
"in frame 2". What does it mean?
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 16:35, "Bogdan-Andrei Iancu"  
:

Any CRITICAL message into the log before the crash ?

also, in gdb in frame 2, please print:
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))


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 03:19 PM, Denis wrote:

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"  
:

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 

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Hello, Bogdan! f 5#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at dlg_hash.c:183183                     destroy_dlg_callbacks_list(dlg->cbs.first); p *dlg->cbs.first$1 = {types = 96, callback = 0x7fdf67531300 , param = 0x0, callback_param_free = 0x7fdf675318fe , next = 0x7fdf84191080} p *dlg->cbs.first->next$2 = {types = 96, callback = 0x7fdf67531300 , param = 0x7fdf83c9f340, callback_param_free = 0x7fdf675318fe , next = 0x0} p *dlg->cbs.first->next->nextCannot access memory at address 0x0 p *dlg->cbs.first->next->next->nextCannot access memory at address 0x20 and so on with at address 0x20 -- С уважением, Денис.Best regards, Denis   04.04.2017, 18:43, "Bogdan-Andrei Iancu" :Super :)we got to something useful.Now, again in GDB please do:f 5p *dlg->cbs.firstp *dlg->cbs.first->nextp *dlg->cbs.first->next->nextand keep adding "->next" until you get error from gdb.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 06:07 PM, Денис Путято wrote:Sorry, Bogdan, i missed that I found such CRITICAL message"CRITICAL:core:qm_free: freeing already freed pointer, first free: acc_logic.c: dlg_free_acc_mask(211) - aborting" And after that and till crash only "WARNING:core:utimer_ticker:" reports in syslog. (gdb)f 2#2  0x00515592 in qm_free (qm=, p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 "acc_logic.c",    func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483483                     abort();  p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 140597661320880}, file = 0x7fdf6753ad62 "acc_logic.c", func = 0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line = 211,  check = 17361641481138401520} -- С уважением, Денис.Best regards, Denis   04.04.2017, 17:58, "Bogdan-Andrei Iancu" :The RADIUS part is not relevant.Still you didn;t answer to my question on the CRITICAL error - according to the backtrace, you should have a CRITICAL message in the opensips log, just before the crash.In GDB, do:    f 2    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))  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 05:55 PM, Denis wrote:During crash there was another problem with LAN network.Because of this problem Opensips could not connect to radius server.rc_ip_hostname: couldn't look up host by addr: xxrc_send_server: no reply from RADIUS server unknown:1812 No more critical messages. Bogdan, i am sorry, but"in frame 2". What does it mean?  -- С уважением, Денис.Best regards, Denis   04.04.2017, 16:35, "Bogdan-Andrei Iancu" :Any CRITICAL message into the log before the crash ?also, in gdb in frame 2, please print:    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))   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 03:19 PM, Denis wrote: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" :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_endThanks,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 Opensips2. 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  already scheduled for 71500 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 

Re: [OpenSIPS-Users] Opensips crash

[Денис Путято via Users]

Sorry, Bogdan, i missed that I found such CRITICAL message"CRITICAL:core:qm_free: freeing already freed pointer, first free: acc_logic.c: dlg_free_acc_mask(211) - aborting" And after that and till crash only "WARNING:core:utimer_ticker:" reports in syslog. (gdb)f 2#2  0x00515592 in qm_free (qm=, p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 "acc_logic.c",    func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line=line@entry=211) at mem/q_malloc.c:483483                     abort();  p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))$1 = {size = 8, u = {nxt_free = 0x7fdf71a8c6b0, is_free = 140597661320880}, file = 0x7fdf6753ad62 "acc_logic.c", func = 0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", line = 211,  check = 17361641481138401520} -- С уважением, Денис.Best regards, Denis   04.04.2017, 17:58, "Bogdan-Andrei Iancu" :The RADIUS part is not relevant.Still you didn;t answer to my question on the CRITICAL error - according to the backtrace, you should have a CRITICAL message in the opensips log, just before the crash.In GDB, do:    f 2    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))  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 05:55 PM, Denis wrote:During crash there was another problem with LAN network.Because of this problem Opensips could not connect to radius server.rc_ip_hostname: couldn't look up host by addr: xxrc_send_server: no reply from RADIUS server unknown:1812 No more critical messages. Bogdan, i am sorry, but"in frame 2". What does it mean?  -- С уважением, Денис.Best regards, Denis   04.04.2017, 16:35, "Bogdan-Andrei Iancu" :Any CRITICAL message into the log before the crash ?also, in gdb in frame 2, please print:    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))   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 03:19 PM, Denis wrote: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" :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_endThanks,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 Opensips2. 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  already scheduled for 71500 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  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_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.git revision: 7922417main.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" :Hello Denis,Thank you for the report. Do you see any CRITICAL log just before the crash, something like:    "bad pointer 0 (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 

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

The RADIUS part is not relevant.

Still you didn;t answer to my question on the CRITICAL error - according 
to the backtrace, you should have a CRITICAL message in the opensips 
log, just before the crash.


In GDB, do:
f 2
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))

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 05:55 PM, Denis wrote:

During crash there was another problem with LAN network.
Because of this problem Opensips could not connect to radius server.
rc_ip_hostname: couldn't look up host by addr: xx
rc_send_server: no reply from RADIUS server unknown:1812
No more critical messages.
Bogdan, i am sorry, but
"in frame 2". What does it mean?
--
С уважением, Денис.
Best regards, Denis
04.04.2017, 16:35, "Bogdan-Andrei Iancu" :

Any CRITICAL message into the log before the crash ?

also, in gdb in frame 2, please print:
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))


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 03:19 PM, Denis wrote:

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"  
:

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  already 
scheduled for 71500 ms
WARNING:core:timer_ticker: timer task  already 
scheduled for 72400 ms
WARNING:core:timer_ticker: timer task  already scheduled 
for 72400 ms
WARNING:core:timer_ticker: timer task  already 
scheduled for 72400 ms
WARNING:core:timer_ticker: timer task  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"  
:

Hello Denis,

Thank you for the report. Do you see any CRITICAL log just before 
the crash, something like:

"bad pointer 0 (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
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

During crash there was another problem with LAN network.Because of this problem Opensips could not connect to radius server.rc_ip_hostname: couldn't look up host by addr: xxrc_send_server: no reply from RADIUS server unknown:1812 No more critical messages. Bogdan, i am sorry, but"in frame 2". What does it mean?  -- С уважением, Денис.Best regards, Denis   04.04.2017, 16:35, "Bogdan-Andrei Iancu" :Any CRITICAL message into the log before the crash ?also, in gdb in frame 2, please print:    p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))   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 03:19 PM, Denis wrote: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" :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_endThanks,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 Opensips2. 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  already scheduled for 71500 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  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_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.git revision: 7922417main.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" :Hello Denis,Thank you for the report. Do you see any CRITICAL log just before the crash, something like:    "bad pointer 0 (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
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Any CRITICAL message into the log before the crash ?

also, in gdb in frame 2, please print:
p *((struct qm_frag*) ((char*)p-sizeof(struct qm_frag)))


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 03:19 PM, Denis wrote:

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" :

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  already 
scheduled for 71500 ms
WARNING:core:timer_ticker: timer task  already scheduled 
for 72400 ms
WARNING:core:timer_ticker: timer task  already scheduled 
for 72400 ms
WARNING:core:timer_ticker: timer task  already scheduled 
for 72400 ms
WARNING:core:timer_ticker: timer task  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"  
:

Hello Denis,

Thank you for the report. Do you see any CRITICAL log just before 
the crash, something like:

"bad pointer 0 (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
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

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" :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_endThanks,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 Opensips2. 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  already scheduled for 71500 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  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_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.git revision: 7922417main.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" :Hello Denis,Thank you for the report. Do you see any CRITICAL log just before the crash, something like:    "bad pointer 0 (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
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

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  already scheduled 
for 71500 ms
WARNING:core:timer_ticker: timer task  already scheduled 
for 72400 ms
WARNING:core:timer_ticker: timer task  already scheduled for 
72400 ms
WARNING:core:timer_ticker: timer task  already scheduled 
for 72400 ms
WARNING:core:timer_ticker: timer task  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" :

Hello Denis,

Thank you for the report. Do you see any CRITICAL log just before the 
crash, something like:

"bad pointer 0 (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
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

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 Opensips2. 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  already scheduled for 71500 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  already scheduled for 72400 msWARNING:core:timer_ticker: timer task  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_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.git revision: 7922417main.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" :Hello Denis,Thank you for the report. Do you see any CRITICAL log just before the crash, something like:    "bad pointer 0 (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
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Hello Denis,

Thank you for the report. Do you see any CRITICAL log just before the 
crash, something like:

"bad pointer 0 (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
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Opensips crash

[Denis via Users]

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   #0  0x7fe069215428 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 14909
selftid = 14909
#1  0x7fe06921702a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 
0x20}, sa_mask = {__val = {137438953472, 140597487971682, 
140597487972240, 0, 140597559685120,
  140597568830240, 8422349725574235136, 140597568830016, 
140597559685120, 1, 140601814054893, 0, 0, 140601816922912, 0, 1}}, sa_flags = 
1805468968, sa_restorer = 0x7fdf6b99f000}
sigs = {__val = {32, 0 }}
#2  0x00515592 in qm_free (qm=, 
p=p@entry=0x7fdf83c9f340, file=file@entry=0x7fdf6753ad62 "acc_logic.c",
func=func@entry=0x7fdf6753af90 <__FUNCTION__.12529> "dlg_free_acc_mask", 
line=line@entry=211) at mem/q_malloc.c:483
f = 
prev = 
next = 
size = 
__FUNCTION__ = "qm_free"
#3  0x7fdf67531aa1 in dlg_free_acc_mask (param=0x7fdf83c9f340) at 
acc_logic.c:211
__FUNCTION__ = "dlg_free_acc_mask"
#4  0x7fdf6842bbb5 in destroy_dlg_callbacks_list (cb=0x0) at dlg_cb.c:76
cb_t = 0x7fdf84191080
__FUNCTION__ = "destroy_dlg_callbacks_list"
#5  0x7fdf6844c4f2 in free_dlg_dlg (dlg=0x7fdf6c4ac158) at dlg_hash.c:183
dv = 
i = 
#6  destroy_dlg (dlg=dlg@entry=0x7fdf6c4ac158) at dlg_hash.c:247
ret = 
__FUNCTION__ = "destroy_dlg"
#7  0x7fdf68456bc5 in unref_dlg (dlg=0x7fdf6c4ac158, cnt=) 
at dlg_hash.c:777
d_entry = 0x7fdf6c04ea08
__FUNCTION__ = "unref_dlg"
#8  0x7fdf6a04a501 in run_trans_callbacks (type=type@entry=4096, 
trans=trans@entry=0x7fdf83d93d68, req=req@entry=0x0, rpl=rpl@entry=0x0, 
code=code@entry=0) at t_hooks.c:209
params = {req = 0x0, rpl = 0x0, code = 0, param = 0x7fdf83b74200, 
extra1 = 0x0, extra2 = 0x0}
cbp = 0x7fdf83b741f0
backup = 0x8901f8 
trans_backup = 0x
__FUNCTION__ = "run_trans_callbacks"
#9  0x7fdf6a01b219 in free_cell (dead_cell=dead_cell@entry=0x7fdf83d93d68) 
at h_table.c:125
b = 
i = 
rpl = 
tt = 
foo = 
p = 
__FUNCTION__ = "free_cell"
#10 0x7fdf6a05b212 in delete_cell (p_cell=p_cell@entry=0x7fdf83d93d68, 
unlock=unlock@entry=1) at timer.c:239
__FUNCTION__ = "delete_cell"
#11 0x7fdf6a05bf9f in wait_handler (wait_tl=0x7fdf83d93de8) at timer.c:445
p_cell = 0x7fdf83d93d68
#12 timer_routine (ticks=, set=) at timer.c:1069
tl = 0x7fdf83d93de8
tmp_tl = 0x7fdf846bcce8
id = 2
__FUNCTION__ = "timer_routine"
#13 0x004a2b6c in handle_timer_job () at timer.c:699
t = 0x7fdf6bc58ff0
---Type  to continue, or q  to quit---
__FUNCTION__ = "handle_timer_job"
#14 0x005a5452 in handle_io (idx=, event_type=, fm=) at net/net_udp.c:264
No locals.
#15 io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225
ret = 
e = 
n = 2
r = 1
#16 udp_rcv_loop (si=si@entry=0x7fe029214a50) at net/net_udp.c:308
__FUNCTION__ = "udp_rcv_loop"
#17 0x005a69fb in udp_start_processes (chd_rank=chd_rank@entry=0x8902ac 
, startup_done=startup_done@entry=0x0) at net/net_udp.c:372
si = 0x7fe029214a50
load_p = 0x7fdf6e048330
pid = 
i = 3
__FUNCTION__ = "udp_start_processes"
#18 0x0041ad71 in main_loop () at main.c:675
startup_done = 0x0
chd_rank = 4
#19 main (argc=, argv=) at main.c:1265
cfg_stream = 
c = 
r = 
tmp = 0x7fff8373eef8 ""
tmp_len = 
port = 
proto = 
protos_no = 
options = 0x5ed520 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:"
ret = -1
seed = 42605482
__FUNCTION__ = "main"
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Ok, thank you. I will try. -- С уважением, Денис.Best regards, Denis 22.03.2017, 16:21, "Răzvan Crainea" :Hi, Denis!Please recompile opensips with QM_MALLOC and DBG_MALLOC flags. This will provide more information about your crash.You can use this[1] tutorial to enable QM_MALLOC.[1] http://www.opensips.org/Documentation/TroubleShooting-OutOfMemBest regards,Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.comOn 03/22/2017 02:30 PM, Denis via Users wrote:Hello! Server:: OpenSIPS (2.2.2 (x86_64/linux)) Information from the core you can find here https://yadi.sk/i/Kr0nzENF3GF9VM Thank you for any help.  -- С уважением, Денис.Best regards, Denis___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
,___Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Răzvan Crainea]

Hi, Denis!

Please recompile opensips with QM_MALLOC and DBG_MALLOC flags. This will 
provide more information about your crash.

You can use this[1] tutorial to enable QM_MALLOC.

[1] http://www.opensips.org/Documentation/TroubleShooting-OutOfMem

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 03/22/2017 02:30 PM, Denis via Users wrote:

Hello!
Server:: OpenSIPS (2.2.2 (x86_64/linux))
Information from the core you can find here 
https://yadi.sk/i/Kr0nzENF3GF9VM

Thank you for any help.
--
С уважением, Денис.
Best regards, Denis


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Opensips crash

[Denis via Users]

Hello! Server:: OpenSIPS (2.2.2 (x86_64/linux)) Information from the core you can find here https://yadi.sk/i/Kr0nzENF3GF9VM Thank you for any help.  -- С уважением, Денис.Best regards, Denis   ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Hi Denis,

Run "opensips -V" .

Best regards,

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

On 02/06/2017 07:16 AM, Denis wrote:

Hello, Bogdan!
Could you, please, tell me how can i checked, that the version of 
Opensips is latest?

Thank you.
--
С уважением, Денис.
Best regards, Denis
05.02.2017, 19:05, "Bogdan-Andrei Iancu" :

Hi Denis,

First, be sure you use the latest 2.2 from GIT.

Now, the crash indicates a memory corruption, so please activate the 
memory debugger:  Run 'make menuconfig' from the main source dir -> 
Configure Compile Options -> Configure Compile Flags -> check 
QM_MALLOC and DBG_MALLOC. Then hit 'q' to go back to the previous 
menu, and hit 'Save Changes'.


Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com 
On 02/02/2017 10:03 AM, Denis via Users wrote:

Hello!
Server:: OpenSIPS (2.2.2 (x86_64/linux))
Information from the core file: https://yadi.sk/i/IfhdM1Y83CQvPk
Thank you for any help.
--
С уважением, Денис.
Best regards, Denis
___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis via Users]

Hello, Bogdan! Could you, please, tell me how can i checked, that the version of Opensips is latest? Thank you. -- С уважением, Денис.Best regards, Denis   05.02.2017, 19:05, "Bogdan-Andrei Iancu" :Hi Denis,First, be sure you use the latest 2.2 from GIT.Now, the crash indicates a memory corruption, so please activate the memory debugger:  Run 'make menuconfig' from the main source dir -> Configure Compile Options -> Configure Compile Flags -> check QM_MALLOC and DBG_MALLOC. Then hit 'q' to go back to the previous menu, and hit 'Save Changes'.Regards,Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.comOn 02/02/2017 10:03 AM, Denis via Users wrote:Hello! Server:: OpenSIPS (2.2.2 (x86_64/linux)) Information from the core file: https://yadi.sk/i/IfhdM1Y83CQvPk Thank you for any help. -- С уважением, Денис.Best regards, Denis___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Bogdan-Andrei Iancu]

Hi Denis,

First, be sure you use the latest 2.2 from GIT.

Now, the crash indicates a memory corruption, so please activate the 
memory debugger:  Run 'make menuconfig' from the main source dir -> 
Configure Compile Options -> Configure Compile Flags -> check QM_MALLOC 
and DBG_MALLOC. Then hit 'q' to go back to the previous menu, and hit 
'Save Changes'.


Regards,

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

On 02/02/2017 10:03 AM, Denis via Users wrote:

Hello!
Server:: OpenSIPS (2.2.2 (x86_64/linux))
Information from the core file: https://yadi.sk/i/IfhdM1Y83CQvPk
Thank you for any help.
--
С уважением, Денис.
Best regards, Denis


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis]

I understand, thank you. -- С уважением, Денис.Best regards, Denis 23.12.2016, 13:13, "Răzvan Crainea" :Hi, Denis!It's not OpenSIPS making the core, it's the Operating System. And the answer is "yes", if OpenSIPS crashes again, the "old core" will be replaced by a new one. One idea is to configure the Operating System to write the corefile using the pid of the process in the pattern. To do that, run:# echo core.%p > /proc/sys/kernel/core_patternBest regards,Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.comOn 12/23/2016 11:35 AM, Denis wrote:One question. If in the destination directory of the core file will be located another "core" file, what will be? Would "old core" file be replaced by a new one, or Opensips makes another core file with a fresh data? Thank you. -- С уважением, Денис.Best regards, Denis 23.12.2016, 12:23, "Răzvan Crainea" :Please update to the latest 2.2.2. If you still have problems, try to make sure opensips can generate a corefile[1].[1] http://www.opensips.org/Documentation/TroubleShooting-CrashBest regards,Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.comOn 12/23/2016 11:16 AM, Denis wrote:Hello! Server:: OpenSIPS (2.2.1 (x86_64/linux)) Today i had a crash of Opensips.Everything that i could collect is here https://yadi.sk/i/dyNnXpBr34YJQ3 Unfortunately, i could not find any fresh core file, despite of the fact that Opensips starts with -w /opensipscore option.In opensipscore i found only core file at 29 Nov. Thank you for any help.  -- С уважением, Денис.Best regards, Denis___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
,___Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
,___Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Miha]

Hey Denis

https://www.opensips.org/Documentation/TroubleShooting-Crash

it will create core.


miha

On 23/12/2016 10:35, Denis wrote:
One question. If in the destination directory of the core file will be 
located another "core" file, what will be? Would "old core" file be 
replaced by a new one, or Opensips makes another core file with a 
fresh data?

Thank you.
--
С уважением, Денис.
Best regards, Denis
23.12.2016, 12:23, "Răzvan Crainea" :
Please update to the latest 2.2.2. If you still have problems, try to 
make sure opensips can generate a corefile[1].


[1] http://www.opensips.org/Documentation/TroubleShooting-Crash

Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com 
On 12/23/2016 11:16 AM, Denis wrote:

Hello!

Server:: OpenSIPS (2.2.1 (x86_64/linux))
Today i had a crash of Opensips.
Everything that i could collect is here 
https://yadi.sk/i/dyNnXpBr34YJQ3
Unfortunately, i could not find any fresh core file, despite of the 
fact that Opensips starts with -w /opensipscore option.

In opensipscore i found only core file at 29 Nov.
Thank you for any help.
--
С уважением, Денис.
Best regards, Denis

___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

,

___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Răzvan Crainea]

Hi, Denis!

It's not OpenSIPS making the core, it's the Operating System. And the 
answer is "yes", if OpenSIPS crashes again, the "old core" will be 
replaced by a new one. One idea is to configure the Operating System to 
write the corefile using the pid of the process in the pattern. To do 
that, run:

# echo core.%p > /proc/sys/kernel/core_pattern

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 12/23/2016 11:35 AM, Denis wrote:
One question. If in the destination directory of the core file will be 
located another "core" file, what will be? Would "old core" file be 
replaced by a new one, or Opensips makes another core file with a 
fresh data?

Thank you.
--
С уважением, Денис.
Best regards, Denis
23.12.2016, 12:23, "Răzvan Crainea" :
Please update to the latest 2.2.2. If you still have problems, try to 
make sure opensips can generate a corefile[1].


[1] http://www.opensips.org/Documentation/TroubleShooting-Crash

Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com 
On 12/23/2016 11:16 AM, Denis wrote:

Hello!

Server:: OpenSIPS (2.2.1 (x86_64/linux))
Today i had a crash of Opensips.
Everything that i could collect is here 
https://yadi.sk/i/dyNnXpBr34YJQ3
Unfortunately, i could not find any fresh core file, despite of the 
fact that Opensips starts with -w /opensipscore option.

In opensipscore i found only core file at 29 Nov.
Thank you for any help.
--
С уважением, Денис.
Best regards, Denis

___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

,

___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis]

One question. If in the destination directory of the core file will be located another "core" file, what will be? Would "old core" file be replaced by a new one, or Opensips makes another core file with a fresh data? Thank you. -- С уважением, Денис.Best regards, Denis 23.12.2016, 12:23, "Răzvan Crainea" :Please update to the latest 2.2.2. If you still have problems, try to make sure opensips can generate a corefile[1].[1] http://www.opensips.org/Documentation/TroubleShooting-CrashBest regards,Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.comOn 12/23/2016 11:16 AM, Denis wrote:Hello! Server:: OpenSIPS (2.2.1 (x86_64/linux)) Today i had a crash of Opensips.Everything that i could collect is here https://yadi.sk/i/dyNnXpBr34YJQ3 Unfortunately, i could not find any fresh core file, despite of the fact that Opensips starts with -w /opensipscore option.In opensipscore i found only core file at 29 Nov. Thank you for any help.  -- С уважением, Денис.Best regards, Denis___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
,___Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Răzvan Crainea]

Please update to the latest 2.2.2. If you still have problems, try to 
make sure opensips can generate a corefile[1].


[1] http://www.opensips.org/Documentation/TroubleShooting-Crash

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 12/23/2016 11:16 AM, Denis wrote:

Hello!

Server:: OpenSIPS (2.2.1 (x86_64/linux))
Today i had a crash of Opensips.
Everything that i could collect is here https://yadi.sk/i/dyNnXpBr34YJQ3
Unfortunately, i could not find any fresh core file, despite of the 
fact that Opensips starts with -w /opensipscore option.

In opensipscore i found only core file at 29 Nov.
Thank you for any help.
--
С уважением, Денис.
Best regards, Denis



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash

[Denis]

Hello! Server:: OpenSIPS (2.2.1 (x86_64/linux)) Today i had a crash of Opensips.Everything that i could collect is here https://yadi.sk/i/dyNnXpBr34YJQ3 Unfortunately, i could not find any fresh core file, despite of the fact that Opensips starts with -w /opensipscore option.In opensipscore i found only core file at 29 Nov. Thank you for any help.  -- С уважением, Денис.Best regards, Denis   

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

9edb9dc5 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5aa42eb28d in clone () from /lib64/libc.so.6

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, October 05, 2016 3:58 PM
To: Ramachandran, Agalya (Contractor) <agalya_ramachand...@comcast.com>; 
OpenSIPS users mailling list <users@lists.opensips.org>
Subject: Re: opensips crash when doing load test

That's a good news :)

Try to add one patch at a time (incrementally) and let's see when it starts to 
crash again.

Thanks and regards,



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 05.10.2016 22:55, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

With 2.2 version, am not seeing any crash. All looks good.

Regards,
Agalya

From: users-boun...@lists.opensips.org<mailto:users-boun...@lists.opensips.org> 
[mailto:users-boun...@lists.opensips.org] On Behalf Of Ramachandran, Agalya 
(Contractor)
Sent: Wednesday, October 05, 2016 10:50 AM
To: Bogdan-Andrei Iancu <bog...@opensips.org><mailto:bog...@opensips.org>; 
OpenSIPS users mailling list 
<users@lists.opensips.org><mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] opensips crash when doing load test

Sure. I will test and share the results by end of day or tomorrow.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, October 05, 2016 10:47 AM
To: Ramachandran, Agalya (Contractor) 
<agalya_ramachand...@comcast.com<mailto:agalya_ramachand...@comcast.com>>; 
OpenSIPS users mailling list 
<users@lists.opensips.org<mailto:users@lists.opensips.org>>
Subject: Re: opensips crash when doing load test

Yes, that is ok (without the REST) - just to be sure which patch introduces the 
bug.

Regards,



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 05.10.2016 17:45, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

I have observed one more thing. In the same source code, when opensips acts as 
pure proxy no HTTP call is made opensips is not crashing.
I suspect the crashes may be due to the new async fix provided.

I can do load test in 2.2, but it  will be just pure-proxy load test and not 
with the REST queries made.
If that is OK, I can test and share the results.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, October 05, 2016 9:46 AM
To: Ramachandran, Agalya (Contractor) 
<agalya_ramachand...@comcast.com><mailto:agalya_ramachand...@comcast.com>; 
OpenSIPS users mailling list 
<users@lists.opensips.org><mailto:users@lists.opensips.org>
Subject: Re: opensips crash when doing load test

Hi Agalya,

That is really weird, as that field (my_T) is initialized (with the address of 
the transaction) when the transaction is created (for all the possible 
branches) and never reset or set again.

To avoid any regression due the patches you applied, could you please run your 
load test with the stock 2.2 code from git ? And see if the crash occurs again.

Regards,



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 04.10.2016 19:51, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

Please find the values. Any common folder you have access for the outside world 
to put files?
If yes, share me the details. I can upload the core file there.

(gdb) print r_buf
$1 = (struct retr_buf *) 0x7fded2484098
(gdb) print *r_buf
$2 = {activ_type = 0, buffer = {
s = 0x7fded0ca79f0 "INVITE 
sip:++1200104@10.0.0.1:5060<mailto:sip:++1200104@10.0.0.1:5060> 
SIP/2.0\r\nRecord-Route: <sip:96.119.240.35;lr>\r\nTo: sut 
<sip:+12452123456@10.0.0.1:5060;user=phone><mailto:sip:+12452123456@10.0.0.1:5060;user=phone>\r\nFrom:
 sipp 
<sip:sipp@10.0.0.2:5060;user=phone<mailto:sip:sipp@10.0.0.2:5060;user=phone>"...,
 len = 968}, dst = {proto = 1,
proto_reserved1 = 0, to = {s = {sa_family = 2, sa_data = 
"\023\304`w\347\375\000\000\000\000\000\000\000"}, sin = {
sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 4259805024}, 
sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {
sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4259805024, 
sin6_addr = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 
0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}},
sin6_scope_id = 0}}, send_sock = 0x7fded841dcb0}, retr_timer = {next_tl 
= 0x7fded1af3518, prev_tl = 0x7fded15c8ae0,
ld_tl = 0x0, time_out = 16950, timer_list = 0x7fded0acbc48, deleted = 
1, set = 0}, fr_timer = {next_tl = 0x0, prev_tl = 0x0,
ld_tl = 0x0, time_out = 165, timer_list = 0x7fded8005b00 , 
deleted = 0, set = 0}, retr_list = RT_T2, my_T = 0x0,
  branch = 0}

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Tuesday, October 04, 2016 11:52 AM
To: Ramach

Re: [OpenSIPS-Users] opensips crash when doing load test

[Bogdan-Andrei Iancu]

That's a good news :)

Try to add one patch at a time (incrementally) and let's see when it 
starts to crash again.


Thanks and regards,

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

On 05.10.2016 22:55, Ramachandran, Agalya (Contractor) wrote:


Hi Bogdan,

With 2.2 version, am not seeing any crash. All looks good.

Regards,
Agalya

*From:*users-boun...@lists.opensips.org 
[mailto:users-boun...@lists.opensips.org] *On Behalf Of *Ramachandran, 
Agalya (Contractor)

*Sent:* Wednesday, October 05, 2016 10:50 AM
*To:* Bogdan-Andrei Iancu <bog...@opensips.org>; OpenSIPS users 
mailling list <users@lists.opensips.org>

*Subject:* Re: [OpenSIPS-Users] opensips crash when doing load test

Sure. I will test and share the results by end of day or tomorrow.

Regards,

Agalya

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Wednesday, October 05, 2016 10:47 AM
*To:* Ramachandran, Agalya (Contractor) 
<agalya_ramachand...@comcast.com 
<mailto:agalya_ramachand...@comcast.com>>; OpenSIPS users mailling 
list <users@lists.opensips.org <mailto:users@lists.opensips.org>>

*Subject:* Re: opensips crash when doing load test

Yes, that is ok (without the REST) - just to be sure which patch 
introduces the bug.


Regards,

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

On 05.10.2016 17:45, Ramachandran, Agalya (Contractor) wrote:

Hi Bogdan,

I have observed one more thing. In the same source code, when
opensips acts as pure proxy no HTTP call is made opensips is not
crashing.

I suspect the crashes may be due to the new async fix provided.

I can do load test in 2.2, but it  will be just pure-proxy load
test and not with the REST queries made.

If that is OK, I can test and share the results.

Regards,

Agalya

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Wednesday, October 05, 2016 9:46 AM
*To:* Ramachandran, Agalya (Contractor)
<agalya_ramachand...@comcast.com>
<mailto:agalya_ramachand...@comcast.com>; OpenSIPS users mailling
list <users@lists.opensips.org> <mailto:users@lists.opensips.org>
*Subject:* Re: opensips crash when doing load test

Hi Agalya,

That is really weird, as that field (my_T) is initialized (with
the address of the transaction) when the transaction is created
(for all the possible branches) and never reset or set again.

To avoid any regression due the patches you applied, could you
please run your load test with the stock 2.2 code from git ? And
see if the crash occurs again.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com

On 04.10.2016 19:51, Ramachandran, Agalya (Contractor) wrote:

Hi Bogdan,

Please find the values. Any common folder you have access for
the outside world to put files?

If yes, share me the details. I can upload the core file there.

(gdb) print r_buf

$1 = (struct retr_buf *) 0x7fded2484098

(gdb) print *r_buf

$2 = {activ_type = 0, buffer = {

s = 0x7fded0ca79f0 "INVITE sip:++1200104@10.0.0.1:5060
<mailto:sip:++1200104@10.0.0.1:5060>
SIP/2.0\r\nRecord-Route: <sip:96.119.240.35;lr>\r\nTo: sut
<sip:+12452123456@10.0.0.1:5060;user=phone>
<mailto:sip:+12452123456@10.0.0.1:5060;user=phone>\r\nFrom:
sipp <sip:sipp@10.0.0.2:5060;user=phone
<mailto:sip:sipp@10.0.0.2:5060;user=phone>"..., len = 968},
dst = {proto = 1,

proto_reserved1 = 0, to = {s = {sa_family = 2, sa_data =
"\023\304`w\347\375\000\000\000\000\000\000\000"}, sin = {

sin_family = 2, sin_port = 50195, sin_addr = {s_addr =
4259805024}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {

sin6_family = 2, sin6_port = 50195, sin6_flowinfo =
4259805024, sin6_addr = {__in6_u = {

__u6_addr8 = '\000' , __u6_addr16 = {0, 0,
0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}},

sin6_scope_id = 0}}, send_sock = 0x7fded841dcb0}, retr_timer =
{next_tl = 0x7fded1af3518, prev_tl = 0x7fded15c8ae0,

ld_tl = 0x0, time_out = 16950, timer_list =
0x7fded0acbc48, deleted = 1, set = 0}, fr_timer = {next_tl =
0x0, prev_tl = 0x0,

ld_tl = 0x0, time_out = 165, timer_list = 0x7fded8005b00
, deleted = 0, set = 0}, retr_list = RT_T2,
my_T = 0x0,

  branch = 0}

Regards,
Agalya

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Tuesday, October 04, 2016 11:52 AM
*To:* Ramachandran, Agalya (Contractor)
<agalya_ramachand...@comcast.com>
<mailto:agalya_ramachand...@comcast.com>; OpenSIPS user

Re: [OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

Hi Bogdan,

With 2.2 version, am not seeing any crash. All looks good.

Regards,
Agalya

From: users-boun...@lists.opensips.org 
[mailto:users-boun...@lists.opensips.org] On Behalf Of Ramachandran, Agalya 
(Contractor)
Sent: Wednesday, October 05, 2016 10:50 AM
To: Bogdan-Andrei Iancu <bog...@opensips.org>; OpenSIPS users mailling list 
<users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] opensips crash when doing load test

Sure. I will test and share the results by end of day or tomorrow.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, October 05, 2016 10:47 AM
To: Ramachandran, Agalya (Contractor) 
<agalya_ramachand...@comcast.com<mailto:agalya_ramachand...@comcast.com>>; 
OpenSIPS users mailling list 
<users@lists.opensips.org<mailto:users@lists.opensips.org>>
Subject: Re: opensips crash when doing load test

Yes, that is ok (without the REST) - just to be sure which patch introduces the 
bug.

Regards,


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 05.10.2016 17:45, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

I have observed one more thing. In the same source code, when opensips acts as 
pure proxy no HTTP call is made opensips is not crashing.
I suspect the crashes may be due to the new async fix provided.

I can do load test in 2.2, but it  will be just pure-proxy load test and not 
with the REST queries made.
If that is OK, I can test and share the results.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, October 05, 2016 9:46 AM
To: Ramachandran, Agalya (Contractor) 
<agalya_ramachand...@comcast.com><mailto:agalya_ramachand...@comcast.com>; 
OpenSIPS users mailling list 
<users@lists.opensips.org><mailto:users@lists.opensips.org>
Subject: Re: opensips crash when doing load test

Hi Agalya,

That is really weird, as that field (my_T) is initialized (with the address of 
the transaction) when the transaction is created (for all the possible 
branches) and never reset or set again.

To avoid any regression due the patches you applied, could you please run your 
load test with the stock 2.2 code from git ? And see if the crash occurs again.

Regards,


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 04.10.2016 19:51, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

Please find the values. Any common folder you have access for the outside world 
to put files?
If yes, share me the details. I can upload the core file there.

(gdb) print r_buf
$1 = (struct retr_buf *) 0x7fded2484098
(gdb) print *r_buf
$2 = {activ_type = 0, buffer = {
s = 0x7fded0ca79f0 "INVITE 
sip:++1200104@10.0.0.1:5060<mailto:sip:++1200104@10.0.0.1:5060> 
SIP/2.0\r\nRecord-Route: <sip:96.119.240.35;lr>\r\nTo: sut 
<sip:+12452123456@10.0.0.1:5060;user=phone><mailto:sip:+12452123456@10.0.0.1:5060;user=phone>\r\nFrom:
 sipp 
<sip:sipp@10.0.0.2:5060;user=phone<mailto:sip:sipp@10.0.0.2:5060;user=phone>"...,
 len = 968}, dst = {proto = 1,
proto_reserved1 = 0, to = {s = {sa_family = 2, sa_data = 
"\023\304`w\347\375\000\000\000\000\000\000\000"}, sin = {
sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 4259805024}, 
sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {
sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4259805024, 
sin6_addr = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 
0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}},
sin6_scope_id = 0}}, send_sock = 0x7fded841dcb0}, retr_timer = {next_tl 
= 0x7fded1af3518, prev_tl = 0x7fded15c8ae0,
ld_tl = 0x0, time_out = 16950, timer_list = 0x7fded0acbc48, deleted = 
1, set = 0}, fr_timer = {next_tl = 0x0, prev_tl = 0x0,
ld_tl = 0x0, time_out = 165, timer_list = 0x7fded8005b00 , 
deleted = 0, set = 0}, retr_list = RT_T2, my_T = 0x0,
  branch = 0}

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Tuesday, October 04, 2016 11:52 AM
To: Ramachandran, Agalya (Contractor) 
<agalya_ramachand...@comcast.com><mailto:agalya_ramachand...@comcast.com>; 
OpenSIPS users mailling list 
<users@lists.opensips.org><mailto:users@lists.opensips.org>
Subject: Re: opensips crash when doing load test

Could you also print r_buf and *r_buf  ?


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

Sure. I will test and share the results by end of day or tomorrow.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, October 05, 2016 10:47 AM
To: Ramachandran, Agalya (Contractor) ; 
OpenSIPS users mailling list 
Subject: Re: opensips crash when doing load test

Yes, that is ok (without the REST) - just to be sure which patch introduces the 
bug.

Regards,



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 05.10.2016 17:45, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

I have observed one more thing. In the same source code, when opensips acts as 
pure proxy no HTTP call is made opensips is not crashing.
I suspect the crashes may be due to the new async fix provided.

I can do load test in 2.2, but it  will be just pure-proxy load test and not 
with the REST queries made.
If that is OK, I can test and share the results.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, October 05, 2016 9:46 AM
To: Ramachandran, Agalya (Contractor) 
; 
OpenSIPS users mailling list 

Subject: Re: opensips crash when doing load test

Hi Agalya,

That is really weird, as that field (my_T) is initialized (with the address of 
the transaction) when the transaction is created (for all the possible 
branches) and never reset or set again.

To avoid any regression due the patches you applied, could you please run your 
load test with the stock 2.2 code from git ? And see if the crash occurs again.

Regards,



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 04.10.2016 19:51, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

Please find the values. Any common folder you have access for the outside world 
to put files?
If yes, share me the details. I can upload the core file there.

(gdb) print r_buf
$1 = (struct retr_buf *) 0x7fded2484098
(gdb) print *r_buf
$2 = {activ_type = 0, buffer = {
s = 0x7fded0ca79f0 "INVITE 
sip:++1200104@10.0.0.1:5060 
SIP/2.0\r\nRecord-Route: \r\nTo: sut 
\r\nFrom:
 sipp 
"...,
 len = 968}, dst = {proto = 1,
proto_reserved1 = 0, to = {s = {sa_family = 2, sa_data = 
"\023\304`w\347\375\000\000\000\000\000\000\000"}, sin = {
sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 4259805024}, 
sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {
sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4259805024, 
sin6_addr = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 
0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}},
sin6_scope_id = 0}}, send_sock = 0x7fded841dcb0}, retr_timer = {next_tl 
= 0x7fded1af3518, prev_tl = 0x7fded15c8ae0,
ld_tl = 0x0, time_out = 16950, timer_list = 0x7fded0acbc48, deleted = 
1, set = 0}, fr_timer = {next_tl = 0x0, prev_tl = 0x0,
ld_tl = 0x0, time_out = 165, timer_list = 0x7fded8005b00 , 
deleted = 0, set = 0}, retr_list = RT_T2, my_T = 0x0,
  branch = 0}

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Tuesday, October 04, 2016 11:52 AM
To: Ramachandran, Agalya (Contractor) 
; 
OpenSIPS users mailling list 

Subject: Re: opensips crash when doing load test

Could you also print r_buf and *r_buf  ?


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash when doing load test

[Bogdan-Andrei Iancu]

Yes, that is ok (without the REST) - just to be sure which patch 
introduces the bug.


Regards,

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

On 05.10.2016 17:45, Ramachandran, Agalya (Contractor) wrote:


Hi Bogdan,

I have observed one more thing. In the same source code, when opensips 
acts as pure proxy no HTTP call is made opensips is not crashing.


I suspect the crashes may be due to the new async fix provided.

I can do load test in 2.2, but it  will be just pure-proxy load test 
and not with the REST queries made.


If that is OK, I can test and share the results.

Regards,

Agalya

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Wednesday, October 05, 2016 9:46 AM
*To:* Ramachandran, Agalya (Contractor) 
; OpenSIPS users mailling list 


*Subject:* Re: opensips crash when doing load test

Hi Agalya,

That is really weird, as that field (my_T) is initialized (with the 
address of the transaction) when the transaction is created (for all 
the possible branches) and never reset or set again.


To avoid any regression due the patches you applied, could you please 
run your load test with the stock 2.2 code from git ? And see if the 
crash occurs again.


Regards,

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

On 04.10.2016 19:51, Ramachandran, Agalya (Contractor) wrote:

Hi Bogdan,

Please find the values. Any common folder you have access for the
outside world to put files?

If yes, share me the details. I can upload the core file there.

(gdb) print r_buf

$1 = (struct retr_buf *) 0x7fded2484098

(gdb) print *r_buf

$2 = {activ_type = 0, buffer = {

s = 0x7fded0ca79f0 "INVITE sip:++1200104@10.0.0.1:5060
 SIP/2.0\r\nRecord-Route:
\r\nTo: sut

\r\nFrom: sipp
"..., len = 968}, dst =
{proto = 1,

proto_reserved1 = 0, to = {s = {sa_family = 2, sa_data =
"\023\304`w\347\375\000\000\000\000\000\000\000"}, sin = {

sin_family = 2, sin_port = 50195, sin_addr = {s_addr =
4259805024}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {

sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4259805024,
sin6_addr = {__in6_u = {

__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0,
0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}},

sin6_scope_id = 0}}, send_sock = 0x7fded841dcb0}, retr_timer =
{next_tl = 0x7fded1af3518, prev_tl = 0x7fded15c8ae0,

ld_tl = 0x0, time_out = 16950, timer_list =
0x7fded0acbc48, deleted = 1, set = 0}, fr_timer = {next_tl = 0x0,
prev_tl = 0x0,

ld_tl = 0x0, time_out = 165, timer_list = 0x7fded8005b00
, deleted = 0, set = 0}, retr_list = RT_T2, my_T =
0x0,

  branch = 0}

Regards,
Agalya

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Tuesday, October 04, 2016 11:52 AM
*To:* Ramachandran, Agalya (Contractor)

; OpenSIPS users mailling
list  
*Subject:* Re: opensips crash when doing load test

Could you also print r_buf and *r_buf  ?



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

Hi Bogdan,

I have observed one more thing. In the same source code, when opensips acts as 
pure proxy no HTTP call is made opensips is not crashing.
I suspect the crashes may be due to the new async fix provided.

I can do load test in 2.2, but it  will be just pure-proxy load test and not 
with the REST queries made.
If that is OK, I can test and share the results.

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, October 05, 2016 9:46 AM
To: Ramachandran, Agalya (Contractor) ; 
OpenSIPS users mailling list 
Subject: Re: opensips crash when doing load test

Hi Agalya,

That is really weird, as that field (my_T) is initialized (with the address of 
the transaction) when the transaction is created (for all the possible 
branches) and never reset or set again.

To avoid any regression due the patches you applied, could you please run your 
load test with the stock 2.2 code from git ? And see if the crash occurs again.

Regards,


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 04.10.2016 19:51, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

Please find the values. Any common folder you have access for the outside world 
to put files?
If yes, share me the details. I can upload the core file there.

(gdb) print r_buf
$1 = (struct retr_buf *) 0x7fded2484098
(gdb) print *r_buf
$2 = {activ_type = 0, buffer = {
s = 0x7fded0ca79f0 "INVITE 
sip:++1200104@10.0.0.1:5060 
SIP/2.0\r\nRecord-Route: \r\nTo: sut 
\r\nFrom:
 sipp 
"...,
 len = 968}, dst = {proto = 1,
proto_reserved1 = 0, to = {s = {sa_family = 2, sa_data = 
"\023\304`w\347\375\000\000\000\000\000\000\000"}, sin = {
sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 4259805024}, 
sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {
sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4259805024, 
sin6_addr = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 
0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}},
sin6_scope_id = 0}}, send_sock = 0x7fded841dcb0}, retr_timer = {next_tl 
= 0x7fded1af3518, prev_tl = 0x7fded15c8ae0,
ld_tl = 0x0, time_out = 16950, timer_list = 0x7fded0acbc48, deleted = 
1, set = 0}, fr_timer = {next_tl = 0x0, prev_tl = 0x0,
ld_tl = 0x0, time_out = 165, timer_list = 0x7fded8005b00 , 
deleted = 0, set = 0}, retr_list = RT_T2, my_T = 0x0,
  branch = 0}

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Tuesday, October 04, 2016 11:52 AM
To: Ramachandran, Agalya (Contractor) 
; 
OpenSIPS users mailling list 

Subject: Re: opensips crash when doing load test

Could you also print r_buf and *r_buf  ?

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash when doing load test

[Bogdan-Andrei Iancu]

Hi Agalya,

That is really weird, as that field (my_T) is initialized (with the 
address of the transaction) when the transaction is created (for all the 
possible branches) and never reset or set again.


To avoid any regression due the patches you applied, could youplease run 
your load test with the stock 2.2 code from git ? And see if the crash 
occurs again.


Regards,

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

On 04.10.2016 19:51, Ramachandran, Agalya (Contractor) wrote:


Hi Bogdan,

Please find the values. Any common folder you have access for the 
outside world to put files?


If yes, share me the details. I can upload the core file there.

(gdb) print r_buf

$1 = (struct retr_buf *) 0x7fded2484098

(gdb) print *r_buf

$2 = {activ_type = 0, buffer = {

s = 0x7fded0ca79f0 "INVITE sip:++1200104@10.0.0.1:5060 
SIP/2.0\r\nRecord-Route: \r\nTo: sut 
\r\nFrom: sipp 
; OpenSIPS users mailling list 


*Subject:* Re: opensips crash when doing load test

Could you also print r_buf and *r_buf  ?



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

Hi Bogdan,

Please find the values. Any common folder you have access for the outside world 
to put files?
If yes, share me the details. I can upload the core file there.

(gdb) print r_buf
$1 = (struct retr_buf *) 0x7fded2484098
(gdb) print *r_buf
$2 = {activ_type = 0, buffer = {
s = 0x7fded0ca79f0 "INVITE sip:++1200104@10.0.0.1:5060 
SIP/2.0\r\nRecord-Route: \r\nTo: sut 
\r\nFrom: sipp 
; 
OpenSIPS users mailling list 
Subject: Re: opensips crash when doing load test

Could you also print r_buf and *r_buf  ?

Regards,


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 04.10.2016 16:08, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

I have printed the "t" variable value. It says "$1 = (struct cell *) 0x0".
Is there any link available to upload/share the core files? Because size of the 
core file 45KB and couldn't attach in e-mail.

(gdb) frame 0
#0  final_response_handler (fr_tl=0x7fded2484110) at timer.c:383
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
(gdb) list +
378 current_processing_ctx = my_ctx;
379 /* set the T context too */
380 set_t( t );
381
382 /* out-of-lock do the cancel I/O */
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
384 set_cancel_extra_hdrs( CANCEL_REASON_SIP_480, 
sizeof(CANCEL_REASON_SIP_480)-1);
385 cancel_branch(t, r_buf->branch );
386 set_cancel_extra_hdrs( NULL, 0);
387 }
(gdb) p t
$1 = (struct cell *) 0x0

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Tuesday, October 04, 2016 6:44 AM
To: Ramachandran, Agalya (Contractor) 
; 
OpenSIPS users mailling list 

Subject: Re: opensips crash when doing load test

Hello Agalya,

In frame 0, could you print the "t" variable ? BTW, is there any way to get 
access to the core file ?

Best regards,



Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 30.09.2016 16:48, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

One more dump

#0  final_response_handler (fr_tl=0x7fded2484110) at timer.c:383
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
Missing separate debuginfos, use: debuginfo-install 
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64 glibc-2.17-106.el7_2.4.x86_64 
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.13.2-12.el7_2.x86_64 
libcom_err-1.42.9-7.el7.x86_64 libcurl-7.29.0-25.el7.centos.x86_64 
libidn-1.28-4.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 
libssh2-1.4.3-10.el7_2.1.x86_64 nspr-4.10.8-2.el7_1.x86_64 
nss-3.19.1-19.el7_2.x86_64 nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64 
nss-util-3.19.1-9.el7_2.x86_64 openldap-2.4.40-9.el7_2.x86_64 
openssl-libs-1.0.1e-51.el7_2.4.x86_64 pcre-8.32-15.el7.x86_64 
xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-15.el7.x86_64
(gdb) bt
#0  final_response_handler (fr_tl=0x7fded2484110) at timer.c:383
#1  timer_routine (ticks=, set=) at timer.c:1066
#2  0x0049d3cd in handle_timer_job () at timer.c:597
#3  0x0059223e in handle_io (fm=, fm=, 
fm=, idx=, event_type=2)
at net/net_udp.c:265
#4  io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225
#5  udp_rcv_loop (si=si@entry=0x7fded841dcb0) at net/net_udp.c:308
#6  0x00593e05 in udp_start_processes (chd_rank=chd_rank@entry=0x84c570 
, startup_done=startup_done@entry=0x0)
at net/net_udp.c:448
#7  0x00419b73 in main_loop () at main.c:736
#8  main (argc=, argv=) at main.c:1282

From: Ramachandran, Agalya (Contractor)
Sent: Friday, September 30, 2016 9:44 AM
To: 

Re: [OpenSIPS-Users] opensips crash when doing load test

[Bogdan-Andrei Iancu]

Could you also print r_buf and*r_buf  ?

Regards,

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

On 04.10.2016 16:08, Ramachandran, Agalya (Contractor) wrote:


Hi Bogdan,

I have printed the “t” variable value. It says “$1 = (struct cell *) 
0x0”.


Is there any link available to upload/share the core files? Because 
size of the core file 45KB and couldn’t attach in e-mail.


(gdb) frame 0

#0 final_response_handler (fr_tl=0x7fded2484110) at timer.c:383

383 if (is_invite(t) && should_cancel_branch(t, 
r_buf->branch) ) {


(gdb) list +

378 current_processing_ctx = my_ctx;

379 /* set the T context too */

380 set_t( t );

381

382 /* out-of-lock do the cancel I/O */

383 if (is_invite(t) && should_cancel_branch(t, 
r_buf->branch) ) {


384 set_cancel_extra_hdrs( CANCEL_REASON_SIP_480, 
sizeof(CANCEL_REASON_SIP_480)-1);


385 cancel_branch(t, r_buf->branch );

386 set_cancel_extra_hdrs( NULL, 0);

387 }

(gdb) p t

$1 = (struct cell *) 0x0

Regards,

Agalya

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Tuesday, October 04, 2016 6:44 AM
*To:* Ramachandran, Agalya (Contractor) 
; OpenSIPS users mailling list 


*Subject:* Re: opensips crash when doing load test

Hello Agalya,

In frame 0, could you print the "t" variable ? BTW, is there any way 
to get access to the core file ?


Best regards,

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

On 30.09.2016 16:48, Ramachandran, Agalya (Contractor) wrote:

Hi Bogdan,

One more dump

#0 final_response_handler (fr_tl=0x7fded2484110) at timer.c:383

383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {

Missing separate debuginfos, use: debuginfo-install
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64
glibc-2.17-106.el7_2.4.x86_64 keyutils-libs-1.5.8-3.el7.x86_64
krb5-libs-1.13.2-12.el7_2.x86_64 libcom_err-1.42.9-7.el7.x86_64
libcurl-7.29.0-25.el7.centos.x86_64 libidn-1.28-4.el7.x86_64
libselinux-2.2.2-6.el7.x86_64 libssh2-1.4.3-10.el7_2.1.x86_64
nspr-4.10.8-2.el7_1.x86_64 nss-3.19.1-19.el7_2.x86_64
nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64
nss-util-3.19.1-9.el7_2.x86_64 openldap-2.4.40-9.el7_2.x86_64
openssl-libs-1.0.1e-51.el7_2.4.x86_64 pcre-8.32-15.el7.x86_64
xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-15.el7.x86_64

(gdb) bt

#0 final_response_handler (fr_tl=0x7fded2484110) at timer.c:383

#1 timer_routine (ticks=, set=) at
timer.c:1066

#2 0x0049d3cd in handle_timer_job () at timer.c:597

#3 0x0059223e in handle_io (fm=,
fm=, fm=, idx=,
event_type=2)

at net/net_udp.c:265

#4 io_wait_loop_epoll (h=, t=,
repeat=) at net/../io_wait_loop.h:225

#5  udp_rcv_loop (si=si@entry=0x7fded841dcb0) at net/net_udp.c:308

#6 0x00593e05 in udp_start_processes
(chd_rank=chd_rank@entry=0x84c570 ,
startup_done=startup_done@entry=0x0)

at net/net_udp.c:448

#7 0x00419b73 in main_loop () at main.c:736

#8  main (argc=, argv=) at main.c:1282

*From:* Ramachandran, Agalya (Contractor)
*Sent:* Friday, September 30, 2016 9:44 AM
*To:* 'Bogdan-Andrei Iancu' 
; OpenSIPS users mailling list
 
*Subject:* opensips crash when doing load test

Hi Bogdan,

I have taken 2.1.4 code base, added the below fixes on top of it

1.Fix potential starvation for the timer tasks.
66c337cc89a2b5c3e1bbd78c289371efcda21886

2.rest_client: Improve polling logic during TCP connect -
c40f2b057209b8078520abc95e5d1bf5e5a28db6

3.rest_client: Add "connect_poll_interval" module parameter -
f5abfb3dee649a14ae39ad74d7f04454f815748f

4.rest_client: Fix bogus condition
-3ba7be6692c6987faecb9c4c904035d5e7c0f916

When I try to perform load test on that code base, randomly am
seeing OpenSIPS is crashing.

Here is the full trace of the core file. Let me know if you need
any additional information or logs.

Am seeing crash is occurring at start_timer_extra_processes().

[root@poc-siplb-cmc-e-004 corefiles]# gdb /usr/local/sbin/opensips
core.opensips.sig11.3977

GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7

Copyright (C) 2013 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later


This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"

and "show warranty" for details.

This GDB was configured as "x86_64-redhat-linux-gnu".

For bug reporting instructions, please see:

...

Reading symbols from 

Re: [OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

Hi Bogdan,

I have printed the "t" variable value. It says "$1 = (struct cell *) 0x0".
Is there any link available to upload/share the core files? Because size of the 
core file 45KB and couldn't attach in e-mail.

(gdb) frame 0
#0  final_response_handler (fr_tl=0x7fded2484110) at timer.c:383
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
(gdb) list +
378 current_processing_ctx = my_ctx;
379 /* set the T context too */
380 set_t( t );
381
382 /* out-of-lock do the cancel I/O */
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
384 set_cancel_extra_hdrs( CANCEL_REASON_SIP_480, 
sizeof(CANCEL_REASON_SIP_480)-1);
385 cancel_branch(t, r_buf->branch );
386 set_cancel_extra_hdrs( NULL, 0);
387 }
(gdb) p t
$1 = (struct cell *) 0x0

Regards,
Agalya

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Tuesday, October 04, 2016 6:44 AM
To: Ramachandran, Agalya (Contractor) ; 
OpenSIPS users mailling list 
Subject: Re: opensips crash when doing load test

Hello Agalya,

In frame 0, could you print the "t" variable ? BTW, is there any way to get 
access to the core file ?

Best regards,


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 30.09.2016 16:48, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,

One more dump

#0  final_response_handler (fr_tl=0x7fded2484110) at timer.c:383
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
Missing separate debuginfos, use: debuginfo-install 
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64 glibc-2.17-106.el7_2.4.x86_64 
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.13.2-12.el7_2.x86_64 
libcom_err-1.42.9-7.el7.x86_64 libcurl-7.29.0-25.el7.centos.x86_64 
libidn-1.28-4.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 
libssh2-1.4.3-10.el7_2.1.x86_64 nspr-4.10.8-2.el7_1.x86_64 
nss-3.19.1-19.el7_2.x86_64 nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64 
nss-util-3.19.1-9.el7_2.x86_64 openldap-2.4.40-9.el7_2.x86_64 
openssl-libs-1.0.1e-51.el7_2.4.x86_64 pcre-8.32-15.el7.x86_64 
xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-15.el7.x86_64
(gdb) bt
#0  final_response_handler (fr_tl=0x7fded2484110) at timer.c:383
#1  timer_routine (ticks=, set=) at timer.c:1066
#2  0x0049d3cd in handle_timer_job () at timer.c:597
#3  0x0059223e in handle_io (fm=, fm=, 
fm=, idx=, event_type=2)
at net/net_udp.c:265
#4  io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225
#5  udp_rcv_loop (si=si@entry=0x7fded841dcb0) at net/net_udp.c:308
#6  0x00593e05 in udp_start_processes (chd_rank=chd_rank@entry=0x84c570 
, startup_done=startup_done@entry=0x0)
at net/net_udp.c:448
#7  0x00419b73 in main_loop () at main.c:736
#8  main (argc=, argv=) at main.c:1282

From: Ramachandran, Agalya (Contractor)
Sent: Friday, September 30, 2016 9:44 AM
To: 'Bogdan-Andrei Iancu' ; 
OpenSIPS users mailling list 

Subject: opensips crash when doing load test

Hi Bogdan,

I have taken 2.1.4 code base, added the below fixes on top of it


1.   Fix potential starvation for the timer tasks. 
66c337cc89a2b5c3e1bbd78c289371efcda21886

2.   rest_client: Improve polling logic during TCP connect - 
c40f2b057209b8078520abc95e5d1bf5e5a28db6

3.   rest_client: Add "connect_poll_interval" module parameter - 
f5abfb3dee649a14ae39ad74d7f04454f815748f

4.   rest_client: Fix bogus condition 
-3ba7be6692c6987faecb9c4c904035d5e7c0f916


When I try to perform load test on that code base, randomly am seeing OpenSIPS 
is crashing.
Here is the full trace of the core file. Let me know if you need any additional 
information or logs.
Am seeing crash is occurring at start_timer_extra_processes().

[root@poc-siplb-cmc-e-004 corefiles]# gdb /usr/local/sbin/opensips 
core.opensips.sig11.3977
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/local/sbin/opensips...done.
[New LWP 3977]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/sbin/opensips -P /var/run/opensips.pid'.
Program terminated with signal 11, Segmentation fault.
#0  final_response_handler (fr_tl=0x7f55fcd82948) at timer.c:383
383 if (is_invite(t) && 

Re: [OpenSIPS-Users] opensips crash when doing load test

[Bogdan-Andrei Iancu]

Hello Agalya,

In frame 0, could you print the "t" variable ? BTW, is there any way to 
get access to the core file ?


Best regards,

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

On 30.09.2016 16:48, Ramachandran, Agalya (Contractor) wrote:


Hi Bogdan,

One more dump

#0 final_response_handler (fr_tl=0x7fded2484110) at timer.c:383

383 if (is_invite(t) && should_cancel_branch(t, 
r_buf->branch) ) {


Missing separate debuginfos, use: debuginfo-install 
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64 glibc-2.17-106.el7_2.4.x86_64 
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.13.2-12.el7_2.x86_64 
libcom_err-1.42.9-7.el7.x86_64 libcurl-7.29.0-25.el7.centos.x86_64 
libidn-1.28-4.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 
libssh2-1.4.3-10.el7_2.1.x86_64 nspr-4.10.8-2.el7_1.x86_64 
nss-3.19.1-19.el7_2.x86_64 nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64 
nss-util-3.19.1-9.el7_2.x86_64 openldap-2.4.40-9.el7_2.x86_64 
openssl-libs-1.0.1e-51.el7_2.4.x86_64 pcre-8.32-15.el7.x86_64 
xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-15.el7.x86_64


(gdb) bt

#0 final_response_handler (fr_tl=0x7fded2484110) at timer.c:383

#1  timer_routine (ticks=, set=) at 
timer.c:1066


#2 0x0049d3cd in handle_timer_job () at timer.c:597

#3 0x0059223e in handle_io (fm=, fm=out>, fm=, idx=, event_type=2)


at net/net_udp.c:265

#4 io_wait_loop_epoll (h=, t=, 
repeat=) at net/../io_wait_loop.h:225


#5  udp_rcv_loop (si=si@entry=0x7fded841dcb0) at net/net_udp.c:308

#6 0x00593e05 in udp_start_processes 
(chd_rank=chd_rank@entry=0x84c570 , 
startup_done=startup_done@entry=0x0)


at net/net_udp.c:448

#7 0x00419b73 in main_loop () at main.c:736

#8  main (argc=, argv=) at main.c:1282

*From:* Ramachandran, Agalya (Contractor)
*Sent:* Friday, September 30, 2016 9:44 AM
*To:* 'Bogdan-Andrei Iancu' ; OpenSIPS users 
mailling list 

*Subject:* opensips crash when doing load test

Hi Bogdan,

I have taken 2.1.4 code base, added the below fixes on top of it

1.Fix potential starvation for the timer tasks. 
66c337cc89a2b5c3e1bbd78c289371efcda21886


2.rest_client: Improve polling logic during TCP connect - 
c40f2b057209b8078520abc95e5d1bf5e5a28db6


3.rest_client: Add "connect_poll_interval" module parameter - 
f5abfb3dee649a14ae39ad74d7f04454f815748f


4.rest_client: Fix bogus condition 
-3ba7be6692c6987faecb9c4c904035d5e7c0f916


When I try to perform load test on that code base, randomly am seeing 
OpenSIPS is crashing.


Here is the full trace of the core file. Let me know if you need any 
additional information or logs.


Am seeing crash is occurring at start_timer_extra_processes().

[root@poc-siplb-cmc-e-004 corefiles]# gdb /usr/local/sbin/opensips 
core.opensips.sig11.3977


GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7

Copyright (C) 2013 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later 



This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.  Type "show copying"

and "show warranty" for details.

This GDB was configured as "x86_64-redhat-linux-gnu".

For bug reporting instructions, please see:

...

Reading symbols from /usr/local/sbin/opensips...done.

[New LWP 3977]

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib64/libthread_db.so.1".

Core was generated by `/usr/local/sbin/opensips -P /var/run/opensips.pid'.

Program terminated with signal 11, Segmentation fault.

#0 final_response_handler (fr_tl=0x7f55fcd82948) at timer.c:383

383 if (is_invite(t) && should_cancel_branch(t, 
r_buf->branch) ) {


Missing separate debuginfos, use: debuginfo-install 
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64 glibc-2.17-106.el7_2.4.x86_64 
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.13.2-12.el7_2.x86_64 
libcom_err-1.42.9-7.el7.x86_64 libcurl-7.29.0-25.el7.centos.x86_64 
libidn-1.28-4.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 
libssh2-1.4.3-10.el7_2.1.x86_64 nspr-4.10.8-2.el7_1.x86_64 
nss-3.19.1-19.el7_2.x86_64 nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64 
nss-util-3.19.1-9.el7_2.x86_64 openldap-2.4.40-9.el7_2.x86_64 
openssl-libs-1.0.1e-51.el7_2.4.x86_64 pcre-8.32-15.el7.x86_64 
xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-15.el7.x86_64


(gdb) bt

#0 final_response_handler (fr_tl=0x7f55fcd82948) at timer.c:383

#1  timer_routine (ticks=, set=) at 
timer.c:1066


#2 0x0049d03a in handle_timer_job () at timer.c:597

#3 start_timer_extra_processes (chd_rank=chd_rank@entry=0x84c570 
) at timer.c:557


#4 0x00419b9a in main_loop () at main.c:748

#5  main (argc=, argv=) at main.c:1282

Regards,

Agalya



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

Hi Bogdan,

One more dump

#0  final_response_handler (fr_tl=0x7fded2484110) at timer.c:383
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
Missing separate debuginfos, use: debuginfo-install 
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64 glibc-2.17-106.el7_2.4.x86_64 
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.13.2-12.el7_2.x86_64 
libcom_err-1.42.9-7.el7.x86_64 libcurl-7.29.0-25.el7.centos.x86_64 
libidn-1.28-4.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 
libssh2-1.4.3-10.el7_2.1.x86_64 nspr-4.10.8-2.el7_1.x86_64 
nss-3.19.1-19.el7_2.x86_64 nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64 
nss-util-3.19.1-9.el7_2.x86_64 openldap-2.4.40-9.el7_2.x86_64 
openssl-libs-1.0.1e-51.el7_2.4.x86_64 pcre-8.32-15.el7.x86_64 
xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-15.el7.x86_64
(gdb) bt
#0  final_response_handler (fr_tl=0x7fded2484110) at timer.c:383
#1  timer_routine (ticks=, set=) at timer.c:1066
#2  0x0049d3cd in handle_timer_job () at timer.c:597
#3  0x0059223e in handle_io (fm=, fm=, 
fm=, idx=, event_type=2)
at net/net_udp.c:265
#4  io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225
#5  udp_rcv_loop (si=si@entry=0x7fded841dcb0) at net/net_udp.c:308
#6  0x00593e05 in udp_start_processes (chd_rank=chd_rank@entry=0x84c570 
, startup_done=startup_done@entry=0x0)
at net/net_udp.c:448
#7  0x00419b73 in main_loop () at main.c:736
#8  main (argc=, argv=) at main.c:1282

From: Ramachandran, Agalya (Contractor)
Sent: Friday, September 30, 2016 9:44 AM
To: 'Bogdan-Andrei Iancu' ; OpenSIPS users mailling list 

Subject: opensips crash when doing load test

Hi Bogdan,

I have taken 2.1.4 code base, added the below fixes on top of it


1.   Fix potential starvation for the timer tasks. 
66c337cc89a2b5c3e1bbd78c289371efcda21886

2.   rest_client: Improve polling logic during TCP connect - 
c40f2b057209b8078520abc95e5d1bf5e5a28db6

3.   rest_client: Add "connect_poll_interval" module parameter - 
f5abfb3dee649a14ae39ad74d7f04454f815748f

4.   rest_client: Fix bogus condition 
-3ba7be6692c6987faecb9c4c904035d5e7c0f916


When I try to perform load test on that code base, randomly am seeing OpenSIPS 
is crashing.
Here is the full trace of the core file. Let me know if you need any additional 
information or logs.
Am seeing crash is occurring at start_timer_extra_processes().

[root@poc-siplb-cmc-e-004 corefiles]# gdb /usr/local/sbin/opensips 
core.opensips.sig11.3977
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/local/sbin/opensips...done.
[New LWP 3977]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/sbin/opensips -P /var/run/opensips.pid'.
Program terminated with signal 11, Segmentation fault.
#0  final_response_handler (fr_tl=0x7f55fcd82948) at timer.c:383
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
Missing separate debuginfos, use: debuginfo-install 
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64 glibc-2.17-106.el7_2.4.x86_64 
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.13.2-12.el7_2.x86_64 
libcom_err-1.42.9-7.el7.x86_64 libcurl-7.29.0-25.el7.centos.x86_64 
libidn-1.28-4.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 
libssh2-1.4.3-10.el7_2.1.x86_64 nspr-4.10.8-2.el7_1.x86_64 
nss-3.19.1-19.el7_2.x86_64 nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64 
nss-util-3.19.1-9.el7_2.x86_64 openldap-2.4.40-9.el7_2.x86_64 
openssl-libs-1.0.1e-51.el7_2.4.x86_64 pcre-8.32-15.el7.x86_64 
xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-15.el7.x86_64
(gdb) bt
#0  final_response_handler (fr_tl=0x7f55fcd82948) at timer.c:383
#1  timer_routine (ticks=, set=) at timer.c:1066
#2  0x0049d03a in handle_timer_job () at timer.c:597
#3  start_timer_extra_processes (chd_rank=chd_rank@entry=0x84c570 
) at timer.c:557
#4  0x00419b9a in main_loop () at main.c:748
#5  main (argc=, argv=) at main.c:1282

Regards,
Agalya

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] opensips crash when doing load test

[Ramachandran, Agalya (Contractor)]

Hi Bogdan,

I have taken 2.1.4 code base, added the below fixes on top of it


1.   Fix potential starvation for the timer tasks. 
66c337cc89a2b5c3e1bbd78c289371efcda21886

2.   rest_client: Improve polling logic during TCP connect - 
c40f2b057209b8078520abc95e5d1bf5e5a28db6

3.   rest_client: Add "connect_poll_interval" module parameter - 
f5abfb3dee649a14ae39ad74d7f04454f815748f

4.   rest_client: Fix bogus condition 
-3ba7be6692c6987faecb9c4c904035d5e7c0f916


When I try to perform load test on that code base, randomly am seeing OpenSIPS 
is crashing.
Here is the full trace of the core file. Let me know if you need any additional 
information or logs.
Am seeing crash is occurring at start_timer_extra_processes().

[root@poc-siplb-cmc-e-004 corefiles]# gdb /usr/local/sbin/opensips 
core.opensips.sig11.3977
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/local/sbin/opensips...done.
[New LWP 3977]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/sbin/opensips -P /var/run/opensips.pid'.
Program terminated with signal 11, Segmentation fault.
#0  final_response_handler (fr_tl=0x7f55fcd82948) at timer.c:383
383 if (is_invite(t) && should_cancel_branch(t, r_buf->branch) ) {
Missing separate debuginfos, use: debuginfo-install 
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64 glibc-2.17-106.el7_2.4.x86_64 
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.13.2-12.el7_2.x86_64 
libcom_err-1.42.9-7.el7.x86_64 libcurl-7.29.0-25.el7.centos.x86_64 
libidn-1.28-4.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 
libssh2-1.4.3-10.el7_2.1.x86_64 nspr-4.10.8-2.el7_1.x86_64 
nss-3.19.1-19.el7_2.x86_64 nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64 
nss-util-3.19.1-9.el7_2.x86_64 openldap-2.4.40-9.el7_2.x86_64 
openssl-libs-1.0.1e-51.el7_2.4.x86_64 pcre-8.32-15.el7.x86_64 
xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-15.el7.x86_64
(gdb) bt
#0  final_response_handler (fr_tl=0x7f55fcd82948) at timer.c:383
#1  timer_routine (ticks=, set=) at timer.c:1066
#2  0x0049d03a in handle_timer_job () at timer.c:597
#3  start_timer_extra_processes (chd_rank=chd_rank@entry=0x84c570 
) at timer.c:557
#4  0x00419b9a in main_loop () at main.c:748
#5  main (argc=, argv=) at main.c:1282

Regards,
Agalya

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash!!!!!!

[Dragomir Haralambiev]

Hi,

Thanks for your replay.

Yes I use radius.

Radius not possible use from latest STABLE version?
Realy?

Regards,


2015-11-03 16:59 GMT+02:00 Arsen :

> Hey Dragomir,
>
> Do you use radius in your setup?
> I had exactly same issue when i was trying to send radius acct request.
>
> You can check this issue here in the list "opensips 2.1 custom radius
> accounting error"
>
> Regards,
> Arsen
>
>
> On Tuesday, 3 November 2015, Dragomir Haralambiev 
> wrote:
>
>> Hello all,
>>
>> I am upgrading opensips from v1.11 to v2.1.1.
>>
>> I am having following wearings continuously after first call:
>>
>> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
>>  already schedualed for 1548180 ms (now 1548280 ms), it may
>> overlap..
>> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
>>  already schedualed for 1548280 ms (now 1548380 ms), it may
>> overlap..
>> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
>>  already schedualed for 1545910 ms (now 1548380 ms), it may
>> overlap..
>> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
>>  already schedualed for 1545910 ms (now 1548380 ms), it may
>> overlap..
>> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
>>  already schedualed for 1545910 ms (now 1548380 ms), it may
>> overlap..
>> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
>>  already schedualed for 1545910 ms (now 1548380 ms), it may
>> overlap..
>> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
>>  already schedualed for 1548380 ms (now 1548480 ms), it may
>> overlap..
>> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
>>  already schedualed for 1548480 ms (now 1548580 ms), it may
>> overlap..
>>
>>
>> Where is problem?
>>
>> Regards,
>> PlayMen
>>
>
>
> --
> Regards,
> Arsen.
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Opensips crash!!!!!!

[Dragomir Haralambiev]

Hello all,

I am upgrading opensips from v1.11 to v2.1.1.

I am having following wearings continuously after first call:

Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
 already schedualed for 1548180 ms (now 1548280 ms), it may
overlap..
Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
 already schedualed for 1548280 ms (now 1548380 ms), it may
overlap..
Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
 already schedualed for 1545910 ms (now 1548380 ms), it may
overlap..
Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
 already schedualed for 1545910 ms (now 1548380 ms), it may
overlap..
Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
 already schedualed for 1545910 ms (now 1548380 ms), it may
overlap..
Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
 already schedualed for 1545910 ms (now 1548380 ms), it may
overlap..
Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
 already schedualed for 1548380 ms (now 1548480 ms), it may
overlap..
Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
 already schedualed for 1548480 ms (now 1548580 ms), it may
overlap..


Where is problem?

Regards,
PlayMen
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips crash!!!!!!

[Arsen]

Hey Dragomir,

Do you use radius in your setup?
I had exactly same issue when i was trying to send radius acct request.

You can check this issue here in the list "opensips 2.1 custom radius
accounting error"

Regards,
Arsen

On Tuesday, 3 November 2015, Dragomir Haralambiev 
wrote:

> Hello all,
>
> I am upgrading opensips from v1.11 to v2.1.1.
>
> I am having following wearings continuously after first call:
>
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
>  already schedualed for 1548180 ms (now 1548280 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
>  already schedualed for 1548280 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
>  already schedualed for 1545910 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
>  already schedualed for 1545910 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
>  already schedualed for 1545910 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:timer_ticker: timer task
>  already schedualed for 1545910 ms (now 1548380 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
>  already schedualed for 1548380 ms (now 1548480 ms), it may
> overlap..
> Oct 30 14:52:11 sbc  [32140]: WARNING:core:utimer_ticker: utimer task
>  already schedualed for 1548480 ms (now 1548580 ms), it may
> overlap..
>
>
> Where is problem?
>
> Regards,
> PlayMen
>


-- 
Regards,
Arsen.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS crash

[Bogdan-Andrei Iancu]

Hi Stas,

Thank you for you help in troubleshooting and fixing the problem. The 
fix is now available on GIT for all maintained branches.


Best regards,

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

On 31.08.2015 23:07, Bogdan-Andrei Iancu wrote:

Hi Stas,

In frame 0, please print in gdb:
_c->callid
_ci->callid
*_ci->callid

Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 31.08.2015 18:32, Stas Kobzar wrote:

Hello list,

We had OpenSIPS crashed. Please, find attached crash full stack trace 
from core file attached.

OpenSIPS version:
version: opensips 1.11.5-notls (x86_64/linux)
flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, 
SHM_MEM, SHM_MMAP, PKG_MALLOC, F_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: 02a7c06
main.c compiled on 18:04:23 Jul 16 2015 with gcc 4.4.7

I am not sure, but it looks like the problem is MI command ul_add. We 
use datagram  MI to add/remove permanent user locations via web 
interface.


Before we were using XML-rpc and we had similar problem. That's why 
we moved to datagram.


Please, advice.
Thank you!

P.S. As it is mentioned in OpenSIPS web-site, I have posted it first 
to devel list. But my email was bounced as I am not a member of the 
list.

Should I send it to OpenSIPS github issues?
--

Stas Kobzar

Developeur VoIP / VoIP Developer

___


Modulis­.ca Inc.

# Bureau / Office: 514-284-2020 x 246

Email: s tas.kob...@modulis.ca

https://www.modulis.com 





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS crash

[Stas Kobzar]

Thank you very much, Bogdan!
As always, OpenSIPS team provides fast and professional support!

Have a good day!






On Tue, Sep 1, 2015 at 3:11 PM, Bogdan-Andrei Iancu 
wrote:

> Hi Stas,
>
> Thank you for you help in troubleshooting and fixing the problem. The fix
> is now available on GIT for all maintained branches.
>
> Best regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 31.08.2015 23:07, Bogdan-Andrei Iancu wrote:
>
> Hi Stas,
>
> In frame 0, please print in gdb:
> _c->callid
> _ci->callid
> *_ci->callid
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 31.08.2015 18:32, Stas Kobzar wrote:
>
> Hello list,
>
> We had OpenSIPS crashed. Please, find attached crash full stack trace from
> core file attached.
> OpenSIPS version:
> version: opensips 1.11.5-notls (x86_64/linux)
> flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
> SHM_MMAP, PKG_MALLOC, F_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: 02a7c06
> main.c compiled on 18:04:23 Jul 16 2015 with gcc 4.4.7
>
> I am not sure, but it looks like the problem is MI command ul_add. We use
> datagram  MI to add/remove permanent user locations via web interface.
>
> Before we were using XML-rpc and we had similar problem. That's why we
> moved to datagram.
>
> Please, advice.
> Thank you!
>
> P.S. As it is mentioned in OpenSIPS web-site, I have posted it first to
> devel list. But my email was bounced as I am not a member of the list.
> Should I send it to OpenSIPS github issues?
> --
>
> Stas Kobzar
>
> Developeur VoIP / VoIP Developer
>
> ___
>
> Modulis­.ca Inc.
>
> # Bureau / Office: 514-284-2020 x 246
>
> Email: s tas.kob...@modulis.ca
>
> https://www.modulis.com
>
> 
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>


-- 

Stas Kobzar

Developeur VoIP / VoIP Developer

___

Modulis­.ca Inc.

# Bureau / Office: 514-284-2020 x 246

Email: s tas.kob...@modulis.ca

https://www.modulis.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] OpenSIPS crash

[Stas Kobzar]

Hello list,

We had OpenSIPS crashed. Please, find attached crash full stack trace from
core file attached.
OpenSIPS version:
version: opensips 1.11.5-notls (x86_64/linux)
flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
SHM_MMAP, PKG_MALLOC, F_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: 02a7c06
main.c compiled on 18:04:23 Jul 16 2015 with gcc 4.4.7

I am not sure, but it looks like the problem is MI command ul_add. We use
datagram  MI to add/remove permanent user locations via web interface.

Before we were using XML-rpc and we had similar problem. That's why we
moved to datagram.

Please, advice.
Thank you!

P.S. As it is mentioned in OpenSIPS web-site, I have posted it first to
devel list. But my email was bounced as I am not a member of the list.
Should I send it to OpenSIPS github issues?
-- 

Stas Kobzar

Developeur VoIP / VoIP Developer

___

Modulis­.ca Inc.

# Bureau / Office: 514-284-2020 x 246

Email: s tas.kob...@modulis.ca

https://www.modulis.com


(gdb) bt full
#0  0x7f6ca92e09ef in mem_update_ucontact (_c=0x7f6c84cdc6d8, 
_ci=0x7fff18013e70) at ucontact.c:262
ptr = 
__FUNCTION__ = "mem_update_ucontact"
#1  0x7f6ca92e39d2 in update_ucontact (_r=0x7f6c84d16b58, 
_c=0x7f6c84cdc6d8, _ci=0x7fff18013e70, is_replicated=0 '\000') at ucontact.c:923
ret = 
__FUNCTION__ = "update_ucontact"
#2  0x7f6ca92eb201 in mi_usrloc_add (cmd=, 
param=) at ul_mi.c:542
ci = {received = {s = 0x0, len = 0}, path = 0x0, expires = 0, q = 1000, 
instance = {s = 0x0, len = 0}, callid = 0x0, cseq = 1, flags = 0, cflags = 0, 
user_agent = 0x7f6ca94fbac0, sock = 0x0, methods = 4294967295, last_modified = 
0, attr = 0x0}
r = 0x7f6c84d16b58
c = 0x7f6c84cdc6d8
node = 
dom = 0x7f6c84c21cc8
aor = 0x7f6cabb0b440
contact = 
ui_val = 
n = 
#3  0x7f6ca9eeb241 in run_mi_cmd (rx_sock=7, tx_sock=7) at ../../mi/mi.h:109
ret = 
#4  mi_datagram_server (rx_sock=7, tx_sock=7) at datagram_fnc.c:520
mi_cmd = 
mi_rpl = 
hdl = 0x0
f = 0x7f6cabac4188
dtgram = {start = 0x7f6cabafb270 ":ul_add", current = 0x7f6cabafb2cc 
"", len = 0}
ret = 
len = 
__FUNCTION__ = "mi_datagram_server"
#5  0x7f6ca9eecd83 in datagram_process (rank=0) at mi_datagram.c:311
__FUNCTION__ = "datagram_process"
#6  0x004af269 in start_module_procs () at sr_module.c:586
m = 
n = 
l = 
x = 
__FUNCTION__ = "start_module_procs"
#7  0x0043a5b0 in main_loop (argc=, argv=) at main.c:852
---Type  to continue, or q  to quit---
i = 
pid = 
si = 0x0
startup_done = 0x0
chd_rank = 0
rc = 
load_p = 0x0
#8  main (argc=, argv=) at main.c:1612
cfg_log_stderr = 
cfg_stream = 
c = 
r = 0
tmp = 0x7fff18014e5e ""
tmp_len = 
port = 
proto = 
options = 0x576ca0 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:"
ret = -1
seed = 933295776
rfd = 
__FUNCTION__ = "main"
(gdb)___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS crash

[Stas Kobzar]

Hello,
Another crash just happened.
Please, find attached gdb bt full.

Thank you,


On Mon, Aug 31, 2015 at 11:32 AM, Stas Kobzar 
wrote:

> Hello list,
>
> We had OpenSIPS crashed. Please, find attached crash full stack trace from
> core file attached.
> OpenSIPS version:
> version: opensips 1.11.5-notls (x86_64/linux)
> flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
> SHM_MMAP, PKG_MALLOC, F_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: 02a7c06
> main.c compiled on 18:04:23 Jul 16 2015 with gcc 4.4.7
>
> I am not sure, but it looks like the problem is MI command ul_add. We use
> datagram  MI to add/remove permanent user locations via web interface.
>
> Before we were using XML-rpc and we had similar problem. That's why we
> moved to datagram.
>
> Please, advice.
> Thank you!
>
> P.S. As it is mentioned in OpenSIPS web-site, I have posted it first to
> devel list. But my email was bounced as I am not a member of the list.
> Should I send it to OpenSIPS github issues?
> --
>
> Stas Kobzar
>
> Developeur VoIP / VoIP Developer
>
> ___
>
> Modulis­.ca Inc.
>
> # Bureau / Office: 514-284-2020 x 246
>
> Email: s tas.kob...@modulis.ca
>
> https://www.modulis.com
>
> 
>



-- 

Stas Kobzar

Developeur VoIP / VoIP Developer

___

Modulis­.ca Inc.

# Bureau / Office: 514-284-2020 x 246

Email: s tas.kob...@modulis.ca

https://www.modulis.com


#0  0x7fcd682cc9ef in mem_update_ucontact (_c=0x7fcd43d682c8, 
_ci=0x7fffde2509a0) at ucontact.c:262
ptr = 
__FUNCTION__ = "mem_update_ucontact"
#1  0x7fcd682cf9d2 in update_ucontact (_r=0x7fcd43d62088, 
_c=0x7fcd43d682c8, _ci=0x7fffde2509a0, is_replicated=0 '\000') at ucontact.c:923
ret = 
__FUNCTION__ = "update_ucontact"
#2  0x7fcd682d7201 in mi_usrloc_add (cmd=, 
param=) at ul_mi.c:542
ci = {received = {s = 0x0, len = 0}, path = 0x0, expires = 0, q = 1000, 
instance = {s = 0x0, len = 0}, callid = 0x0, cseq = 1, flags = 0, cflags = 0, 
  user_agent = 0x7fcd684e7ac0, sock = 0x0, methods = 4294967295, 
last_modified = 0, attr = 0x0}
r = 0x7fcd43d62088
c = 0x7fcd43d682c8
node = 
dom = 0x7fcd43c7c6f8
aor = 0x7fcd6aae8860
contact = 
ui_val = 
n = 
#3  0x7fcd68ed7241 in run_mi_cmd (rx_sock=7, tx_sock=7) at ../../mi/mi.h:109
ret = 
#4  mi_datagram_server (rx_sock=7, tx_sock=7) at datagram_fnc.c:520
mi_cmd = 
mi_rpl = 
hdl = 0x0
f = 0x7fcd6aab1fd0
dtgram = {start = 0x7fcd6aaec380 ":ul_add", current = 0x7fcd6aaec3dc 
"", len = 0}
ret = 
len = 
__FUNCTION__ = "mi_datagram_server"
#5  0x7fcd68ed8d83 in datagram_process (rank=0) at mi_datagram.c:311
__FUNCTION__ = "datagram_process"
#6  0x004af269 in start_module_procs () at sr_module.c:586
m = 
n = 
l = 
x = 
__FUNCTION__ = "start_module_procs"
#7  0x0043a5b0 in main_loop (argc=, argv=) at main.c:852
i = 
pid = 
si = 0x0
startup_done = 0x0
chd_rank = 0
rc = 
load_p = 0x0
#8  main (argc=, argv=) at main.c:1612
cfg_log_stderr = 
cfg_stream = 
c = 
r = 0
tmp = 0x7fffde252e5e ""
tmp_len = 
port = 
proto = 
options = 0x576ca0 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:"
ret = -1
seed = 344037650
rfd = 
__FUNCTION__ = "main"
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS crash

[Stas Kobzar]

Hello,
We had a couple another crashes which looks very much the same.
Please, see attached.

Thank you,

On Mon, Aug 31, 2015 at 12:00 PM, Stas Kobzar 
wrote:

> Hello,
> Another crash just happened.
> Please, find attached gdb bt full.
>
> Thank you,
>
>
> On Mon, Aug 31, 2015 at 11:32 AM, Stas Kobzar 
> wrote:
>
>> Hello list,
>>
>> We had OpenSIPS crashed. Please, find attached crash full stack trace
>> from core file attached.
>> OpenSIPS version:
>> version: opensips 1.11.5-notls (x86_64/linux)
>> flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
>> SHM_MMAP, PKG_MALLOC, F_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: 02a7c06
>> main.c compiled on 18:04:23 Jul 16 2015 with gcc 4.4.7
>>
>> I am not sure, but it looks like the problem is MI command ul_add. We use
>> datagram  MI to add/remove permanent user locations via web interface.
>>
>> Before we were using XML-rpc and we had similar problem. That's why we
>> moved to datagram.
>>
>> Please, advice.
>> Thank you!
>>
>> P.S. As it is mentioned in OpenSIPS web-site, I have posted it first to
>> devel list. But my email was bounced as I am not a member of the list.
>> Should I send it to OpenSIPS github issues?
>> --
>>
>> Stas Kobzar
>>
>> Developeur VoIP / VoIP Developer
>>
>> ___
>>
>> Modulis­.ca Inc.
>>
>> # Bureau / Office: 514-284-2020 x 246
>>
>> Email: s tas.kob...@modulis.ca
>>
>> https://www.modulis.com
>>
>> 
>>
>
>
>
> --
>
> Stas Kobzar
>
> Developeur VoIP / VoIP Developer
>
> ___
>
> Modulis­.ca Inc.
>
> # Bureau / Office: 514-284-2020 x 246
>
> Email: s tas.kob...@modulis.ca
>
> https://www.modulis.com
>
> 
>



-- 

Stas Kobzar

Developeur VoIP / VoIP Developer

___

Modulis­.ca Inc.

# Bureau / Office: 514-284-2020 x 246

Email: s tas.kob...@modulis.ca

https://www.modulis.com


#0  0x7f18d62559ef in mem_update_ucontact (_c=0x7f18b2334458, 
_ci=0x7fff100b4580) at ucontact.c:262
ptr = 
__FUNCTION__ = "mem_update_ucontact"
#1  0x7f18d62589d2 in update_ucontact (_r=0x7f18b1f7e5b0, 
_c=0x7f18b2334458, _ci=0x7fff100b4580, is_replicated=0 '\000') at ucontact.c:923
ret = 
__FUNCTION__ = "update_ucontact"
#2  0x7f18d6260201 in mi_usrloc_add (cmd=, 
param=) at ul_mi.c:542
ci = {received = {s = 0x0, len = 0}, path = 0x0, expires = 0, q = 1000, 
instance = {s = 0x0, len = 0}, callid = 0x0, cseq = 1, flags = 0, cflags = 0, 
  user_agent = 0x7f18d6470ac0, sock = 0x0, methods = 4294967295, 
last_modified = 0, attr = 0x0}
r = 0x7f18b1f7e5b0
c = 0x7f18b2334458
node = 
dom = 0x7f18b1c10b20
aor = 0x7f18d8a71238
contact = 
ui_val = 
n = 
#3  0x7f18d6e60241 in run_mi_cmd (rx_sock=7, tx_sock=7) at ../../mi/mi.h:109
ret = 
#4  mi_datagram_server (rx_sock=7, tx_sock=7) at datagram_fnc.c:520
mi_cmd = 
mi_rpl = 
hdl = 0x0
f = 0x7f18d8a3b080
dtgram = {start = 0x7f18d8a72940 ":ul_add", current = 0x7f18d8a7299c 
"", len = 0}
ret = 
len = 
__FUNCTION__ = "mi_datagram_server"
#5  0x7f18d6e61d83 in datagram_process (rank=0) at mi_datagram.c:311
__FUNCTION__ = "datagram_process"
#6  0x004af269 in start_module_procs () at sr_module.c:586
m = 
n = 
l = 
x = 
__FUNCTION__ = "start_module_procs"
#7  0x0043a5b0 in main_loop (argc=, argv=) at main.c:852
i = 
pid = 
si = 0x0
startup_done = 0x0
chd_rank = 0
rc = 
load_p = 0x0
#8  main (argc=, argv=) at main.c:1612
cfg_log_stderr = 
cfg_stream = 
c = 
r = 0
tmp = 0x7fff100b5e5e ""
tmp_len = 
port = 
proto = 
options = 0x576ca0 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:"
ret = -1
seed = 3732902674
rfd = 
__FUNCTION__ = "main"
#0  0x7ff1a1af69ef in mem_update_ucontact (_c=0x7ff17d594410, 
_ci=0x7fff482488a0) at ucontact.c:262
ptr = 
__FUNCTION__ = "mem_update_ucontact"
#1  0x7ff1a1af99d2 in update_ucontact (_r=0x7ff17d020c08, 
_c=0x7ff17d594410, _ci=0x7fff482488a0, is_replicated=0 '\000') at ucontact.c:923
ret = 
__FUNCTION__ = "update_ucontact"
#2  0x7ff1a1b01201 in mi_usrloc_add (cmd=, 
param=) at ul_mi.c:542
ci = {received = {s = 0x0, len = 0}, path = 0x0, expires = 0, q = 1000, 
instance = {s = 0x0, len = 0}, callid = 0x0, cseq = 1, flags = 0, cflags = 0, 
  

Re: [OpenSIPS-Users] OpenSIPS crash

[Bogdan-Andrei Iancu]

Hi Stas,

In frame 0, please print in gdb:
_c->callid
_ci->callid
*_ci->callid

Regards,

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

On 31.08.2015 18:32, Stas Kobzar wrote:

Hello list,

We had OpenSIPS crashed. Please, find attached crash full stack trace 
from core file attached.

OpenSIPS version:
version: opensips 1.11.5-notls (x86_64/linux)
flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, 
SHM_MEM, SHM_MMAP, PKG_MALLOC, F_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: 02a7c06
main.c compiled on 18:04:23 Jul 16 2015 with gcc 4.4.7

I am not sure, but it looks like the problem is MI command ul_add. We 
use datagram  MI to add/remove permanent user locations via web 
interface.


Before we were using XML-rpc and we had similar problem. That's why we 
moved to datagram.


Please, advice.
Thank you!

P.S. As it is mentioned in OpenSIPS web-site, I have posted it first 
to devel list. But my email was bounced as I am not a member of the list.

Should I send it to OpenSIPS github issues?
--

Stas Kobzar

Developeur VoIP / VoIP Developer

___


Modulis­.ca Inc.

# Bureau / Office: 514-284-2020 x 246

Email: s tas.kob...@modulis.ca

https://www.modulis.com 





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] opensips crash when imc_mi_list_rooms

[Dani Popa]

Hi,
My opensips crash when try to list imc rooms: opensipsctl fifo
imc_list_rooms


see the trace:

(gdb) bt full

#0  imc_mi_list_rooms (cmd_tree=0x0, param=0x0) at imc.c:714

i = optimized out

len = 1

rpl_tree = 0xb71b49b0

rpl = 0xb71b49c0

node = 0xb71b49f4

attr = optimized out

irp = 0xb49b3b94

p = optimized out

#1  0xb70d60fc in run_mi_cmd (param=0x8b3c8a8, f=optimized out, t=0x0,
cmd=optimized out) at ../../mi/mi.h:109

ret = optimized out

#2  mi_fifo_server (fifo_stream=fifo_stream@entry=0x8b38378) at
fifo_fnc.c:490

mi_cmd = optimized out

mi_rpl = 0xb71a6a10

hdl = 0x0

line_len = 1

file_sep = optimized out

command = optimized out

file = optimized out

f = 0xb71a6a10

reply_stream = 0x8b3c8a8

__FUNCTION__ = mi_fifo_server

#3  0xb70d7601 in fifo_process (rank=0) at mi_fifo.c:213

fifo_stream = 0x8b38378

__FUNCTION__ = fifo_process

#4  0x080ed8bf in start_module_procs () at sr_module.c:586

m = optimized out

n = optimized out

l = optimized out

x = optimized out

__FUNCTION__ = start_module_procs

#5  0x0805df6d in main_loop () at main.c:865

i = optimized out

pid = optimized out

si = optimized out

startup_done = 0x0

chd_rank = 0

rc = optimized out

load_p = 0x0

#6  main (argc=5, argv=0xbfd244e4) at main.c:1634

cfg_log_stderr = optimized out

cfg_stream = 0x8b24008

c = optimized out

r = optimized out

tmp = 0x5 Address 0x5 out of bounds

tmp_len = optimized out

port = optimized out

proto = optimized out

options = 0x81e78f8 f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:

ret = -1

seed = 1704724837

rfd = optimized out

__FUNCTION__ = main

Regards,
-- 
Dani Popa
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash when imc_mi_list_rooms

[Bogdan-Andrei Iancu]

Hey Dany,

What version of OpenSIPS are you using ?

Also, can you provide (off list) the DB conf you / rooms sets you may 
have (or whatever is required to reproduce the crash).


Thanks and regards,

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

On 15.06.2015 18:31, Dani Popa wrote:

Hi,
My opensips crash when try to list imc rooms: opensipsctl fifo 
imc_list_rooms



see the trace:

(gdb) bt full

#0  imc_mi_list_rooms (cmd_tree=0x0, param=0x0) at imc.c:714

i = optimized out

len = 1

rpl_tree = 0xb71b49b0

rpl = 0xb71b49c0

node = 0xb71b49f4

attr = optimized out

irp = 0xb49b3b94

p = optimized out

#1  0xb70d60fc in run_mi_cmd (param=0x8b3c8a8, f=optimized out, 
t=0x0, cmd=optimized out) at ../../mi/mi.h:109


ret = optimized out

#2  mi_fifo_server (fifo_stream=fifo_stream@entry=0x8b38378) at 
fifo_fnc.c:490


mi_cmd = optimized out

mi_rpl = 0xb71a6a10

hdl = 0x0

line_len = 1

file_sep = optimized out

command = optimized out

file = optimized out

f = 0xb71a6a10

reply_stream = 0x8b3c8a8

__FUNCTION__ = mi_fifo_server

#3  0xb70d7601 in fifo_process (rank=0) at mi_fifo.c:213

fifo_stream = 0x8b38378

__FUNCTION__ = fifo_process

#4  0x080ed8bf in start_module_procs () at sr_module.c:586

m = optimized out

n = optimized out

l = optimized out

x = optimized out

__FUNCTION__ = start_module_procs

#5  0x0805df6d in main_loop () at main.c:865

i = optimized out

pid = optimized out

si = optimized out

startup_done = 0x0

chd_rank = 0

rc = optimized out

load_p = 0x0

#6  main (argc=5, argv=0xbfd244e4) at main.c:1634

cfg_log_stderr = optimized out

cfg_stream = 0x8b24008

c = optimized out

r = optimized out

tmp = 0x5 Address 0x5 out of bounds

tmp_len = optimized out

port = optimized out

proto = optimized out

options = 0x81e78f8 f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:

ret = -1

seed = 1704724837

rfd = optimized out

__FUNCTION__ = main


Regards,
--
Dani Popa


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash with location data

[Bogdan-Andrei Iancu]

Hi Pasan,

Glad the problem was fixed.

Most of the modules rely on the fact the DB schema is correct and all 
columns have the correct type. So, they do not actually check that - 
just a few are doing.
Probably it will be a good practice to have all of them doing that kind 
of checks. I will add that on the TODO list :).


Regards,

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

On 12.06.2014 06:53, Pasan Meemaduma wrote:


Hi Bogdan.

I can confirm the opensips crash stopped after I used the correct 
schema. Is it possible to add better erorr handling to such situation 
? or is it a overhead ?


On Wednesday, 11 June 2014, 7:46, Pasan Meemaduma pasan...@ymail.com 
wrote:






Hi Bogdan,

appologies for my late reply. I got problem with accessing my email 
account from home. :(


Thanks for the help in spotting the mistake I did :'(. I'll fix the 
location table and see how it goes. :)




On Friday, 6 June 2014, 16:58, Bogdan-Andrei Iancu 
bog...@opensips.org wrote:



no, it is not related to that :) - see my previous email.

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


___
Users mailing list
Users@lists.opensips.org mailto:Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash with location data

[Pasan Meemaduma]

Hi Bogdan,

appologies for my late reply. I got problem with accessing my email account 
from home. :(

Thanks for the help in spotting the mistake I did :'(. I'll fix the location 
table and see how it goes. :)




On Friday, 6 June 2014, 16:58, Bogdan-Andrei Iancu bog...@opensips.org wrote:
 


no, it is not related to that :) - see my previous email.

Regards,
 
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 06.06.2014 06:35, Pasan Meemaduma wrote:

Hi Bogdan,


I just found that I have got the key constraint wrong. Will that be the issue ?


| location | CREATE TABLE `location` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `username` char(64) NOT NULL DEFAULT '',
  `domain` char(64) DEFAULT NULL,
  `contact` char(255) NOT NULL DEFAULT '',
  `received` char(128) DEFAULT NULL,
  `path` char(128) DEFAULT NULL,
  `expires` datetime NOT NULL DEFAULT '2020-05-28 21:32:15',
  `q` float(10,2) NOT NULL DEFAULT '1.00',
  `callid` char(255) NOT NULL DEFAULT 'Default-Call-ID',
  `cseq` int(11) NOT NULL DEFAULT '13',
  `last_modified` datetime NOT NULL DEFAULT '1900-01-01
00:00:01',
  `flags` int(11) NOT NULL DEFAULT '0',
  `cflags` int(11) NOT NULL DEFAULT '0',
  `user_agent` char(255) NOT NULL DEFAULT '',
  `socket` char(64) DEFAULT NULL,
  `methods` int(11) DEFAULT NULL,
  `sip_instance` char(255) DEFAULT NULL,
  `attr` char(255) DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `account_contact_idx` (`username`,`domain`,`contact`)
) ENGINE=MyISAM AUTO_INCREMENT=25375081 DEFAULT
CHARSET=latin1 |



account_contact_idx is missing callid column. Will this has any relation to 
crash ?




On Friday, 6 June 2014, 8:48, Pasan Meemaduma pasan...@ymail.com wrote:
 


Hi Bogdan,


Thanks for the reply. I created the table using normal schema it looks fine to 
me. I was refering to the old url you gave me. There in that table attr was 
missing :)


this is the url missing attr in location table
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN7254  


below is my table schema,

mysql desc location;
+---+--+--+-+-++
| Field | Type | Null |
  Key | Default | Extra  |
+---+--+--+-+-++
| id    | int(10) unsigned | NO   |
  PRI | NULL    | auto_increment |
| username  | char(64) | NO   |
  MUL | |    |
| domain    | char(64) | YES 
  | | NULL    |    |
| contact   | char(255)    | NO  
  | | |    |
| received  | char(128)    | YES 
  | | NULL    |    |
| path  | char(128)    | YES 
  | | NULL    |    |
| expires   | datetime | NO  
  | | 2020-05-28 21:32:15 |    |
| q | float(10,2)  | NO  
  | | 1.00    |    |
| callid    | char(255)    | NO  
  | | Default-Call-ID |    |
| cseq  | int(11)  | NO  
  | | 13  |    |
| last_modified | datetime | NO  
  | | 1900-01-01 00:00:01 |    |
| flags | int(11)  | NO  
  | | 0   |    |
| cflags    | int(11)  | NO  
  | | 0   |    |
| user_agent    | char(255)    | NO  
  | | |    |
| socket    | char(64) | YES 
  | | NULL    |    |
| methods   | int(11)  | YES 
  | | NULL    |    |
| sip_instance  | char(255)    | YES 
  | | NULL    |    |
| attr  | char(255)    | YES 
  | | NULL    |    |
+---+--+--+-+-++


attr holds NULL values for all entries.

do I have to run below in gdb after running bt
  full right ?

this is what i got

(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info
  (contact=0x7fffe0246180, vals=0x7f648287a260)
  at udomain.c:306
306    in udomain.c
(gdb) p (vals+6)-val.string_val
$2 = 0x0
(gdb) 


-without running bt full
  

Re: [OpenSIPS-Users] opensips crash with location data

[Pasan Meemaduma]

Hi Bogdan,

Awesome :) . Thanks for all the help. I still can't believe I just missed that 
change. :(. I took care of lot of things when I migrate the script from 1.5 - 
1.10.



On Thursday, 12 June 2014, 17:06, Bogdan-Andrei Iancu bog...@opensips.org 
wrote:
 


Hi Pasan,

Glad the problem was fixed.

Most of the modules rely on the fact the DB schema is correct
and all columns have the correct type. So, they do not actually
check that - just a few are doing.
Probably it will be a good practice to have all of them doing
that kind of checks. I will add that on the TODO list :).

Regards,
 
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash with location data

[Pasan Meemaduma]

Hi Bogdan.

I can confirm the opensips crash stopped after I used the correct schema. Is it 
possible to add better erorr handling to such situation ? or is it a overhead ? 


On Wednesday, 11 June 2014, 7:46, Pasan Meemaduma pasan...@ymail.com wrote:
 






Hi Bogdan,


appologies for my late reply. I got problem with accessing my email account 
from home. :(

Thanks for the help in spotting the mistake I did :'(. I'll fix the location 
table and see how it goes. :)



On Friday, 6 June 2014, 16:58, Bogdan-Andrei Iancu bog...@opensips.org wrote:
 


no, it is not related to that :) - see my previous email.

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


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash with location data

[Pasan Meemaduma]

Hi Bogdan,


appologies for my late reply. I got problem with accessing my email account 
from home. :(

Thanks for the help in spotting the mistake I did :'(. I'll fix the location 
table and see how it goes. :)



On Friday, 6 June 2014, 16:58, Bogdan-Andrei Iancu bog...@opensips.org wrote:
 


no, it is not related to that :) - see my previous email.

Regards,
 
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash with location data

[Bogdan-Andrei Iancu]

Hi Pasan,

OK, the online docs were fixed, thank for the notice.

The backtrace points to the cflags field - this was changed from int 
to string - and you did not made the correct change in your table 
definition. This causes the crash.


Regards,

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

On 06.06.2014 06:18, Pasan Meemaduma wrote:

Hi Bogdan,

Thanks for the reply. I created the table using normal schema it looks 
fine to me. I was refering to the old url you gave me. There in that 
table attr was missing :)


this is the url missing attr in location table
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN7254


below is my table schema,

mysql desc location;
+---+--+--+-+-++
| Field | Type | Null | Key | Default 
| Extra  |

+---+--+--+-+-++
| id| int(10) unsigned | NO   | PRI | NULL
| auto_increment |
| username  | char(64) | NO   | MUL | 
||
| domain| char(64) | YES  | | NULL
||
| contact   | char(255)| NO   | | 
||
| received  | char(128)| YES  | | NULL
||
| path  | char(128)| YES  | | NULL
||
| expires   | datetime | NO   | | 2020-05-28 21:32:15 
||
| q | float(10,2)  | NO   | | 1.00
||
| callid| char(255)| NO   | | Default-Call-ID 
||
| cseq  | int(11)  | NO   | | 13  
||
| last_modified | datetime | NO   | | 1900-01-01 00:00:01 
||
| flags | int(11)  | NO   | | 0   
||
| cflags| int(11)  | NO   | | 0   
||
| user_agent| char(255)| NO   | | 
||
| socket| char(64) | YES  | | NULL
||
| methods   | int(11)  | YES  | | NULL
||
| sip_instance  | char(255)| YES  | | NULL
||
| attr  | char(255)| YES  | | NULL
||

+---+--+--+-+-++


attr holds NULL values for all entries.

do I have to run below in gdb after running bt full right ?

this is what i got

(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info (contact=0x7fffe0246180, 
vals=0x7f648287a260) at udomain.c:306

306in udomain.c
(gdb) p (vals+6)-val.string_val
$2 = 0x0
(gdb)


-without running bt full - just in case :)
(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info (contact=0x7fffe0246180, 
vals=0x7f648287a260) at udomain.c:306

306udomain.c: No such file or directory.
(gdb) p (vals+6)-val.string_val
$1 = 0x0






___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash with location data

[Bogdan-Andrei Iancu]

no, it is not related to that :) - see my previous email.

Regards,

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

On 06.06.2014 06:35, Pasan Meemaduma wrote:

Hi Bogdan,

I just found that I have got the key constraint wrong. Will that be 
the issue ?


| location | CREATE TABLE `location` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `username` char(64) NOT NULL DEFAULT '',
  `domain` char(64) DEFAULT NULL,
  `contact` char(255) NOT NULL DEFAULT '',
  `received` char(128) DEFAULT NULL,
  `path` char(128) DEFAULT NULL,
  `expires` datetime NOT NULL DEFAULT '2020-05-28 21:32:15',
  `q` float(10,2) NOT NULL DEFAULT '1.00',
  `callid` char(255) NOT NULL DEFAULT 'Default-Call-ID',
  `cseq` int(11) NOT NULL DEFAULT '13',
  `last_modified` datetime NOT NULL DEFAULT '1900-01-01 00:00:01',
  `flags` int(11) NOT NULL DEFAULT '0',
  `cflags` int(11) NOT NULL DEFAULT '0',
  `user_agent` char(255) NOT NULL DEFAULT '',
  `socket` char(64) DEFAULT NULL,
  `methods` int(11) DEFAULT NULL,
  `sip_instance` char(255) DEFAULT NULL,
  `attr` char(255) DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `account_contact_idx` (`username`,`domain`,`contact`)
) ENGINE=MyISAM AUTO_INCREMENT=25375081 DEFAULT CHARSET=latin1 |

account_contact_idx is missing callid column. Will this has any 
relation to crash ?



On Friday, 6 June 2014, 8:48, Pasan Meemaduma pasan...@ymail.com wrote:


Hi Bogdan,

Thanks for the reply. I created the table using normal schema it looks 
fine to me. I was refering to the old url you gave me. There in that 
table attr was missing :)


this is the url missing attr in location table
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN7254


below is my table schema,

mysql desc location;
+---+--+--+-+-++
| Field | Type | Null | Key | Default 
| Extra  |

+---+--+--+-+-++
| id| int(10) unsigned | NO   | PRI | NULL
| auto_increment |
| username  | char(64) | NO   | MUL | 
||
| domain| char(64) | YES | | NULL
||
| contact   | char(255)| NO | | 
||
| received  | char(128)| YES | | NULL
||
| path  | char(128)| YES | | NULL
||
| expires   | datetime | NO | | 2020-05-28 21:32:15 
||
| q | float(10,2)  | NO | | 1.00
||
| callid| char(255)| NO | | Default-Call-ID 
||
| cseq  | int(11)  | NO | | 13  
||
| last_modified | datetime | NO | | 1900-01-01 00:00:01 
||
| flags | int(11)  | NO | | 0   
||
| cflags| int(11)  | NO | | 0   
||
| user_agent| char(255)| NO | | 
||
| socket| char(64) | YES | | NULL
||
| methods   | int(11)  | YES | | NULL
||
| sip_instance  | char(255)| YES | | NULL
||
| attr  | char(255)| YES | | NULL
||

+---+--+--+-+-++


attr holds NULL values for all entries.

do I have to run below in gdb after running bt full right ?

this is what i got

(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info (contact=0x7fffe0246180, 
vals=0x7f648287a260) at udomain.c:306

306in udomain.c
(gdb) p (vals+6)-val.string_val
$2 = 0x0
(gdb)


-without running bt full - just in case :)
(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info (contact=0x7fffe0246180, 
vals=0x7f648287a260) at udomain.c:306

306udomain.c: No such file or directory.
(gdb) p (vals+6)-val.string_val
$1 = 0x0



On Thursday, 5 June 2014, 17:07, Bogdan-Andrei Iancu 
bog...@opensips.org wrote:



Thanks for the backtrace. In DB, what do you have for the attr value 
? NULL or an empty string ?


In gdb, could you do:
f 1
p (vals+6)-val.string_val

Thanks,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com  http://www.opensips-solutions.com/
On 05.06.2014 06:15, Pasan Meemaduma wrote:


oops sorry I forgot opensips-dbg :) bt reattached.

I have change some sensitive values with 'x' as below, hope it wont 
affect u r investigations


contact = {s = 0xf91eab sip:xxx...@xxx.xxx.xxx.xx 
mailto:sip:xxx...@xxx.xxx.xxx.xx, len = 29}



On Thursday, 5 

Re: [OpenSIPS-Users] opensips crash with location data

[Bogdan-Andrei Iancu]

Thanks for the backtrace. In DB, what do you have for the attr value ? 
NULL or an empty string ?


In gdb, could you do:
f 1
p (vals+6)-val.string_val

Thanks,

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

On 05.06.2014 06:15, Pasan Meemaduma wrote:

oops sorry I forgot opensips-dbg :) bt reattached.

I have change some sensitive values with 'x' as below, hope it wont 
affect u r investigations


contact = {s = 0xf91eab sip:xxx...@xxx.xxx.xxx.xx, len = 29}


On Thursday, 5 June 2014, 8:34, Pasan Meemaduma pasan...@ymail.com 
wrote:



Hi Bogdan,

I double checked the schema and it is correct. btw doc needs fixing 
its missing attr column which is needed by 1.10 for location table 
otherwise I'll get below error.


Jun 5 12:57:26  x/usr/sbin/opensips[30176]: 
CRITICAL:db_mysql:wrapper_single_mysql_real_query: driver error 
(1054): Unknown column 'attr' in 'field list'
Jun  5 12:57:26 x /usr/sbin/opensips[30177]: DBG:core:db_do_init: 
connection 0x7f4dc04c1c28 inserted in pool as 0x7f4dc04c1d30
Jun  5 12:57:26 x /usr/sbin/opensips[30176]: ERROR:core:db_do_query: 
error while submitting query - [select 
username,contact,expires,q,callid,cseq,flags,cflags,user_agent,received,path,socket,methods,last_modified,sip_instance,attr 
from location ]
Jun  5 12:57:26 anacardium3backup /usr/sbin/opensips[30176]: 
ERROR:usrloc:preload_udomain: db_query (1) failed


:)

I got the backtrace as you requested , It doesn't seems right to me. 
does it make any sense ? or did I miss something getting it ?






___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash with location data

[Pasan Meemaduma]

oops sorry I forgot opensips-dbg :) bt reattached.

I have change some sensitive values with 'x' as below, hope it wont affect u r 
investigations

    contact = {s = 0xf91eab sip:xxx...@xxx.xxx.xxx.xx, len = 29}



On Thursday, 5 June 2014, 8:34, Pasan Meemaduma pasan...@ymail.com wrote:
 


Hi Bogdan,

I double checked the schema and it is correct. btw doc needs fixing its missing 
attr column which is needed by 1.10 for location table otherwise I'll get below 
error.

Jun  5 12:57:26  x/usr/sbin/opensips[30176]: 
CRITICAL:db_mysql:wrapper_single_mysql_real_query: driver error (1054): Unknown 
column 'attr' in 'field list'
Jun  5 12:57:26 x /usr/sbin/opensips[30177]: DBG:core:db_do_init: connection 
0x7f4dc04c1c28 inserted in pool as 0x7f4dc04c1d30
Jun  5 12:57:26 x /usr/sbin/opensips[30176]: ERROR:core:db_do_query: error 
while submitting query - [select 
username,contact,expires,q,callid,cseq,flags,cflags,user_agent,received,path,socket,methods,last_modified,sip_instance,attr
 from location ]
Jun  5 12:57:26 anacardium3backup /usr/sbin/opensips[30176]: 
ERROR:usrloc:preload_udomain: db_query (1) failed


:)


I got the backtrace as you requested , It doesn't seems right to me.  does it 
make any sense ? or did I miss something getting it ?


gdb opensips core.opensips.sig11.29154
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by
 law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/sbin/opensips...(no debugging symbols found)...done.
[New LWP 29154]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

warning: no loadable sections found in added symbol-file system-supplied DSO at 
0x779fe000
Core was generated by `/usr/sbin/opensips -P /var/run/opensips/opensips.pid -m 
512 -M 16 -u opensips -'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f3a71ab4f21 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt full
#0  0x7f3a71ab4f21 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x7f3a703b50a2 in preload_udomain () from 
/usr/lib/opensips/modules/usrloc.so
No symbol table info available.
#2  0x7f3a703b8fb6 in ?? () from /usr/lib/opensips/modules/usrloc.so
No symbol table info available.
#3  0x0047c617 in ?? ()
No symbol table info available.
#4  0x0047c4e7 in ?? ()
No symbol table info available.
#5  0x0047c4e7 in ?? ()
No symbol table info available.
#6  0x0047c4e7 in ?? ()
No symbol table info available.
#7  0x0047c4e7 in ?? ()
No symbol table info available.
#8  0x0047c4e7 in ?? ()
No symbol table info available.
#9  0x0047c4e7 in ?? ()
No symbol table info available.
#10 0x0047c4e7 in ?? ()
No symbol table info available.
#11 0x0047c4e7 in ?? ()
No symbol table info available.
#12 0x0047c4e7 in ?? ()
No symbol table info available.
#13 0x0047c4e7 in ?? ()
No symbol table info available.
#14 0x0047c4e7 in ?? ()
No symbol table info available.
#15 0x0047c4e7 in ?? ()
No symbol table info available.
#16 0x0047c4e7 in ?? ()
No symbol table info available.
#17 0x0047c4e7 in ?? ()
No symbol table info available.
#18 0x0047c4e7 in ?? ()
No symbol table info available.
#19 0x0047c4e7 in ?? ()
No symbol table info available.
#20 0x0047c4e7 in ?? ()
No symbol table info available.
#21 0x0047c4e7 in ?? ()
No symbol table info available.
#22 0x0047c4e7 in ?? ()
No symbol table info available.
---Type return to continue, or q
 return to quit---
#23 0x0047c4e7 in ?? ()
No symbol table info available.
#24 0x0047c4e7 in ?? ()
No symbol table info available.
#25 0x0047c4e7 in ?? ()
No symbol table info available.
#26 0x0047c4e7 in ?? ()
No symbol table info available.
#27 0x0047c4e7 in ?? ()
No symbol table info available.
#28 0x0047c4e7 in ?? ()
No symbol table info available.
#29 0x004186be in main ()
No symbol table info available.




On Wednesday, 4 June 2014, 17:49, Bogdan-Andrei Iancu bog...@opensips.org 
wrote:
 


Hi Pasan,

Please be sure you are using the DB schema for 1.11 (see 
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN7254 ) - check 
the DB types and the content.

Also, follow this tutorial 
http://www.opensips.org/Documentation/TroubleShooting-Crash in order to extract 
and post here the backtrace of your crash.

Regards,
 
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer 

Re: [OpenSIPS-Users] opensips crash with location data

[Bogdan-Andrei Iancu]

Hi Pasan,

The schema is correct (see 
https://github.com/OpenSIPS/opensips/blob/1.10/scripts/mysql/usrloc-create.sql) 
- it contain the attr field. How did you created the location table 
for 1.10 ??


about the crash - looking into the bt in the next email.

Regards,

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

On 05.06.2014 06:03, Pasan Meemaduma wrote:

Hi Bogdan,

I double checked the schema and it is correct. btw doc needs fixing 
its missing attr column which is needed by 1.10 for location table 
otherwise I'll get below error.


Jun  5 12:57:26  x/usr/sbin/opensips[30176]: 
CRITICAL:db_mysql:wrapper_single_mysql_real_query: driver error 
(1054): Unknown column 'attr' in 'field list'
Jun  5 12:57:26 x /usr/sbin/opensips[30177]: DBG:core:db_do_init: 
connection 0x7f4dc04c1c28 inserted in pool as 0x7f4dc04c1d30
Jun  5 12:57:26 x /usr/sbin/opensips[30176]: ERROR:core:db_do_query: 
error while submitting query - [select 
username,contact,expires,q,callid,cseq,flags,cflags,user_agent,received,path,socket,methods,last_modified,sip_instance,attr 
from location ]
Jun  5 12:57:26 anacardium3backup /usr/sbin/opensips[30176]: 
ERROR:usrloc:preload_udomain: db_query (1) failed


:)

I got the backtrace as you requested , It doesn't seems right to me.  
does it make any sense ? or did I miss something getting it ?



gdb opensips core.opensips.sig11.29154
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
http://gnu.org/licenses/gpl.html

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/sbin/opensips...(no debugging symbols 
found)...done.

[New LWP 29154]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

warning: no loadable sections found in added symbol-file 
system-supplied DSO at 0x779fe000
Core was generated by `/usr/sbin/opensips -P 
/var/run/opensips/opensips.pid -m 512 -M 16 -u opensips -'.

Program terminated with signal 11, Segmentation fault.
#0  0x7f3a71ab4f21 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt full
#0  0x7f3a71ab4f21 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x7f3a703b50a2 in preload_udomain () from 
/usr/lib/opensips/modules/usrloc.so

No symbol table info available.
#2  0x7f3a703b8fb6 in ?? () from /usr/lib/opensips/modules/usrloc.so
No symbol table info available.
#3  0x0047c617 in ?? ()
No symbol table info available.
#4  0x0047c4e7 in ?? ()
No symbol table info available.
#5  0x0047c4e7 in ?? ()
No symbol table info available.
#6  0x0047c4e7 in ?? ()
No symbol table info available.
#7  0x0047c4e7 in ?? ()
No symbol table info available.
#8  0x0047c4e7 in ?? ()
No symbol table info available.
#9  0x0047c4e7 in ?? ()
No symbol table info available.
#10 0x0047c4e7 in ?? ()
No symbol table info available.
#11 0x0047c4e7 in ?? ()
No symbol table info available.
#12 0x0047c4e7 in ?? ()
No symbol table info available.
#13 0x0047c4e7 in ?? ()
No symbol table info available.
#14 0x0047c4e7 in ?? ()
No symbol table info available.
#15 0x0047c4e7 in ?? ()
No symbol table info available.
#16 0x0047c4e7 in ?? ()
No symbol table info available.
#17 0x0047c4e7 in ?? ()
No symbol table info available.
#18 0x0047c4e7 in ?? ()
No symbol table info available.
#19 0x0047c4e7 in ?? ()
No symbol table info available.
#20 0x0047c4e7 in ?? ()
No symbol table info available.
#21 0x0047c4e7 in ?? ()
No symbol table info available.
#22 0x0047c4e7 in ?? ()
No symbol table info available.
---Type return to continue, or q return to quit---
#23 0x0047c4e7 in ?? ()
No symbol table info available.
#24 0x0047c4e7 in ?? ()
No symbol table info available.
#25 0x0047c4e7 in ?? ()
No symbol table info available.
#26 0x0047c4e7 in ?? ()
No symbol table info available.
#27 0x0047c4e7 in ?? ()
No symbol table info available.
#28 0x0047c4e7 in ?? ()
No symbol table info available.
#29 0x004186be in main ()
No symbol table info available.



On Wednesday, 4 June 2014, 17:49, Bogdan-Andrei Iancu 
bog...@opensips.org wrote:



Hi Pasan,

Please be sure you are using the DB schema for 1.11 (see 
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN7254 ) 
- check the DB types and the content.


Also, follow this tutorial 
http://www.opensips.org/Documentation/TroubleShooting-Crash in order 
to extract and post here the 

Re: [OpenSIPS-Users] opensips crash with location data

[Pasan Meemaduma]

Hi Bogdan,

Thanks for the reply. I created the table using normal schema it looks fine to 
me. I was refering to the old url you gave me. There in that table attr was 
missing :)


this is the url missing attr in location table
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN7254  


below is my table schema,

mysql desc location;
+---+--+--+-+-++
| Field | Type | Null | Key | Default | Extra   
   |
+---+--+--+-+-++
| id    | int(10) unsigned | NO   | PRI | NULL    | 
auto_increment |
| username  | char(64) | NO   | MUL | | 
   |
| domain    | char(64) | YES  | | NULL    | 
   |
| contact   | char(255)    | NO   | | | 
   |
| received  | char(128)    | YES  | | NULL    | 
   |
| path  | char(128)    | YES  | | NULL    | 
   |
| expires   | datetime | NO   | | 2020-05-28 21:32:15 | 
   |
| q | float(10,2)  | NO   | | 1.00    | 
   |
| callid    | char(255)    | NO   | | Default-Call-ID | 
   |
| cseq  | int(11)  | NO   | | 13  | 
   |
| last_modified | datetime | NO   | | 1900-01-01 00:00:01 | 
   |
| flags | int(11)  | NO   | | 0   | 
   |
| cflags    | int(11)  | NO   | | 0   | 
   |
| user_agent    | char(255)    | NO   | | | 
   |
| socket    | char(64) | YES  | | NULL    | 
   |
| methods   | int(11)  | YES  | | NULL    | 
   |
| sip_instance  | char(255)    | YES  | | NULL    | 
   |
| attr  | char(255)    | YES  | | NULL    | 
   |
+---+--+--+-+-++


attr holds NULL values for all entries.

do I have to run below in gdb after running bt full right ?

this is what i got

(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info (contact=0x7fffe0246180, 
vals=0x7f648287a260) at udomain.c:306
306    in udomain.c
(gdb) p (vals+6)-val.string_val
$2 = 0x0
(gdb) 


-without running bt full - just in case :)
(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info (contact=0x7fffe0246180, 
vals=0x7f648287a260) at udomain.c:306
306    udomain.c: No such file or directory.
(gdb) p (vals+6)-val.string_val
$1 = 0x0




On Thursday, 5 June 2014, 17:07, Bogdan-Andrei Iancu bog...@opensips.org 
wrote:
 


Thanks for the backtrace. In DB, what do you have for the attr value ? NULL 
or an empty string ?

In gdb, could you do:
    f 1
    p (vals+6)-val.string_val

Thanks,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 05.06.2014 06:15, Pasan Meemaduma wrote:

oops sorry I forgot opensips-dbg :) bt reattached.


I have change some sensitive values with 'x' as below, hope it wont affect u r 
investigations


    contact = {s = 0xf91eab sip:xxx...@xxx.xxx.xxx.xx, len = 29}




On Thursday, 5 June 2014, 8:34, Pasan Meemaduma pasan...@ymail.com wrote:
 


Hi Bogdan,


I double checked the schema and it is correct. btw doc needs fixing its 
missing attr column which is needed by 1.10 for location table otherwise I'll 
get below error.


Jun  5 12:57:26  x/usr/sbin/opensips[30176]: 
CRITICAL:db_mysql:wrapper_single_mysql_real_query: driver error (1054): 
Unknown column 'attr' in 'field list'
Jun  5 12:57:26 x /usr/sbin/opensips[30177]:
DBG:core:db_do_init: connection 0x7f4dc04c1c28
inserted in pool as 0x7f4dc04c1d30
Jun  5 12:57:26 x /usr/sbin/opensips[30176]:
ERROR:core:db_do_query: error while submitting
query - [select

username,contact,expires,q,callid,cseq,flags,cflags,user_agent,received,path,socket,methods,last_modified,sip_instance,attr
from location ]
Jun  5 12:57:26 anacardium3backup
/usr/sbin/opensips[30176]:
ERROR:usrloc:preload_udomain: db_query (1)
failed


:)



I got the backtrace as you requested , It doesn't seems right to me.  does it 
make any sense ? or did I miss something getting it ?



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips crash with location data

[Pasan Meemaduma]

Hi Bogdan,

I just found that I have got the key constraint wrong. Will that be the issue ?

| location | CREATE TABLE `location` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `username` char(64) NOT NULL DEFAULT '',
  `domain` char(64) DEFAULT NULL,
  `contact` char(255) NOT NULL DEFAULT '',
  `received` char(128) DEFAULT NULL,
  `path` char(128) DEFAULT NULL,
  `expires` datetime NOT NULL DEFAULT '2020-05-28 21:32:15',
  `q` float(10,2) NOT NULL DEFAULT '1.00',
  `callid` char(255) NOT NULL DEFAULT 'Default-Call-ID',
  `cseq` int(11) NOT NULL DEFAULT '13',
  `last_modified` datetime NOT NULL DEFAULT '1900-01-01 00:00:01',
  `flags` int(11) NOT NULL DEFAULT '0',
  `cflags` int(11) NOT NULL DEFAULT '0',
  `user_agent` char(255) NOT NULL DEFAULT '',
  `socket` char(64) DEFAULT NULL,
  `methods` int(11) DEFAULT NULL,
  `sip_instance` char(255) DEFAULT NULL,
  `attr` char(255) DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `account_contact_idx` (`username`,`domain`,`contact`)
) ENGINE=MyISAM AUTO_INCREMENT=25375081 DEFAULT CHARSET=latin1 |


account_contact_idx is missing callid column. Will this has any relation to 
crash ?



On Friday, 6 June 2014, 8:48, Pasan Meemaduma pasan...@ymail.com wrote:
 


Hi Bogdan,

Thanks for the reply. I created the table using normal schema it looks fine to 
me. I was refering to the old url you gave me. There in that table attr was 
missing :)


this is the url missing attr in location table
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN7254  


below is my table schema,

mysql desc location;
+---+--+--+-+-++
| Field | Type | Null | Key | Default | Extra   
   |
+---+--+--+-+-++
| id    | int(10) unsigned | NO   | PRI | NULL    | 
auto_increment |
|
 username  | char(64) | NO   | MUL | |  
  |
| domain    | char(64) | YES  | | NULL    | 
   |
| contact   | char(255)    | NO   |
 | |    |
| received  | char(128)    | YES  | | NULL    | 
   |
| path  | char(128)    | YES  | | NULL    | 
   |
|
 expires   | datetime | NO   | | 2020-05-28 21:32:15 |  
  |
| q | float(10,2)  | NO   | | 1.00    | 
   |
| callid    | char(255)    | NO   | | Default-Call-ID | 
   |
|
 cseq  | int(11)  | NO   | | 13  |  
  |
| last_modified | datetime | NO   | | 1900-01-01 00:00:01 | 
   |
| flags | int(11)  | NO   | | 0  
 |    |
| cflags    | int(11)  | NO   | | 0   | 
   |
| user_agent    | char(255)    | NO   | | | 
   |
| socket    |
 char(64) | YES  | | NULL    |    |
| methods   | int(11)  | YES  | | NULL    | 
   |
| sip_instance  | char(255)    | YES  | | NULL   
 |    |
| attr  | char(255)    | YES  | | NULL    | 
   |
+---+--+--+-+-++


attr holds NULL values for all entries.

do I have to run below in gdb after running bt full right ?

this is what i got

(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info
 (contact=0x7fffe0246180, vals=0x7f648287a260) at udomain.c:306
306    in udomain.c
(gdb) p (vals+6)-val.string_val
$2 = 0x0
(gdb) 


-without running bt full - just in case :)
(gdb) f 1
#1  0x7f64823a60a2 in dbrow2info (contact=0x7fffe0246180, 
vals=0x7f648287a260) at udomain.c:306
306    udomain.c: No such file or directory.
(gdb) p (vals+6)-val.string_val
$1 = 0x0




On Thursday, 5 June 2014, 17:07, Bogdan-Andrei Iancu bog...@opensips.org 
wrote:
 


Thanks for the backtrace. In DB, what do you have for the attr value ? NULL 
or an empty string ?

In gdb, could you do:
    f 1
    p (vals+6)-val.string_val

Thanks,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 05.06.2014 06:15, Pasan Meemaduma wrote:

oops sorry I forgot opensips-dbg :) bt reattached.


I have change some sensitive values with 'x' as below, hope it wont affect u r 
investigations


    contact = {s = 0xf91eab sip:xxx...@xxx.xxx.xxx.xx, len = 29}




On Thursday, 5 June 2014, 8:34, Pasan Meemaduma pasan...@ymail.com wrote:
 


Hi Bogdan,


I double checked the schema and it is correct. btw doc needs fixing its 
missing attr column which is needed by 1.10 for location table otherwise I'll 
get below error.

Re: [OpenSIPS-Users] opensips crash with location data

[Bogdan-Andrei Iancu]

Hi Pasan,

Please be sure you are using the DB schema for 1.11 (see 
http://www.opensips.org/Documentation/Install-DBSchema-1-10#AEN7254 ) - 
check the DB types and the content.


Also, follow this tutorial 
http://www.opensips.org/Documentation/TroubleShooting-Crash in order to 
extract and post here the backtrace of your crash.


Regards,

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

On 03.06.2014 06:34, Pasan Meemaduma wrote:

Hi Guys,

I recently migrate a opensips 1.5.3 server to a 1.10.1. Everything 
went fine expect I couldn't bring up opensips with old location data 
it crashes everytime there's data in location table, I have even fix 
the column count before starting opensips. when I delete all records 
from location table and then start opensips it works fine.


So now everytime I have to restart opensips I have to delete location 
table entries. Could you please check if this a bug, I have attach the 
debug trace here.


According to the debug log it gets a segfault while parsing location data.

CPU 2.3 GHz x 2
OS x64 bit debian 7.5

ii opensips 1.10.1-1~1 amd64very 
fast and configurable SIP server
ii  opensips-carrierroute-module 1.10.1-1~1
amd64Carrierroute module for OpenSIPS
ii  opensips-memcached-module 1.10.1-1~1amd64
Interface module to interact with a memcached server
ii  opensips-mysql-module 1.10.1-1~1amd64MySQL 
database connectivity module for OpenSIPS



Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
STRING [xx)]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
STRING [udp:xxx:5060]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
DATETIME [2014-06-01 01:14:14]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
STRING []
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
STRING [sip:xxx@xxx:5060]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
DATETIME [2014-06-01 01:16:40]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
DOUBLE [-1.00]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
STRING [77baea9e4abc04810fc1992d56c7a2f4@xxx]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting INT 
[88543]

Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting INT [0]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting INT [0]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
STRING [FPBX-2.11.0(11.5.1)]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
STRING [udp::5060]
Jun  3 12:25:32 [6982] DBG:db_mysql:db_mysql_str2val: converting 
DATETIME [2014-06-01 01:14:40]
Jun  3 12:25:32 [6982] DBG:usrloc:preload_udomain: loading records - 
cycle [1]
Jun  3 12:25:32 [6977] DBG:core:wait_status_code: read code 0 ? rc = 
0, errno=Success
Jun  3 12:25:32 [6977] INFO:core:daemonize: pre-daemon process exiting 
with -1

 already running.
Jun  3 12:25:32 [6979] DBG:core:handle_sigs: status = 11
Jun  3 12:25:32 [6979] INFO:core:handle_sigs: child process 6982 
exited by a signal 11

Jun  3 12:25:32 [6979] INFO:core:handle_sigs: core was not generated
Jun  3 12:25:32 [6979] INFO:core:handle_sigs: terminating due to SIGCHLD
Jun  3 12:25:32 [6995] INFO:core:sig_usr: signal 15 received
Jun  3 12:25:32 [6991] INFO:core:sig_usr: signal 15 received
Jun  3 12:25:32 [6996] INFO:core:sig_usr: signal 15 received
Jun  3 12:25:32 [6988] INFO:core:sig_usr: signal 15 received
Jun  3 12:25:32 [6994] INFO:core:sig_usr: signal 15 received
Jun  3 12:25:32 [6984] INFO:core:sig_usr: signal 15 received

Expecting an advice on this.

Thanks.

Pasan.


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users