Child process with pid: 10834 was killed by signal: 15, core dump: 0

[cevo]

I got a lot of this error message in
/usr/local/lsws/logs/stderr.log

How to fix it?

2015-01-09 10:45:42.066 [STDERR] Child process with pid: 10834 was killed by signal: 15, core dump: 0

2015-01-09 10:45:51.096 [STDERR] Child process with pid: 10859 was killed by signal: 15, core dump: 0

2015-01-09 10:45:58.020 [STDERR] Child process with pid: 10843 was killed by signal: 15, core dump: 0

2015-01-09 10:46:09.018 [STDERR] Child process with pid: 10837 was killed by signal: 15, core dump: 0

2015-01-09 10:46:21.018 [STDERR] Child process with pid: 10879 was killed by signal: 15, core dump: 0

2015-01-09 10:46:30.022 [STDERR] Child process with pid: 10829 was killed by signal: 15, core dump: 0

2015-01-09 10:46:33.032 [STDERR] Child process with pid: 10943 was killed by signal: 15, core dump: 0

2015-01-09 10:46:34.011 [STDERR] Child process with pid: 10825 was killed by signal: 15, core dump: 0

2015-01-09 10:46:35.037 [STDERR] Child process with pid: 10826 was killed by signal: 15, core dump: 0

2015-01-09 10:46:44.016 [STDERR] Child process with pid: 11107 was killed by signal: 15, core dump: 0

 

[mistwang]

that's normal, unused PHP processes was stoped with SIGTERM by the web server.

 

[cevo]

if it normal behaviour should Litespeed fix it not to produce the error to stderr? to avoid any misunderstood?

 

[mistwang]

We could do that, but it can help us analyzing what happened when real problem happens, so we prefer leaving it there.