> > After seen the log I understand you are asking for the INFO messages that > inform that a Docker agent is disconnected, IIRC those messages are normal > they only inform about the Docker agent status, > > Thanks for your reply. Let me make sure I understand. So the Docker Cloud plugin will spawn new Jenkins Docker agents. It'll stop the agents by using DockerContainerWatchdog thread which regularly tries to connect to the agent and when it fails, it removes the agent. This is what happened in the following example:
2020-02-14 09:13:37.434+0000 [id=268432] INFO i .j.docker.DockerTransientNode$1#println: Disconnected computer for node 'Jenkins SSH Slave a3-0094ebcvu7jkf'. 122020-02-14 09:13:37.434+0000 [id=268243] INFO h.r.SynchronousCommandTransport$ReaderThread#run: I/O error in channel Jenkins SSH Slave a3-0094ebcvu7jkf 13java.net.SocketException: Socket closed 14 at java.net.SocketInputStream.socketRead0(Native Method) 15 at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) 16 at java.net.SocketInputStream.read(SocketInputStream.java:171) 17 at java.net.SocketInputStream.read(SocketInputStream.java:141) 18 at io.jenkins.docker.client .DockerMultiplexedInputStream.readInternal(DockerMultiplexedInputStream.java :48) 19 at io.jenkins.docker.client.DockerMultiplexedInputStream.read (DockerMultiplexedInputStream.java:30) 20 at hudson.remoting.FlightRecorderInputStream.read (FlightRecorderInputStream.java:91) 21 at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java: 72) 22 at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream. java:103) 23 at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport. java:39) 24 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read (AbstractSynchronousByteArrayCommandTransport.java:34) 25 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport. java:63) 262020-02-14 09:13:37.440+0000 [id=268432] INFO i .j.docker.DockerTransientNode$1#println: Removed Node for node 'Jenkins SSH Slave a3-0094ebcvu7jkf'. So it means that whether the agent finishes it work or whether there's a connection issue between Jenkins master and the agent, it'll be reported the same in the jenkins.log file. Basically it's the same mechanism for stopping an agent having finished its work or handling a connection error. In both cases it"ll be reported as INFO in the logs too. Right? you can change the verbose level of the Java package on logs configuration > to omit those type of messages if they bother you Indeed that could be interesting. Now it means we would also not be able to see the real communication errors between master and agents I guess. Thanks a lot for your help. If you could confirm this it would be great; I'd be able to move forward and move to the next problems (we have plenty of intermittent errors to figure out ;)). Have a great weekend -Vincent -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c7e601cd-b34c-4e75-8d76-fb58439474ef%40googlegroups.com.
