Bug 1339586
| Summary: | When storage server is back to running state, rhq-Server status still in MAINTENANCE mode only | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Vijay Kumar <pasumarthivijaykumar> |
| Component: | Core Server, Communications Subsystem, High Availability, Operations, Storage Node | Assignee: | Michael Burman <miburman> |
| Status: | CLOSED DUPLICATE | QA Contact: | Mike Foley <mfoley> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | JON 3.3.6 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-25 12:50:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 1212627 *** |
Description of problem: When storage server is up and running, rhq-Server status still in MAINTENANCE mode only. Version-Release number of selected component (if applicable): 4.13.1 How reproducible: Always Steps to Reproduce: 1. Stop Storage server (using service command / kill the process) 2. now rhq-server comes to MAINTENANCE mode. 3. now start the storage server, once it is up and running rhq-server is not getting connected to subSystem until rhq-server restart happens. Actual results: rhq-server is not connected to subSystem storage server, once the storage is up and running. Expected results: rhq-server should get connected to subSystem storage server, once the storage is up and running. Additional info: Storage client subsystem wasn't initialized because it wasn't possible to connect to the storage cluster. The RHQ server is set to MAINTENANCE mode. Please start the storage cluster as soon as possible.: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: esmon/141.137.236.129 ([esmon/141.137.236.129] Cannot connect)) at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:185) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:80) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:839) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Manager.access$100(Cluster.java:763) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster.<init>(Cluster.java:93) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Builder.build(Cluster.java:732) [cassandra-driver-core-1.0.8-jboss-1.jar:] at org.rhq.cassandra.util.ClusterBuilder.build(ClusterBuilder.java:130) [rhq-cassandra-util-4.13.1.jar:4.13.1] at org.rhq.cassandra.schema.SessionManager.initSession(SessionManager.java:33) [rhq-cassandra-schema-4.13.1.jar:4.13.1] at org.rhq.cassandra.schema.AbstractManager.initClusterSession(AbstractManager.java:100) [rhq-cassandra-schema-4.13.1.jar:4.13.1] at org.rhq.cassandra.schema.AbstractManager.initClusterSession(AbstractManager.java:90) [rhq-cassandra-schema-4.13.1.jar:4.13.1] at org.rhq.cassandra.schema.VersionManager.checkCompatibility(VersionManager.java:259) [rhq-cassandra-schema-4.13.1.jar:4.13.1] at org.rhq.cassandra.schema.SchemaManager.checkCompatibility(SchemaManager.java:136) [rhq-cassandra-schema-4.13.1.jar:4.13.1]