Re: [Kamailio-Users] Kamailio Blocking

2010-04-09 Thread Daniel-Constantin Mierla

Hello,


On 4/9/10 6:54 AM, dotnetdub wrote:

Hello List,

I have been running a very stable Kamailio 1.4 install for over a year 
now with no downtime. From time to time I get a message from the OS 
telling me that task kamailio: blocked for more than 120 seconds 
and a dump into syslog.


I recently setup Kamailio 3.01 and it's been running for around 3 
weeks now. Purely testing at the moment, there is only 1 SIP 
registration and almost no activity most of the time.
the messages refer to mi_datagram processes. These processes listen on a 
unixsocket as I could get from the trace, and if there is no mi command, 
they stay blocked.


I haven't seen such messages so far, what is your OS?

They should be harmless, anyhow these processes don't handle sip 
messages, just mi commands send via unixsocket.


Cheers,
Daniel



I was checking dmesg and:

[269844.208011] INFO: task kamailio:28504 blocked for more than 120 
seconds.
[269844.208093] echo 0  /proc/sys/kernel/hung_task_timeout_secs 
disables this message.

[269844.208178] kamailio  D f6d77bf8 0 28504  28484
[269844.208180]f771e140 0082 0002 f6d77bf8 f7091390 
f771e2cc c4019020 
[269844.208184] 011615c9 f7091398 0282  
  
[269844.208188]f5cba384 f5cba38c f5cba388 f771e140 c02c91ec 
f6969d68 f5cba38c f771e140

[269844.208191] Call Trace:
[269844.208203]  [c02c91ec] __mutex_lock_slowpath+0x50/0x7b
[269844.208208]  [c02c9082] mutex_lock+0xa/0xb
[269844.208210]  [c02b7d4d] unix_dgram_recvmsg+0x3e/0x231
[269844.208214]  [c0161beb] get_page_from_freelist+0xc1/0x3e9
[269844.208218]  [c0161045] __rmqueue_smallest+0x83/0xe3
[269844.208221]  [c025f771] sock_recvmsg+0xde/0xf9
[269844.208226]  [c01387b0] autoremove_wake_function+0x0/0x2d
[269844.208231]  [c01620e9] __alloc_pages_internal+0xb5/0x34e
[269844.208236]  [c0260595] sys_recvfrom+0xb4/0x116
[269844.208239]  [c011af13] do_page_fault+0x0/0x8f9
[269844.208242]  [c0108540] do_notify_resume+0x5f8/0x649
[269844.208247]  [c011b3c5] do_page_fault+0x4b2/0x8f9
[269844.208250]  [c0260a48] sys_socketcall+0x135/0x19e
[269844.208254]  [c0108853] sysenter_past_esp+0x78/0xb1
[269844.208257]  [c02c] xenfb_probe+0xd1/0x35b
[269844.208261]  ===
[269844.208262] INFO: task kamailio:28506 blocked for more than 120 
seconds.
[269844.208314] echo 0  /proc/sys/kernel/hung_task_timeout_secs 
disables this message.

[269844.208395] kamailio  D d0e00947 0 28506  28484
[269844.208397]f77f8e60 0082 0002 d0e00947 4292 
f77f8fec c4024020 0001
[269844.208401] 0001 0002  f7091398 
0001 0001 c01211f2
[269844.208404]f5cba384 f5cba38c f5cba388 f77f8e60 c02c91ec 
f5cba38c f60add68 f77f8e60

[269844.208408] Call Trace:
[269844.208410]  [c01211f2] __wake_up_sync+0x2a/0x3e
[269844.208413]  [c02c91ec] __mutex_lock_slowpath+0x50/0x7b
[269844.208416]  [c02c9082] mutex_lock+0xa/0xb
[269844.208418]  [c02b7d4d] unix_dgram_recvmsg+0x3e/0x231
[269844.208421]  [c0161beb] get_page_from_freelist+0xc1/0x3e9
[269844.208424]  [c0161045] __rmqueue_smallest+0x83/0xe3
[269844.208427]  [c025f771] sock_recvmsg+0xde/0xf9
[269844.208431]  [c01387b0] autoremove_wake_function+0x0/0x2d
[269844.208435]  [c01620e9] __alloc_pages_internal+0xb5/0x34e
[269844.208440]  [c0260595] sys_recvfrom+0xb4/0x116
[269844.208444]  [c0180d0d] cp_new_stat64+0xfc/0x10e
[269844.208449]  [c011b3c5] do_page_fault+0x4b2/0x8f9
[269844.208452]  [c0260a48] sys_socketcall+0x135/0x19e
[269844.208456]  [c0108853] sysenter_past_esp+0x78/0xb1
[269844.208459]  [c02c] xenfb_probe+0xd1/0x35b
[269844.208462]  ===
[274198.229285] INFO: task kamailio:28504 blocked for more than 120 
seconds.
[274198.229340] echo 0  /proc/sys/kernel/hung_task_timeout_secs 
disables this message.

[274198.229422] kamailio  D f6d77bf8 0 28504  28484
[274198.229425]f771e140 0082 0002 f6d77bf8 f7091390 
f771e2cc c4019020 
[274198.229429] 011615c9 f7091398 0282  
  
[274198.229432]f5cba384 f5cba38c f5cba388 f771e140 c02c91ec 
f6969d68 f5cba38c f771e140

[274198.229436] Call Trace:
[274198.229447]  [c02c91ec] __mutex_lock_slowpath+0x50/0x7b
[274198.229453]  [c02c9082] mutex_lock+0xa/0xb
[274198.229455]  [c02b7d4d] unix_dgram_recvmsg+0x3e/0x231
[274198.229459]  [c0161beb] get_page_from_freelist+0xc1/0x3e9
[274198.229463]  [c0161045] __rmqueue_smallest+0x83/0xe3
[274198.229466]  [c025f771] sock_recvmsg+0xde/0xf9
[274198.229471]  [c01387b0] autoremove_wake_function+0x0/0x2d
[274198.229476]  [c01620e9] __alloc_pages_internal+0xb5/0x34e
[274198.229481]  [c0260595] sys_recvfrom+0xb4/0x116
[274198.229484]  [c011af13] do_page_fault+0x0/0x8f9
[274198.229487]  [c0108540] do_notify_resume+0x5f8/0x649
[274198.229492]  [c011b3c5] do_page_fault+0x4b2/0x8f9
[274198.229495]  [c0260a48] sys_socketcall+0x135/0x19e
[274198.229499]  

Re: [Kamailio-Users] Kamailio Blocking

2010-04-09 Thread Daniel-Constantin Mierla

Hello,

On 4/9/10 10:58 AM, Henning Westerholt wrote:

On Friday 09 April 2010, Daniel-Constantin Mierla wrote:
   

I have been running a very stable Kamailio 1.4 install for over a year
now with no downtime. From time to time I get a message from the OS
telling me that task kamailio: blocked for more than 120 seconds
and a dump into syslog.
   

[..]
the messages refer to mi_datagram processes. These processes listen on a
unixsocket as I could get from the trace, and if there is no mi command,
they stay blocked.

I haven't seen such messages so far, what is your OS?
 

Hi Daniel,

this is a more or less standard behaviour in the linux kernel available since
2.6.26 or so, if i remember correctly.

ok, good to know.


  I think that i saw it a few times on
some systems as well, but so far don't remember the cause.
   


Maybe google will reveal something, I will check once I get some spare 
time...


Thanks,
Daniel

--
Daniel-Constantin Mierla * http://www.asipto.com/ * 
http://twitter.com/miconda * 
http://www.linkedin.com/in/danielconstantinmierla


___
Kamailio (OpenSER) - Users mailing list
Users@lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users


Re: [Kamailio-Users] Kamailio Blocking

2010-04-09 Thread Klaus Darilion



Am 09.04.2010 06:54, schrieb dotnetdub:

kamctl ps:

Process::  ID=14 PID=28504 Type=MI DATAGRAM
Process::  ID=15 PID=28505 Type=MI DATAGRAM
Process::  ID=16 PID=28506 Type=MI DATAGRAM


Is it possible to have several MI listeners? I always have only one.

regards
klaus

___
Kamailio (OpenSER) - Users mailing list
Users@lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users


Re: [Kamailio-Users] Kamailio Blocking

2010-04-09 Thread Daniel-Constantin Mierla



On 4/9/10 12:07 PM, Klaus Darilion wrote:



Am 09.04.2010 06:54, schrieb dotnetdub:

kamctl ps:

Process::  ID=14 PID=28504 Type=MI DATAGRAM
Process::  ID=15 PID=28505 Type=MI DATAGRAM
Process::  ID=16 PID=28506 Type=MI DATAGRAM


Is it possible to have several MI listeners? I always have only one.

for mi_datagram it is possible:
http://kamailio.org/docs/modules/stable/modules_k/mi_datagram.html#id2583658

Cheers.
Daniel

--
Daniel-Constantin Mierla * http://www.asipto.com/ * 
http://twitter.com/miconda * 
http://www.linkedin.com/in/danielconstantinmierla


___
Kamailio (OpenSER) - Users mailing list
Users@lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users