hello
can you help me ? i really cannt find other ways to solve this. i just
add socket ,then occur so big problem, how i can do this ?___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http:/
On 26/12/13 16:55, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
I looked quickly over the code and it seems that in 4.0 there are some
error cases when an acquired lock is not released.
yes, there was a few error and done goto cases where lock was not
released. hopefully i caught th
i very thanks you to answer my question so quickly. so there are no problem in
my add codes ?___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr
dear : now i just register and unregister ,the kamailio stop ,why?
below is bebug:
DEBUG: [parser/msg_parser.c:629]: parse_msg(): method:
8(3563) DEBUG: [parser/msg_parser.c:631]: parse_msg(): uri:
8(3563) DEBUG: [parser/msg_parser.c:633]: parse_msg(): version:
8(3563) DE
Daniel-Constantin Mierla writes:
> I looked quickly over the code and it seems that in 4.0 there are some
> error cases when an acquired lock is not released.
yes, there was a few error and done goto cases where lock was not
released. hopefully i caught them all.
if i don't see any objections,
On 23/12/13 14:25, Juha Heinanen wrote:
file http://box.tutpro.com/tmp/gdb_kamailio_20131223_145323 contains gdb bt
of all presence server processes when presence server is not responding to
any new requests. looks like several processes are in futexlock.h if that
tells something.
It is a sign
Hello,
On 23/12/13 12:12, Juha Heinanen wrote:
Klaus Darilion writes:
utils/kamctl: new command 'trap'
- useful to get a full bt dump of all kamailio processes
- handy in dead-lock investigatigations
klaus,
thanks for the pointer. i pulled out shell script from it (below).
it would b
Juha Heinanen writes:
> file http://box.tutpro.com/tmp/gdb_kamailio_20131223_145323 contains gdb bt
> of all presence server processes when presence server is not responding to
> any new requests. looks like several processes are in futexlock.h if that
> tells something.
>
> this is with kamaili
file http://box.tutpro.com/tmp/gdb_kamailio_20131223_145323 contains gdb bt
of all presence server processes when presence server is not responding to
any new requests. looks like several processes are in futexlock.h if that
tells something.
this is with kamailio 4.0.
-- juha
__
Klaus Darilion writes:
> utils/kamctl: new command 'trap'
> - useful to get a full bt dump of all kamailio processes
> - handy in dead-lock investigatigations
klaus,
thanks for the pointer. i pulled out shell script from it (below).
it would be still nice to know how kamailio is dispatchin
FYI: In master there is a nice way to get all the BTs:
utils/kamctl: new command 'trap'
- useful to get a full bt dump of all kamailio processes
- handy in dead-lock investigatigations
regards
Klaus
On 20.12.2013 19:06, Daniel-Constantin Mierla wrote:
Hello,
the bt is from custom timer proc
Daniel-Constantin Mierla writes:
> the bt is from custom timer process, which doesn't handle sip requests
> from the network.
ok, that just happened to be the one that according to 'top' used most
cpu time.
> Do a 'kamctl ps' and the select one of the sip workers to grab the back
> with gdb.
Hello,
the bt is from custom timer process, which doesn't handle sip requests
from the network.
Do a 'kamctl ps' and the select one of the sip workers to grab the back
with gdb.
Cheers,
Daniel
On 20/12/13 15:22, Juha Heinanen wrote:
once in a while kamailio 4.0 presence server becomes unr
once in a while kamailio 4.0 presence server becomes unresponsive, i.e.,
does not process any requests. below is bt full of a process that at
that time takes most of the cpu time. rls_notifier_processes is not
set, i.e., it defaults to 1.
does the bt give any clue why kamailio is unresponsive?
14 matches
Mail list logo
