I am troubleshooting intermittent latency on a server, several processes
will report slow action at the same time every now and then,
something odd it that some of the actions are most likely not using any
mutexes, I can not imagine how they can end up blocking unless the process
is actually suspended by the OS, however the CPU usage and load average is
quite low on this server.
Is there any reason why assigning to a PKG var could be delayed 3 seconds.
2019-11-13T21:58:04.018631614Z 23(42) WARNING: <core> [core/action.c:1586]:
run_actions(): alert - action [corefunc (16)] cfg
[/etc/kamailio/kamailio.cfg:115] took too long [2579486 us]
$var(reply) = 0; // I wonder how this can endup blocking ?
2019-11-13T21:58:04.018748710Z 42(61) WARNING: <core> [core/action.c:1586]:
run_actions(): alert - action [corefunc (16)] cfg
[/etc/kamailio/kamailio.cfg:221] took too long [2222010 us]
} // Samething here, simply exiting a scope
2019-11-13T21:58:04.015675095Z 11(30) WARNING: <core> [core/action.c:1586]:
run_actions(): alert - action [t_relay_cancel (24)] cfg
[/etc/kamailio/kamailio.cfg:86] took too long [2588818 us]
} if (!t_relay_cancel()) { // Indeed a t_relay_cancel
2019-11-13T21:58:04.018647988Z 26(45) WARNING: <core> [core/action.c:1586]:
run_actions(): alert - action [t_relay (24)] cfg
[/etc/kamailio/kamailio.cfg:289] took too long [2739366 us]
t_relay(); // Indeed a t_relay
2019-11-13T21:58:04.018651243Z 15(34) WARNING: <core> [core/action.c:1586]:
run_actions(): alert - action [sl_send_reply (26)] cfg
[/etc/kamailio/kamailio.cfg:112] took too long [2587812 us]
sl_send_reply("100", "Trying"); // Indeed a sl_send_reply
Not sure which mailing list is best for this question
Regards
Julien
I am trying to compile and load kamailio 5.2.4 on centos 7.5.
I am getting below errors whenever I start kamailio . I have the latest openssl and openssl-devel packages installed on my centos . Not sure what other dependencies .
Not starting Kamailio SIP Server: invalid configuration fil[FAILED] [FAILED]0(23235) ERROR: <core> [core/sr_module.c:498]: load_module(): could not open module </usr/local/lib64/kamailio/modules/db_mysql.so>: /usr/local/lib64/kamailio/modules/db_mysql.so: undefined symbol: SSL_get_error 0(23235) CRITICAL: <core> [core/cfg.y:3508]: yyerror_at(): parse error in config file //usr/local/etc/kamailio/kamailio.cfg, line 229, column 12-24: failed to load module ERROR: bad config file (1 errors) 0(23235) INFO: <core[FAILED]sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized [FAILED]
Hello,
on Thursday and Friday this week over a dozen of Kamailio developers
will be in Dusseldorf for the annual coding meeting, so we thought of
doing an online meeting via some video conferencing bridge, with IRC as
a backup chatting channel, to allow also other community members to join
remotely and discuss the development plans for short/medium term.
It is more or less what we used to do during the past IRC devel
meetings, but to make the discussions go faster and shorter the meeting,
so people in Dusseldorf spend more time coding, this time we will try
video conferencing. Very likely we will use Jitsi Meet, so anyone that
wants to join should be prepared with a WebRTC capable web browser (all
major ones support it) -- link and details how to join will be provided
short before the meeting starts, right now the plan is to do it on
Thursday, Nov 14, at 15:00UTC/London (16:00Berlin-Paris, 10:00New York).
If someone wants to address questions but doesn't have the possibility
to join the video conf bridge, then join the IRC #kamailio channel on
freenode.net and post your question there during the meeting. The IRC
channel will be monitored and used for text chatting whenever needed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Hello,
Kamailio SIP Server v5.3.1 stable release is out.
This is a maintenance release of the latest stable branch, 5.3, that
includes fixes since the release of v5.3.1. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.3.x. Deployments running previous v5.3.x
versions are strongly recommended to be upgraded to v5.3.1.
For more details about version 5.3.1 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2019/11/kamailio-v5-3-1-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Hello,
the plan right now is to release v5.3.1 during the next Kamailio
Developers Meeting, if we succeed to coordinate on site, therefore
expect it to happen next week during Nov 14-15. Besides just doing this
specific release, to goal is to try to build a more automatic process
for releases, document how is done, etc... updates about the results
will follow after the event.
Anyhow, for now the usual the pre-release notice: if anyone is aware of
some issue that is not yet reported, do it asap in order to give it a
chance to be analyzed and fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Hi!
I just made a simple test performance between native script and kemi/lua
with the event_route[core:msg-received] callback.
# lua script children=1 cpu.process=100%
function ksr_core_received()
exit;
end
# native script children=1 cpu.process=70%
event_route[core:msg-received] {
exit;
}
# tested with udp 5060, 1000 Mbits/sec
iperf -c 127.0.0.1 -p 5060 -u -b1000m
I don't know if it's normal and what we should expect from kemi, but I
would like to share this with you. Maybe someone could confirm the
performance difference.
Have a good day !
Hi,
looking at the documentation and the code, I couldn't answer myself.
- does kamailio use one lua interpreter per fork ?
- about the safety, I just made a bad lua module in c, to force a
segmentation fault in the module.
I would expect kamailio to protect itself from the crash, but kamailio
restarted.