Hello,
On 1/28/10 3:34 PM, Aymeric Moizard wrote:
some other answer below:
On Thu, 28 Jan 2010, Daniel-Constantin Mierla wrote:
I am cc-ing sr-dev, since tcp code is from ser and Andrei may have
more insights...
On 1/28/10 2:41 PM, Aymeric Moizard wrote:
On Thu, 28 Jan 2010, Henning We
some other answer below:
On Thu, 28 Jan 2010, Daniel-Constantin Mierla wrote:
I am cc-ing sr-dev, since tcp code is from ser and Andrei may have more
insights...
On 1/28/10 2:41 PM, Aymeric Moizard wrote:
On Thu, 28 Jan 2010, Henning Westerholt wrote:
On Thursday 28 January 2010, Aymer
Again additionnal information:
Doing new capture: after the failure, I can see that a TCP
connection is made with second SRV record: sip.mobipouce.com
(91.199.234.46)
I got:
SYN ACK -> sip.mobipouce.com
ACK <- sip.mobipouce.com
PSH, ACK <- sip.mobipouce.com
ACK -> sip.mobipouce.com
I'm guess
I am cc-ing sr-dev, since tcp code is from ser and Andrei may have more
insights...
On 1/28/10 2:41 PM, Aymeric Moizard wrote:
On Thu, 28 Jan 2010, Henning Westerholt wrote:
On Thursday 28 January 2010, Aymeric Moizard wrote:
here is the backtrace I have. unfortunatly without debug symbol
On Thu, 28 Jan 2010, Henning Westerholt wrote:
On Thursday 28 January 2010, Aymeric Moizard wrote:
here is the backtrace I have. unfortunatly without debug symbol!
I found the same for many of the kamailio process. "sched_yield"
is pending for ever. My system is a debian/etch.
#0 0xe424
On Thursday 28 January 2010, Aymeric Moizard wrote:
> here is the backtrace I have. unfortunatly without debug symbol!
> I found the same for many of the kamailio process. "sched_yield"
> is pending for ever. My system is a debian/etch.
>
> #0 0xe424 in __kernel_vsyscall ()
> #1 0xb7cef4ac i
Hi again,
here is the backtrace I have. unfortunatly without debug symbol!
I found the same for many of the kamailio process. "sched_yield"
is pending for ever. My system is a debian/etch.
#0 0xe424 in __kernel_vsyscall ()
#1 0xb7cef4ac in sched_yield () from /lib/tls/i686/cmov/libc.so.6
On Thu, 28 Jan 2010, Daniel-Constantin Mierla wrote:
Hello,
On 1/28/10 11:18 AM, Aymeric Moizard wrote:
Got some more info:
The UDP deadlock always seems to happen after a SUBSCRIBE
is sent (in UDP) to mobipouce.com:
Jan 28 11:00:40 ns26829 /usr/sbin/kamailio[13363]:
ERROR:core:tcp_bloc
Hello,
On 1/28/10 11:18 AM, Aymeric Moizard wrote:
Got some more info:
The UDP deadlock always seems to happen after a SUBSCRIBE
is sent (in UDP) to mobipouce.com:
Jan 28 11:00:40 ns26829 /usr/sbin/kamailio[13363]:
ERROR:core:tcp_blocking_connect: poll error: flags 18
Jan 28 11:00:40 ns26829
Got some more info:
The UDP deadlock always seems to happen after a SUBSCRIBE
is sent (in UDP) to mobipouce.com:
Jan 28 11:00:40 ns26829 /usr/sbin/kamailio[13363]:
ERROR:core:tcp_blocking_connect: poll error: flags 18
Jan 28 11:00:40 ns26829 /usr/sbin/kamailio[13363]:
ERROR:core:tcp_blocking_
Hi again people!
I'm currently having some trouble with my sip.antisip.com server.
Within the previous 2 or 3 days, kamailio sometimes fall into
some kind of dead lock.
I've been checking my logs while the dead lock happen, and it
seems (although I'm not sure with only the logs) that only UDP
11 matches
Mail list logo
