Inbound WebSocket agents remain offline after Jenkins reboot

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: support-core-plugin
    • Environment:
      Jenkins: 2.440.2
      Agents: 3206.vb_15dcf73f6a_9
      Java (Jenkins, Agents): 17.0.10
      support-core-plugin: 1421.v1a_899a_c02a_54

      After updating to the latest version of the support core plugin I noticed that my inbound agents remain offline and the only way to bring them back online is to reboot the agents when the Jenkins is up and running.

      I get the following Jenkins warning for each agent which is trying to connect:

      [id=76]    WARNING j.u.ErrorLoggingExecutorService#lambda$wrap$0
java.lang.NullPointerException: Cannot invoke "java.lang.Boolean.booleanValue()" because the return value of "java.util.Map.put(Object, Object)" is null
        at com.cloudbees.jenkins.support.impl.SlaveLaunchLogs$Jenkins72799Hack.preOnline(SlaveLaunchLogs.java:200)
        at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:720)
        at jenkins.slaves.DefaultJnlpSlaveReceiver.afterChannel(DefaultJnlpSlaveReceiver.java:176)
        at org.jenkinsci.remoting.engine.JnlpConnectionState.fire(JnlpConnectionState.java:337)
        at org.jenkinsci.remoting.engine.JnlpConnectionState.fireAfterChannel(JnlpConnectionState.java:428)
        at jenkins.agents.WebSocketAgents$Session.lambda$opened$2(WebSocketAgents.java:136)
        at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        at jenkins.util.ErrorLoggingExecutorService.lambda$wrap$0(ErrorLoggingExecutorService.java:51)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)

      By disabling the support core plugin the problem disappears.

       

            Assignee:
            Emilio Escobar
            Reporter:
            Meyti
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: