Hi,
We are running Kamailio 3.3.5 as a Registrar service. We wanted to
increase some logging, so we inserted the following lines into our
configuration file:
...
# log failed registration
route[LOG_REG_DENIED]{
xlog("L_ERR","md=REGISTER, s=DENIED, n=$tU,
ct=$sel(contact.uri.hostport), v=$sel(via[1].host)");
}
# log successful registration
route[LOG_REG_SUCCESS]{
xlog("L_ERR","md=REGISTER, s=OK, n=$tU,
ct=$sel(contact.uri.hostport), v=$sel(via[1].host)");
}
...
After about 24 hours Kamailio stopped working properly and the following
ERROR messages started to appear in the log:
ERROR: <core> [lvalue.c:389]: rval expression evaluation failed
(141,18-141,57)
ERROR: <core> [db_row.c:116]: no private memory left
ERROR: db_mysql [km_row.c:58]: could not allocate row
ERROR: db_mysql [km_res.c:188]: error while converting row #0
ERROR: db_mysql [km_res.c:217]: error while converting rows
ERROR: db_mysql [km_dbase.c:191]: error while converting result
ERROR: <core> [db_query.c:134]: error while storing result
ERROR: p_usrloc [ul_db_query.c:108]: could not query table location.
ERROR: p_usrloc [ul_db_query.c:52]: could not query table location error
on id 12, db 1.
ERROR: p_usrloc [ul_db.c:199]: error on id 12, db 1, errors occured: 1,
threshold: 50
ERROR: <core> [db_row.c:116]: no private memory left
ERROR: db_mysql [km_row.c:58]: could not allocate row
ERROR: db_mysql [km_res.c:188]: error while converting row #0
ERROR: db_mysql [km_res.c:217]: error while converting rows
ERROR: db_mysql [km_dbase.c:191]: error while converting result
ERROR: <core> [db_query.c:134]: error while storing result
ERROR: p_usrloc [ul_db_query.c:108]: could not query table location.
ERROR: p_usrloc [ul_db_query.c:52]: could not query table location error
on id 12, db 1.
ERROR: <core> [db_row.c:116]: no private memory left
ERROR: db_mysql [km_row.c:58]: could not allocate row
ERROR: db_mysql [km_res.c:188]: error while converting row #0
ERROR: db_mysql [km_res.c:217]: error while converting rows
ERROR: db_mysql [km_dbase.c:191]: error while converting result
ERROR: <core> [db_query.c:134]: error while storing result
ERROR: p_usrloc [ul_db_query.c:108]: could not query table location.
ERROR: p_usrloc [ul_db_query.c:52]: could not query table location error
on id 12, db 2.
ERROR: p_usrloc [ul_db.c:199]: error on id 12, db 2, errors occured: 0,
threshold: 50
ERROR: <core> [db_row.c:116]: no private memory left
ERROR: db_mysql [km_row.c:58]: could not allocate row
ERROR: db_mysql [km_res.c:188]: error while converting row #0
ERROR: db_mysql [km_res.c:217]: error while converting rows
ERROR: db_mysql [km_dbase.c:191]: error while converting result
ERROR: <core> [db_query.c:134]: error while storing result
ERROR: p_usrloc [ul_db_query.c:108]: could not query table location.
ERROR: p_usrloc [ul_db_query.c:52]: could not query table location error
on id 12, db 2.
ERROR: p_usrloc [udomain.c:433]: db_query failed
ERROR: <core> [msg_translator.c:2089]: ERROR:
build_res_buf_from_sip_req: out of memory ; needs 484
ERROR: sl [sl.c:270]: failed to reply stateful (tm)
ERROR: registrar [reply.c:607]: failed to send 200 OK
ERROR: <core> [msg_translator.c:2089]: ERROR:
build_res_buf_from_sip_req: out of memory ; needs 530
ERROR: sl [sl_funcs.c:371]: ERROR: sl_reply_error used: I'm terribly
sorry, server error occurred (1/SL)
We strongly suppose that this memory issue is somehow caused by the
above mentioned xlog-lines or the usage of the select framework inside
those lines, because if we take out those lines, Kamailio is running
smoothly (Currently running for 6 days now). May it be a possible memory
leak in the select framework?
Some statistics about our Registrar (Interval 24h):
- Number of transactions: Average 500, Maximum 1000
- Number of accepted registrations: Average 7500, Maximum 14500
- Used Memory: Average 9MB, Maximum 15MB
Regards,
Paul
Hi,
I've been experimenting with Msilo in Kamailio 4.1.1 and I noticed some
things seem to be deprecated when looking at old configuration examples
like the one here
http://telephonynetworks.blogspot.pt/2012/08/configuracion-de-kamailio-33-c…
It seems that #!ifdef WITH_MSILO is no longer supported. At least with me
Kamailio doesn't start if I have that in kamailio.cfg. I have to explicitly
load msilo.so and all the related module params without #!ifdef WITH_MSILO
Can someone confirm that this syntax has indeed been deprecated so I don't
spend any more time trying to adapt outdated configuration files to 4.1.1?
Thanks
Hi!
After a year of working with Kamailio on social media we now have around 400 followers on Twitter, over 250 on Facebook, 220 on G+ and a mixture of groups on LInkedIn - from Openser to SIP-router and Kamailio with a pretty large following. G+ have a page with a news flow and a community group for discussions.
I try to publish what's on the Kamailio.org web site as news. In addition, I highlight some features now and then to keep the flow going, regardless of the news flow in the project. We've also worked on and published an article on the IMS functionality on the web site. I think we should work on more of those articles/interviews - like talking about how carrierroute came to existance and how it's used, new modules like mohqueue and the whole webrtc support stuff.
I hope to make some time for that kind of articles that I think adds interest and explains more of what we are doing and how Kamailio can be used. Hopefully we can discuss this at Kamailio World!
If you have ideas, feel free to contact me on or off list. I think we can use the -doc list for these kind of discussions, it's a pretty empty forum right now.
Please don't hesitate to remind me to inform about new functions, events or related stuff in these channels. If you can, inform your friends and followers about these channels to raise interest in Kamailio.
We do get questions on these channels too, I have mostly referred to the mailing list, but if you can help in answering I would be happy.
I have no stats on how many subscriptions we have on the mailing lists or visits on the web site, that would be interesting. (hint, hint ;-) )
Have a great weekend!
/O
G+ https://plus.google.com/u/0/b/114984922071338017631/
Facebook https://www.facebook.com/Kamailio
Twitter @kamailioproject
Hello Devs,
I was going to answer the question below on sr-users about the websocket
module/package.
With the exception of OpenSuse > v12, the websocket module is not built
into any of the RPM distros on the kamailio download pages.
Is this due to the libunistring build-dependancy? Can we update the spec
file to make websockets available in as many distributions as possible?
Regards,
Hugh
-------- Original Message --------
Subject: [SR-Users] websocket.so module not generated
Date: Fri, 14 Feb 2014 22:36:42 +0100
From: Alvaro Urionabarrenetxea Gomez <alvurion(a)gmail.com>
Reply-To: Kamailio (SER) - Users Mailing List
<sr-users(a)lists.sip-router.org>
To: sr-users(a)lists.sip-router.org
Hi.
I have a problem when I'm trying to start with my Kamailio server. I
have an error about not existing "websocket.so" module.
Here is the error:
root@kamailio:# /etc/init.d/kamailio start
** Not starting Kamailio SIP server: invalid configuration file!*
***
** 0 (8327) ERROR: <core> [sr_module.c:587]: load_module(): ERROR:
load_module: could not find module <websocket> in
</usr/local/lib/kamailio/modules/>*
*0(8327) : <core> [cfg.y:3408]: yyerror_at(): parse_error in config file
/usr/local/etc/kamailio/kamailio.cfg, line 318, column 12-25: failed to
load module*
*ERROR: bad config file (1 errors)*
***
And here is the line 318 in kamailio.cfg:
*loadmodule "websocket.so"*
I looked for that module in the correspondent folder but isn't there.
Can anyone upload the websocket.so file to another mirror, MEGA for
example? I tried to generate another time, download another kamailio
versions but the error stills there.
Much apreciated.
Thanks!