Probably something doing fork-exec and that not being closed properly
On Aug 28, 2020, at 6:10 AM, <ziv@ip-com.co.il> <ziv@ip-com.co.il> wrote:
Hello
We have an occasional situation where the one FreeSWITCH process suddenly have a child process. We do not know what circumstances may have caused it. Happens every few days. The child process consumes memory like the normal process, which is a significant amount. It doesn’t consume CPU. In the case that we didn’t restart FreeSWITCH after the problem happened, later it happened again and we had 2 child processes. When killing the child process, FreeSWITCH seems to continue working normally, but this is not a thing we’d do on our production machines. Happens on one specific FreeSWITCH, our other machines do not show this behavior. The FreeSWITCH log for the time the child process starts shows initialization messages as when the normal process starts, but nothing that could tell us why the child starts.
After noticing the issue on FreeSWITCH 1.8.5, we upgraded to 1.10.5 via “apt” (didn’t build from source) but the problem is still there.
O/S: Debian 9.13 (we didn’t upgrade it when upgraded FreeSWITCH) FreeSWITCH: 1.10.5-release-17-25569c1631~64bit We use FusionPBX to operate the system.
“ps -ef” shows: UID PID PPID C STIME TTY TIME CMD freeswi+ 470 23710 0 11:25 ? 00:00:00 /usr/bin/freeswitch -ncwait -nonat freeswi+ 23710 1 62 Aug26 ? 1-11:31:26 /usr/bin/freeswitch -ncwait -nonat
“top” shows PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 23710 freeswi+ -2 19 3627008 1.543g 13972 S 110.7 20.7 2136:50 freeswitch 470 freeswi+ 39 19 3615296 1.507g 884 S 0.0 20.2 0:00.02 freeswitch