Agents LostContact status after go-server upgrade to 19.8.0-9915

[Michael Trafficante]

Upgrading and reinstalling existing agents has not resolved the issue. Seeing this in the go-server.log:

2019-09-24 01:19:03,104 WARN  [qtp1995616381-48] HttpChannel:590 - /go/admin/latest-agent.status

javax.servlet.ServletException: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.NullPointerException

        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)

        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)

        at org.eclipse.jetty.server.Server.handle(Server.java:502)

        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)

        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)

        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)

        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)

        at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:411)

        at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:305)

        at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:159)

        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)

        at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)

        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)

        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)

        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)

        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)

        at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)

        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)

        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)

        at java.lang.Thread.run(Thread.java:748)

[Ankit Srivastava]

Hi Michael,

Do you see any error in the GoCD agent logs? Can you check below log files:

go-agent-bootstrapper-wrapper.log go-agent-bootstrapper.log         go-agent-launcher.log             go-agent-stderr.log               go-agent-stdout.log               go-agent.log

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/064ab94f-e5b1-446e-b09b-ab0fe3edb498%40googlegroups.com.

--

Regards,

Ankit

[Jeff]

I had issues w/ my 19.4.0 agents having their /var/lib/go-agent/config/token file deleted so it wouldn't connect back to the server.  I had to remove the guid.txt file and re-accept/enable the agent on the server (getting a new guid) and then had to update all my environments to use the new agent guids.

I initially thought it was when upgrading the go-agent from 19.4.0 to 19.8.0, but even rebooting an existing 19.4.0 agent after the server upgrade would cause the issue.  I was not able to get a 19.4.0 back to that state where it would happen though since I had already upgraded the server.  

Something to check at least.

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAFC4iTXgYbHhEW5GK8yUOJQ00wUF7doEDadzbXGx0U_Ck-ugJA%40mail.gmail.com.