[JIRA] (JENKINS-12569) Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes

[sam777t@gmail.com (JIRA)]

Sam Talebbeik created JENKINS-12569:
---------------------------------------

Summary: Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes
Key: JENKINS-12569
URL: https://issues.jenkins-ci.org/browse/JENKINS-12569
Project: Jenkins
Issue Type: Bug
Components: core
Environment: Jenkins 1.409.3
Main server is running on Ubuntu 2.6.24-24-generic
Slaves are running on a variety of Ubuntu 32 or 64 bit and Windows 32 and 64 bit

Reporter: Sam Talebbeik

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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[caleb.tote@gmail.com (JIRA)]

Caleb Tote commented on JENKINS-12569

Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes

We too are seeing this issue; as well as the issue referenced by Pavel.

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators.

[mjvanderloo@yahoo.com (JIRA)]

Mark Vanderloo commented on JENKINS-12569

Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes

We are seeing this in 1.553, too.

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators.

[daniel@beckweb.net (JIRA)]

Daniel Beck commented on JENKINS-12569

Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes

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 since.

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators.

[daniel@beckweb.net (JIRA)]

Daniel Beck edited a comment on JENKINS-12569

Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes

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.

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators.

[SeventhSon99@gmail.com (JIRA)]

Steven Murphy commented on JENKINS-12569

Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes

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.

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators.

[daniel@beckweb.net (JIRA)]

Daniel Beck commented on JENKINS-12569

Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes

At least for custom log recorders in, you can reduce logging levels for more specific loggers since 1.549 (undocumented, unfortunately).

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators.