@miconda 

That did the trick!

````
(gdb)
(gdb) set $i=0
(gdb) while ($i < *process_count)
 >p pt[$i++]
 >end
$1 = {pid = 9446, unix_sock = -1, idx = -1, desc = "main process - attendant", 
'\000' <repeats 103 times>}
$2 = {pid = 9449, unix_sock = 13, idx = -1,
  desc = "udp receiver child=0 sock=172.31.46.236:5060 (sip.domain.com:5060)", 
'\000' <repeats 61 times>}
$3 = {pid = 9450, unix_sock = 14, idx = -1,
  desc = "udp receiver child=1 sock=172.31.46.236:5060 (sip.domain.com:5060)", 
'\000' <repeats 61 times>}
$4 = {pid = 9451, unix_sock = 15, idx = -1,
  desc = "udp receiver child=2 sock=172.31.46.236:5060 (sip.domain.com:5060)", 
'\000' <repeats 61 times>}
$5 = {pid = 9452, unix_sock = 16, idx = -1,
  desc = "udp receiver child=3 sock=172.31.46.236:5060 (sip.domain.com:5060)", 
'\000' <repeats 61 times>}
$6 = {pid = 9453, unix_sock = 17, idx = -1,
  desc = "udp receiver child=0 sock=172.31.46.236:6050 (sip.domain.com:6050)", 
'\000' <repeats 61 times>}
$7 = {pid = 9454, unix_sock = 18, idx = -1,
  desc = "udp receiver child=1 sock=172.31.46.236:6050 (sip.domain.com:6050)", 
'\000' <repeats 61 times>}
$8 = {pid = 9455, unix_sock = 19, idx = -1,
  desc = "udp receiver child=2 sock=172.31.46.236:6050 (sip.domain.com:6050)", 
'\000' <repeats 61 times>}
$9 = {pid = 9456, unix_sock = 20, idx = -1,
  desc = "udp receiver child=3 sock=172.31.46.236:6050 (sip.domain.com:6050)", 
'\000' <repeats 61 times>}
$10 = {pid = 9457, unix_sock = 21, idx = -1, desc = "slow timer", '\000' 
<repeats 117 times>}
$11 = {pid = 9458, unix_sock = 22, idx = -1, desc = "timer", '\000' <repeats 
122 times>}
$12 = {pid = 9459, unix_sock = 23, idx = -1, desc = "secondary timer", '\000' 
<repeats 112 times>}
$13 = {pid = 9460, unix_sock = 24, idx = -1, desc = "MI FIFO", '\000' <repeats 
120 times>}
$14 = {pid = 9467, unix_sock = 26, idx = -1, desc = "ctl handler", '\000' 
<repeats 116 times>}
$15 = {pid = 9468, unix_sock = 4, idx = -1, desc = "TIMER NH", '\000' <repeats 
119 times>}
$16 = {pid = 9469, unix_sock = 30, idx = -1, desc = "Http Worker", '\000' 
<repeats 116 times>}
$17 = {pid = 9470, unix_sock = 31, idx = 0, desc = "tcp receiver (generic) 
child=0", '\000' <repeats 97 times>}
$18 = {pid = 9474, unix_sock = 32, idx = 1, desc = "tcp receiver (generic) 
child=1", '\000' <repeats 97 times>}
$19 = {pid = 9475, unix_sock = 34, idx = 2, desc = "tcp receiver (generic) 
child=2", '\000' <repeats 97 times>}
$20 = {pid = 9476, unix_sock = 36, idx = 3, desc = "tcp receiver (generic) 
child=3", '\000' <repeats 97 times>}
$21 = {pid = 9477, unix_sock = -1, idx = -1, desc = "tcp main process", '\000' 
<repeats 111 times>}
(gdb)
(gdb)
````

Which also confirms that pid 9469 is in fact the Http Worker.

If I'm able to search the kamailio source code correct, then only 
http_async_client spawns that process. I'll rewrite some config code to not use 
that module, and just use http_client instead. It's fairly inconsequential in 
this case, so I'm alright with that.

If I catch another core dump with core per pid enabled I'll be sure to post 
that here as well.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1208#issuecomment-321017848
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Reply via email to