Open timja opened 12 years ago
Hi,
Any chance to have this problem fixed (make the swap space monitoring truly disabled)?
I'm too experiencing this problem where I disabled the swap space monitoring for slaves but it still tries to run and from some unknown reason it fails. This failure seems to be a cause of my problem with building on slave machines, reported here:
https://issues.jenkins-ci.org/browse/JENKINS-19445
We too are seeing this issue; as well as the issue referenced by Pavel.
We are seeing this in 1.553, too.
Seems to be a documentation issue of /computer/configure rather than a bug of node monitoring running even though it should not be.
From the code, it's obvious it's only that the result is ignored wrt taking slaves offline, monitoring always runs.
It would be good to have the ability to truly disable these checks. My HP slaves have issues with the Free Swap Space check (java exception 'top' unavailable) and these errors clutter the log.
At least for custom log recorders in, you can reduce logging levels for more specific loggers since 1.549 (undocumented, unfortunately).
Under Jenkins -> Manage Jenkins -> Manage Nodes --> Configure we have unchecked "Free Swap Space" option
This should disable the monitoring for the Free Swap Space.
Upon examining the Jenkins log we still see indications that the swap monitoring thread might still be running
WARNING: Previous Free Swap Space monitoring activity still in progress. Interrupting
Exception in thread "Monitoring slave-node1 for Free Swap Space" hudson.remoting.RequestAbortedException: hud
son.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
Originally reported by samt, imported from: Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes