Bug 812000 - Guide the user what to do when the agent token is "not there"
Summary: Guide the user what to do when the agent token is "not there"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.4.0
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-12 13:45 UTC by Heiko W. Rupp
Modified: 2013-09-01 10:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-01 10:08:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Heiko W. Rupp 2012-04-12 13:45:28 UTC
snert:/im/rhq/modules/enterprise/agent/target/rhq-agent hrupp$ bin/rhq-agent.shListening for transport dt_socket at address: 8788
RHQ 4.4.0-SNAPSHOT [74326f0] (null)
The server has rejected the agent registration request. Cause: [org.rhq.core.clientapi.server.core.AgentRegistrationException:An agent is trying to register with an existing agent name [snert] without providing a valid security token. If you are attempting to re-register this agent, please consult an administrator to reconfigure this agent with its proper security token.]
Will retry the agent registration request soon...

Neither this, nor rhq-agent.sh --help tells me the magic -Dx=y combination to pass the token in - I think this is not user friendly.


We should either in that message list the property name - or on the server page that lists the token, so that a user that runs into that issue can easily fix it without googling etc.

Comment 2 John Mazzitelli 2012-04-12 13:57:31 UTC
the error messages are build in CoreServerServiceImpl - so any changes would go in there

Comment 3 John Mazzitelli 2012-04-12 14:28:55 UTC
git commit 5745929

message will now say:

An agent is trying to register with an existing agent name [snert] without providing a valid security token. If you are attempting to re-register this agent, 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>"

Comment 4 Heiko W. Rupp 2013-09-01 10:08:26 UTC
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.


Note You need to log in before you can comment on or make changes to this bug.