THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#430 - bogus core statistics?
User who did this - Juha Heinanen (jh)
----------
regarding core:bad_URIs_rcvd, i changed some DBGs in parser to INFOs and got this:
May 19 20:59:43 siika /usr/sbin/sip-proxy[22053]: INFO: <core> [parser/parse_uri.c:1272]: parse_uri(): parse_uri: uri too short: <> (0)
on this incoming notify:
NOTIFY sip:jh-0xa66180@192.98.102.30:5066;alias=192.98.102.30~38276~2;transport=tcp SIP/2.0.
Via: SIP/2.0/TCP 192.98.102.30:5080;branch=z9hG4bKbf4c.f63f0680000000000000000000000000.0.
To: <sip:jh@test.tutpro.com>;tag=92a902cb1206b577.
From: <sip:jh@test.tutpro.com>;tag=cd79fb8f5c18efbd1a0962eab2c7a83a-c767.
CSeq: 2 NOTIFY.
Call-ID: bc1797dbe425d0ef.
Route: <sip:127.0.0.1:5070;transport=tcp;r2=on;lr>, <sip:192.98.102.30;transport=tcp;r2=on;lr>.
Content-Length: 48.
User-Agent: OpenXg Presence/XCAP Server (4.2.0-dev3 (x86_64/linux)).
Max-Forwards: 70.
Event: message-summary.
Contact: <sip:192.98.102.30:5080;transport=tcp>.
Subscription-State: active;expires=600.
Content-Type: application/simple-message-summary.
.
Messages-Waiting: no.
Voice-Message: 0/0 (0/0).
i don't see any uri missing. also, proxy forwards the request fine.
any ideas why parser is trying to parse empty uri and, as result, increments core:bad_URIs_rcvd value?
-- juha
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=430#comment1470
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi,
I decided to start a new kamailio install with the 4.1 debian packages.
Everything seems to have gone as expected, and kamailio starts normally.
However, as soon as I try to register (MySQL), Kamailio crashes as can be
seen by the logs.
I have tls enabled, as well as rtpengine (although could someone please
confirm that we are supposed to continue loading "rtpproxy-ng.so"? I didn't
find any new module named rtpengine.so after compiling and installing its
debian packages, so I presume we are to keep using rtpproxy-ng.so), and
have created the DB tables, so not sure what's causing it to crash. I can
get a core dump if needed.
Any clues?
Thanks,
Peter
May 19 16:37:04 vmhost /usr/sbin/kamailio[18513]: ALERT: <core>
[main.c:775]: handle_sigs(): child process 18520 exited by a signal 11
May 19 16:37:04 vmhost /usr/sbin/kamailio[18513]: ALERT: <core>
[main.c:778]: handle_sigs(): core was not generated
May 19 16:37:04 vmhost /usr/sbin/kamailio[18513]: INFO: <core>
[main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD
May 19 16:37:04 vmhost kernel: [189666.602743] kamailio[18520] general
protection ip:536104 sp:7fff87fe0190 error:0 in
kamailio[400000+27a000]
May 19 16:37:04 vmhost /usr/sbin/kamailio[18519]: INFO: <core>
[main.c:841]: sig_usr(): INFO: signal 15 received
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#430 - bogus core statistics?
User who did this - Juha Heinanen (jh)
----------
.. and also by publish messages.
how to fix that as well as core:unsupported_methods for xmlrpc requests?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=430#comment1469
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#430 - bogus core statistics?
User who did this - Juha Heinanen (jh)
----------
looks like core:bad_URIs_rcvd in incremented either by subscribe or notify messages.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=430#comment1468
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#430 - bogus core statistics?
User who did this - Ovidiu Sas (osas)
----------
In my test setup I have core:bad_URIs_rcvd set to 0.
Please test with a different UA.
This might be something related to baresip ua.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=430#comment1467
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#430 - bogus core statistics?
User who did this - Juha Heinanen (jh)
----------
after restart i'm seeing core:bad_URIs_rcvd increasing every time i restart baresip ua. so it still looks like a bug to me.
what comes to core:unsupported_methods, increase of that value is indeed due to xmlrpc requests, which, of course, are not unsupported requests.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=430#comment1466
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#430 - bogus core statistics?
User who did this - Ovidiu Sas (osas)
----------
Please retrieve the statistics using kamcmd and check the values again (after a restart).
IIRC, you reported that the core:unsupported_methods stat is increased for HTTP requests.
I had the same issue while I was testing using xhttp_rpc interface.
If you query the stats using xmlrpc, then most likly the core:unsupported_methods stat will be increased.
We need to determine if all the bogus stats are related to HTTP or nor.
Thanks,
Ovidiu
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=430#comment1465
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Juha Heinanen (jh)
Attached to Project - sip-router
Summary - bogus core statistics?
Task Type - Bug Report
Category - Core
Status - New
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - when i query tmx core stats, i get:
# sip-proxy_ctl stats.get_statistics core:
core:bad_URIs_rcvd = 14
core:bad_msg_hdr = 0
core:drop_replies = 0
core:drop_requests = 0
core:err_replies = 0
core:err_requests = 0
core:fwd_replies = 0
core:fwd_requests = 2
core:rcv_replies = 32
core:rcv_requests = 149
core:unsupported_methods = 35
i suspect that both core:bad_URIs_rcvd and core:unsupported_methods values are incorrect. since i started the proxy, i have only used baresip uas that hardly generate any bad uris or unsupported methods.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=430
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
