JON update from 3.3.2 to JON 3.3.3 does not remove all files introduced with JON 3.3.0 update 02
Issue
- JON update from 3.3.2 to JON 3.3.3 does not remove all files introduced with JON 3.3.0 update 02
- Storage node recovery (restart) does not change the status of the JON Server and JON agent is not re-registered with the server.
- When storage node is down, the following message is repeated all the time and scheduling interval is very quickly increased:
10:49:25,086 ERROR [com.datastax.driver.core.ControlConnection] (Reconnection-1) [Control connection] Cannot connect to any host, scheduling retry in 512000 milliseconds
- JON Agent is not reconnecting to the JON Server once the JON storage node is restarted;
- The server.log file contains the following error messages:
11:07:56,207 ERROR [stderr] (StorageNode SessionAliveChecker) Exception in thread "StorageNode SessionAliveChecker" java.lang.NoSuchMethodError: org.rhq.server.metrics.MetricsDAO.checkLiveness(Ljava/lang/String;)Lcom/datastax/driver/core/ResultSet;
11:07:56,207 ERROR [stderr] (StorageNode SessionAliveChecker) at org.rhq.enterprise.server.storage.StorageClientManager$SessionAliveChecker.run(StorageClientManager.java:674)
Environment
- Red Hat JBoss Operations Network (JON) 3.3.0
- Red Hat JBoss Operations Network 3.3 is updated first to Update 02 and then to Update 03;
- JON storage node is shut down and JON Server is in
MAINTENANCE
mode and JON Agent is backfilled; - JON Storage node is started again;
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.