You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
I thought that since kamcmd ps was matching the amount of Kamailio running processes we could be able to find why the count was not matching, in this
For the last test I lowered the amount of childs
0(21919) CRITICAL: <core> [core/pt.c:285]: fork_process(): Process limit of 13 exceeded. Will simulate fork fail.
As seen above there is 14 processes when the server is starting properly, I concluded that is must be one of the following :
/ # kamcmd ps
7 main process - attendant
24 udp receiver child=0 sock=117.75.69.33:5060
25 udp receiver child=0 sock=117.75.69.33:5160
26 slow timer
27 timer
28 secondary timer
29 JSONRPC-S FIFO
30 JSONRPC-S DATAGRAM
31 ctl handler
32 RTIMER EXEC child=0 timer=tmetrics
33 HTable Timer
34 Dialog Clean Timer
35 tcp receiver (generic) child=0
36 tcp main process
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.