Am 15.05.17 um 17:54 schrieb David Osborne: > In some cases (but not all), Ns_WaitProcess is logging an error > immediately after the reaper sends a signal 15. > > It's under these circumstances ReleaseProxy seems to find the proxy > Busy without a slave. > > [15/May/2017:16:38:39][23802.7f2f0d7fa700][-nsproxy:reap-] Warning: > [testpool]: pid 5174 won't die, send signal 15 > [15/May/2017:16:38:40][23802.7f2f0d7fa700][-nsproxy:reap-] Error: > process 5174 killed with signal 15 (Terminated) at least this case are of no concern: the reaper stops the child process and sends it a signal; then it recognizes, that the child was killed by a signal and reports this via the error log entry. "Error" is probably too strong here (for the server it is not clear, who sent the signal).... grading this down to a "warning" is probably not problematic and less worrying.
-gn ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
