[BambooAgentHttpRequestUtils] Cannot process message: invalid authentication token

[Eric Hong]

I'm testing with a trial version of Bamboo and it was working fine when one day suddenly the agent failed to connect and went down with this error on the server log:

-------------------------

2021-09-27 10:36:31,172 WARN [http-nio-8085-exec-3] [BambooAgentHttpRequestUtils] Cannot process message: invalid authentication token [ba503f98c080c2f7e5d99118d72c0fec53e60e6c]: Artifact [node_modules] for CMAPP-ECM-JOB1-30

---------------------------

Also, on the Bamboo agent log:

----------------------------------
INFO | jvm 1 | 2021/09/27 10:36:29 | 2021-09-27 10:36:29,833 INFO [0-BAM::lc02d9378md6r.lan::Agent:pool-3-thread-1] [DefaultBuildAgent] Changing context: null -> CMAPP-ECM-JOB1-30 on lc02d9378md6r.lan/7b97e1bb
INFO | jvm 1 | 2021/09/27 10:36:29 | 2021-09-27 10:36:29,870 INFO [0-BAM::lc02d9378md6r.lan::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Found artifact that needs upload retry: node_modules
INFO | jvm 1 | 2021/09/27 10:36:29 | 2021-09-27 10:36:29,878 INFO [0-BAM::lc02d9378md6r.lan::Agent:pool-3-thread-1] [AbstractArtifactManager] Republishing [node_modules] for CMAPP-ECM-JOB1-30
INFO | jvm 1 | 2021/09/27 10:36:29 | 2021-09-27 10:36:29,914 INFO [0-BAM::lc02d9378md6r.lan::Agent:pool-3-thread-1] [AbstractArtifactManager] Trying to republish the artifact with handler: com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler
INFO | jvm 1 | 2021/09/27 10:36:31 | 2021-09-27 10:36:31,742 WARN [0-BAM::lc02d9378md6r.lan::Agent:pool-3-thread-1] [ArtifactStreams] Error during artifact transfer, total bytes written: 10199188, total requested: 10225544, latest request: 63220
INFO | jvm 1 | 2021/09/27 10:36:31 | java.net.SocketException: Broken pipe (Write failed)
INFO | jvm 1 | 2021/09/27 10:36:31 | at java.net.SocketOutputStream.socketWrite0(Native Method)

----------------------------

I re-instal the bamboo and bamboo agent with no avail. 

Not sure how to resolve this problem.

[Eric Hong · Accepted solution]

OK,

I figured it out.  I was running the local agent manually without creating a new local agent in the server.  After I used the server Admin => Agent => "Add local agent", everything works fine.