Also when this happens, even after I have managed to relaunch the agent, no build can run on it. It stops on "Waiting for next available executor on ‘node-name’", even though it is online. the previous build I stopped is still on the executor. The only solution is to restart Jenkins.
fredag 12. juli 2019 14.23.24 UTC+2 skrev Sverre Moe følgende: > > I don't actually have to do anything, judt open Configure, Save, then > Relaunch Agent. > > fredag 12. juli 2019 13.30.05 UTC+2 skrev Sverre Moe følgende: >> >> Strange >> If I configure the agent, save then try to reconnect it is able to create >> a connection and is back online. >> >> tirsdag 9. juli 2019 13.20.55 UTC+2 skrev Sverre Moe følgende: >>> >>> On the build agents that gets disconnected there is plenty of available >>> disk space. >>> >>> When there are trying to connect, there are no remoting.jar java process >>> on the agent running. >>> >>> lørdag 6. juli 2019 22.59.31 UTC+2 skrev Karan Kaushik følgende: >>>> >>>> Hi >>>> >>>> We had been facing the same issue with Jenkins agent, one thing I >>>> remember doing was managing the space on the jenkins agent, the disconnect >>>> could happen due to no space remaining on agent machine. >>>> >>> -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7707010a-2d74-4ea7-9e21-64f5c69604d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
