although I'm not the developer, I'll try to discuss it with you.
the message should come from lsapi ---
download latest php lsapi 6.6 (
http://www.litespeedtech.com/products/litespeed-sapi/download)
#grep "Children tracking is wrong" *
lsapilib.c: fprintf( stderr, "Children tracking is wrong: PID: %d, Cur Childen: %d, count: %d, idle: %d, dying: %d\n", getpid(),
so for
Code:
2014-04-01 10:49:18.059 [STDERR] Children tracking is wrong: PID: 11277, Cur Childen: 34, count: 36, idle: 22, dying: 0
a lsphp process (which pid=11277), counts its number of current child lsphp process, which is 34
by its tracking records(for example, +1 when adding a new child, -1 when kill an old child), it should be 36.
so 2 child lsphp has lost its track. then it reports to stderr.
there may be many reasons a child process losing its track by its parent process. for example, a manual kill.
it just print out a warning, if the number of such message is very few, can ignore it safely.
