Hi,
I was wondering if anyone could point us in the right direction with an
intermittent problem we're seeing. Apologies for the wooly problem
description - we don't have a firm test case as of yet.
These instances are running NaviServer/4.99.16d10 on Debian Jessie 8.10
The problem usually manifests itself as memory exhaustion on the server in
question where the system's OOM killer is invoked.
What seems to be causing the memory exhaustion is a copy of the main nsd
process (sometimes several) which can use large amounts of memory.
For example we captured a snapshot of this copy of the nsd daemon (also
using 4gb RSS) after it had been running for about 5 hours.
[image: image.png]
It appears as if there are 2 of main nsd daemons running. Usually only 1
nsd daemon is running on this server.
When this child was killed by the OOM killer, it was a Tcl exec of an
external command which was running within it - not a command that would
normally 5 hours to complete.
child killed: kill signal
while executing
"exec $cmd << $input"
In test, when running an exec from naviserver, I see the forked process
being created and initially named "nsd", then it takes on the name of the
underlying command. I'm not sure why this isn't happening in these cases.
Any insights?
--
*David *
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
