Thanks @miconda for your hints. We will try this if kamailio crashes again.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3539#issuecomment-1693033259
You are receiving this because you are subscribed to this thread.
Message ID:
Got another crash during the night and it dumped a core for the crashed
process. However the one that was originally dumped was also from the dying
Http Worker-process, so it contained nothing that wasn't already posted in this
issue.
I have both cores stored away, if the module devs want me
@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' }
$2 = {pid = 9449, unix_sock = 13, idx = -1,
desc = "udp receiver child=0 sock=172.31.46.236:5060
@miconda
This is really all it gives me. I've tried both Enter, Space and a bunch of
other things. Nothing really indicates there would be any more data to print.
(gdb)
(gdb)
(gdb)
(gdb) set $i=0
(gdb) while ($i < process_no)
>p pt[$i++]
>end
$16 = {pid = 9446, unix_sock = -1, idx = -1,
Looks like at least that modules spawns a process with that type:
https://github.com/kamailio/kamailio/blob/4.4/modules/http_async_client/http_async_client_mod.c#L374
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@miconda
I've grapped kamctl ps output now:
Process:: ID=0 PID=29653 Type=main process - attendant
Process:: ID=1 PID=29656 Type=udp receiver child=0 sock=172.31.46.236:5060
(sip.telzio.com:5060)
Process:: ID=2 PID=29657 Type=udp receiver child=1 sock=172.31.46.236:5060
This is the result of that:
$31 = {pid = 9446, unix_sock = -1, idx = -1, desc = "main process - attendant",
'\000' }
$32 = {pid = 9449, unix_sock = 13, idx = -1,
desc = "udp receiver child=0 sock=172.31.46.236:5060 (sip.domain.com:5060)",
'\000' }
$33 = {pid = 9450, unix_sock = 14, idx =
@miconda
Ah, as this looks like one of the processes crashing out we'll get just two
core files?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@miconda
Here are the lines immediately after the Critical
Aug 7 22:44:11 ip-172-31-46-236 /usr/local/sbin/kamailio[9477]: CRITICAL:
[pass_fd.c:277]: receive_fd(): EOF on 30
Aug 7 22:44:13 ip-172-31-46-236 /usr/local/sbin/kamailio[9449]: ERROR: maxfwd
[mf_funcs.c:62]:
The last core dump it did was 300mb - it's running 20 processes or so, so I
would guess now it needs to dump 300*20mb?
If that's the case I need to expand the volume of this server before enabling
this, else it'll potentially run out of space.
echo "0" > /proc/sys/kernel/core_uses_pid
@SurendraPlivo
Alright, I've executed the following on the server. Do I need to restart
Kamailio or anything for it to take effect?
echo "1" > /proc/sys/kernel/core_uses_pid
I've checked the memory monitor for the time around the last crash (+/- 6
hours), but there was no noticable
These are the modules I'm loading
```
loadmodule "db_postgres.so"
loadmodule "mi_fifo.so"
loadmodule "kex.so"
loadmodule "tm.so"
loadmodule "tmx.so"
loadmodule "sl.so"
loadmodule "rr.so"
loadmodule "pv.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule
12 matches
Mail list logo
