Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Server reports key errors when agent is in bad state

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.6.5
  • Fix Version/s: None
  • Component/s: None
  • Environment:
    Two ubuntu 11.10 servers with mysql 5.1 backend with 4.6.5 RTM in failover configuration.

    Env was setup less than 1.25 hours ago
  • Case Links:
    none
  • Regression:
    No

Description

Symptoms:

in the server.log:

Failed to send ping command to agent with id 10106. Reason: Error sending argument: Unable to connect to 192.168.69.102:2144: java.security.cert.CertificateException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, retried 5 times, cmd=agent:ping

and server is unable to ping agent.

Steps to Reproduce:

1.) Shutdown agent - The agent needs to not properly shutdown and just hang. Can't figure out exactly what to reproduce this yet.

Activity

Hide
Wes Schlichter added a comment - - edited

I can't reproduce this again myself but this is what it seems to be.

The agent didn't die properly, left port 2144 open. Server thinks it is getting a bad cert and rejects it's own attempts to communicate with agent.

Agent started again with 13-03-2012 14:55:40,273 CDT WARN [AgentDaemonMain] [SSLConnectionListener@237] Failed to listen at *:2144: Address already in use. Will retry until up.

this wasn't prominent in agent.log and I missed it since agent was still showing activity.

This would appear to be more of an agent issue and not specific to failover env.

Show
Wes Schlichter added a comment - - edited I can't reproduce this again myself but this is what it seems to be. The agent didn't die properly, left port 2144 open. Server thinks it is getting a bad cert and rejects it's own attempts to communicate with agent. Agent started again with 13-03-2012 14:55:40,273 CDT WARN [AgentDaemonMain] [SSLConnectionListener@237] Failed to listen at *:2144: Address already in use. Will retry until up. this wasn't prominent in agent.log and I missed it since agent was still showing activity. This would appear to be more of an agent issue and not specific to failover env.
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 4 days ago