Announcement Announcement Module
Collapse
No announcement yet.
AMS Console Throws Unauthorized Exception - Server Configuration Action Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • AMS Console Throws Unauthorized Exception - Server Configuration Action

    I've just installed and Agent, AMS Server, and tcServer on my local machine. Everything seems to be working until I attempt to view the Application Management or Server Configuration tabs for my tcServer.

    When I drill into these tabs, I see:
    Agent exception occurred on <myhost> tc Server <myserver>: Unauthorized

    In my AMS server logs, I see:
    2009-09-10 13:32:44,743 INFO [http-0.0.0.0-7080-1] [org.hyperic.hq.agent.client.AgentConnection] 10.46.104.197 -> hyperic.livedata.getData
    2009-09-10 13:32:44,837 WARN [http-0.0.0.0-7080-2] [com.springsource.ams.tcserver.serverconfig.web.ser vices.SettingsLoaderImpl] Unable to load Settings for '2:10008', 500 Agent exception occurred on <myhost> tc Server <myserver>: Unauthorized

    Any ideas?

    Thanks in advance.

  • #2
    Originally posted by jdevine View Post
    I've just installed and Agent, AMS Server, and tcServer on my local machine. Everything seems to be working until I attempt to view the Application Management or Server Configuration tabs for my tcServer.

    When I drill into these tabs, I see:
    Agent exception occurred on <myhost> tc Server <myserver>: Unauthorized

    In my AMS server logs, I see:
    2009-09-10 13:32:44,743 INFO [http-0.0.0.0-7080-1] [org.hyperic.hq.agent.client.AgentConnection] 10.46.104.197 -> hyperic.livedata.getData
    2009-09-10 13:32:44,837 WARN [http-0.0.0.0-7080-2] [com.springsource.ams.tcserver.serverconfig.web.ser vices.SettingsLoaderImpl] Unable to load Settings for '2:10008', 500 Agent exception occurred on <myhost> tc Server <myserver>: Unauthorized

    Any ideas?

    Thanks in advance.
    JDevine,

    Do you have other AMS agents running on the system? The only time I have seen this is when the authentication token from the agent is incorrect.
    Please verify no other agent is running, shutdown this agent, delete the data directory under the agent-home. Restart the agent and reconfigure it with the AMS server.

    HTH,

    Jason

    Comment


    • #3
      Worked - thank you

      That worked. It looked like it was related to how I was configuring the agent.

      I was attempting to use 127.0.0.1 for both questions below.

      When I changed my answers to below, it worked fine.

      What is the AMS server IP address? 127.0.0.1
      What IP should AMS use to contact the agent? <actual>

      Thanks again.

      Comment

      Working...
      X