-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
CentOS / RHEL 6.x
I am seeing the following in the jenkins logs when nodes are starting up.
Aug 07, 2013 2:18:42 PM com.youdevise.hudson.slavestatus.SlaveListenerInitiator onOnline
INFO: Starting slave-status listener on NJ3
Aug 07, 2013 2:19:17 PM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor
WARNING: Failed to monitor SC9 Prod Jenkins for Free Temp Space
java.util.concurrent.TimeoutException
at hudson.remoting.Request$1.get(Request.java:275)
at hudson.remoting.Request$1.get(Request.java:210)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:97)
at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:282)
- duplicates
-
-
- Open
-
[JENKINS-19107] Nodes Unable to monitor free temp space
Matt Taylor
added a comment - Pavel this is still an issue and agree exactly with your comment I have experienced the same.
Matt Taylor
added a comment - Pavel this is still an issue and agree exactly with your comment I have experienced the same. It is same as JENKINS-20947, see the analysis there. Closing as a duplicate.
Hopefully JENKINS-48309 will resolve that
Hi,
Iam using linux jenkins master (Jenkins 2.332.2) and trying to connect linux node using username and password.
after showing slave setup done, Getting below error and agent gets disconnecting.
I tried to use ssh private keys, still no luck.
java version "java 11 corretto" using for both master and slave. tried all possible ways, no luck
tried to disable all node monitoring stuff,no use
able to ssh from both servers.
sujan reddy
added a comment - - edited Hi,
Iam using linux jenkins master ( Jenkins 2.332.2 ) and trying to connect linux node using username and password.
after showing slave setup done, Getting below error and agent gets disconnecting.
I tried to use ssh private keys, still no luck.
java version "java 11 corretto" using for both master and slave. tried all possible ways, no luck
tried to disable all node monitoring stuff,no use
able to ssh from both servers. sujanr23 please, do not reopen issues a long time ago closed
https://www.jenkins.io/participate/report-issue/#issue-reporting
Hello,
I'm sorry to reopen this issue, but I think this "Failed to monitor" error is a cause of our ongoing problem with randomly hanged jobs on slave machines (described here: https://issues.jenkins-ci.org/browse/JENKINS-19445).
In our case, there appears "Failed to monitor SlaveName for Free Swap Space" error. When this error happens (on on-demand started slave machines), the build job is never performed. It waits endlessly with "Building remotely on slave-name..." message and spinning circle.
I disabled all monitoring tasks in node configuration, but it seems the swap monitoring still tries to start but fails? Any chance to fix this behavior? Thank you in advance!