KBEC-00336 - Workspace Issue: Agent returned error 404

Problem:
When you try to access the log icon of a step, you do not see the content of the log file.
Instead you see a message similar to:
"The agent returned error 404.

resolveFile failed with code: [NoSuchAgent] message: ‘Agent ‘136’ does not exist’"
Solution:
One possible cause for this problem:
If your CloudBees CD (CloudBees Flow) Server hostname definition does match the Web Server’s
definition of the CloudBees CD (CloudBees Flow) Server hostname
Check the commander.properties file located in the CloudBees CD (CloudBees Flow) server host:
/conf/commander.properties

COMMANDER_SERVER_NAME=

Make sure the in the commander.properties is also set in the Web Server httpd.conf file

In the Web Server host, check /conf/httpd.conf

SetEnv COMMANDER_SERVER

should be the same as

Example

commander.properties in CloudBees CD (CloudBees Flow) server host contains

COMMANDER_SERVER_NAME=ecloud.electric-cloud.com

httpd.conf in Web Server host contains

SetEnv COMMANDER_SERVER ecloud

I would edit the httpd.conf file to:

SetEnv COMMANDER_SERVER ecloud.electric-cloud.com

Applies To:
All supported OS and versions of ElectricCommander and CloudBees CD (CloudBees Flow)

Have more questions?

0 Comments

Please sign in to leave a comment.