Bug 606641 - multiple connectors get created when time is changed on the rhq server
multiple connectors get created when time is changed on the rhq server
Status: CLOSED DUPLICATE of bug 598095
Product: RHQ Project
Classification: Other
Component: Communications Subsystem (Show other bugs)
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Corey Welton
Depends On:
  Show dependency treegraph
Reported: 2010-06-22 02:38 EDT by Sudhir D
Modified: 2010-09-24 09:17 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-09-24 09:17:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Multiple connectors post system time change. (182.23 KB, image/png)
2010-06-22 02:38 EDT, Sudhir D
no flags Details

  None (edit)
Description Sudhir D 2010-06-22 02:38:35 EDT
Created attachment 425835 [details]
Multiple connectors post system time change.

Description of problem:
The rhq server system time was out of sync and when I synced to ntp and restarted rhq, created another set of connectors and the old ones now show down and report under "Has Alerts or Currently Unavailable" in Dashboard

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install and configure rhq server on a non synced ntp server.
2. Sync the server, which is running rhq, to ntp and restart rhq.
3. Check the dashboard under "Has Alerts or Currently Unavailable"
Actual results:
The connectors show down for 7080 and 7443. However, when we check under Resources->Connector, we can see that there is a new set of connector that is created and the old ones show as down.

Expected results:
The old one should be removed, if the new connectors are automatically created. If not the old ones should be re-used instead of creating new.

Additional info:
Comment 1 Corey Welton 2010-09-24 09:17:04 EDT

*** This bug has been marked as a duplicate of bug 598095 ***

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