-
Notifications
You must be signed in to change notification settings - Fork 571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CRASH] Crash in proto_tcp #2291
Comments
Another similar one:
|
Another one sudo gdb opensips core.26907.opensips.1603177037 GNU gdb (Debian 8.2.1-2+b3) 8.2.1
|
The last two core dumps are generated by an |
We only have logs for maximum 10 days :-( But I have a more recent one, I come back with the logs for it. |
Corespondent Logs
|
logs
|
New BT
Logs
|
|
|
|
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
@adigeo , I did some cleanup here, I removed all the backtraces showing shutdown crashes, as not relevant (traces showing the |
Now, 90% of the crashes are triggered from an abort in |
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
Marking as closed due to lack of progress for more than 30 days. If this issue is still relevant, please re-open it with additional details. |
OpenSIPS version you are running
[New LWP 18532]
[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/sbin/opensips -w /run/opensips -P opensips.pid -a F_MALLOC_DBG -m 512'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007f400a752535 in __GI_abort () at abort.c:79
#2 0x000056033c94787e in build_res_buf_from_sip_res (msg=msg@entry=0x560342cb8600, returned_len=returned_len@entry=0x7fff2ed27664,
sock=, flags=flags@entry=0) at msg_translator.c:2419
#3 0x00007f3fe9688a1d in relay_reply (t=0x7f3fec518c00, p_msg=, branch=0, msg_status=200,
cancel_bitmap=0x7fff2ed27754) at t_reply.c:1282
#4 0x00007f3fe968af9d in reply_received (p_msg=0x560342cb8600) at t_reply.c:1647
#5 0x000056033c91dad8 in forward_reply (msg=msg@entry=0x560342cb8600) at forward.c:499
#6 0x000056033c9066c7 in receive_msg (
buf=0x56033cc72ac0 <tcp_current_req> "SIP/2.0 200 OK\r\nVia: SIP/2.0/TCP 81.23.228.180:5060;branch=z9hG4bK0bed.86362ac.0\r\nVia: SIP/2.0/UDP 10.0.1.115:33503;received=95.238.189.100;rport=61791;branch=z9hG4bKPj05a40413-4fc5-4a98-ba0e-9a3228df"...,
len=, len@entry=2205, rcv_info=rcv_info@entry=0x7fff2ed279c0, existing_context=existing_context@entry=0x0,
msg_flags=msg_flags@entry=0) at receive.c:266
#7 0x000056033ca7aba5 in tcp_handle_req (_max_msg_chunks=, con=0x7f3fee2e4100, req=0x56033cc72ac0 <tcp_current_req>)
at net/proto_tcp/tcp_common.h:411
#8 tcp_read_req (con=, bytes_read=0x7fff2ed27a80) at net/proto_tcp/proto_tcp.c:1197
#9 0x000056033ca5ac7a in handle_io (fm=, idx=idx@entry=16, event_type=event_type@entry=1) at net/net_tcp_proc.c:312
#10 0x000056033ca5cfb1 in io_wait_loop_epoll (h=, t=, repeat=)
at net/../io_wait_loop.h:305
#11 tcp_worker_proc_loop () at net/net_tcp_proc.c:422
#12 0x000056033ca6d2cb in tcp_start_processes (chd_rank=chd_rank@entry=0x56033cc4c5c8 <chd_rank>,
startup_done=startup_done@entry=0x0) at net/net_tcp.c:2088
#13 0x000056033c8eb813 in main_loop () at main.c:810
#14 main (argc=, argv=) at main.c:1491
(gdb)
The text was updated successfully, but these errors were encountered: