JON Agent fails to connect to the JON Server with the message: "... restart the agent with the option "-Drhq.agent.security-token=<the valid security token>" "

Solution Verified - Updated -

Environment

  • Red Hat JBoss Operations Network (JON)
    • 3.x

Issue

  • When we try to re-register JBoss ON Agent with JBoss ON Server, after we've entered the ip, agent's name etc, we got the following message:
The setup has been completed for the preferences at node [/rhq-agent/default].
The server has rejected the agent registration request. Cause: org.rhq.core.clientapi.server.core.AgentRegistrationException:The agent asking for registration under the name [jon_agent_name] provided an invalid security token. This request will fail. Please consult an administrator to obtain the agent's proper security token and restart the agent with the option "-Drhq.agent.security-token=<the valid security token>"
Will retry the agent registration request soon...

Resolution

JBoss ON Server release 3.x brought few changes in the way how JBoss ON Agent registers and gets connected with the JBoss ON Server. From JBoss ON 3.0.1, one of them is that the JON Agent cannot register with an existing agent name without corresponding security token. If for any reason, security token is lost, it will have to be re-installed if the name of the agent already exists. The following documents contain more information regarding security token and how to re-install security token.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.