Bug #34024 | NullPointerException getServerStatusInfo(AgentMonitorEntry.java:151) | ||
---|---|---|---|
Submitted: | 23 Jan 2008 22:16 | Modified: | 23 May 2008 18:50 |
Reporter: | Adam Dixon | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Enterprise Monitor: Web | Severity: | S3 (Non-critical) |
Version: | 1.2.0.7879 | OS: | Linux |
Assigned to: | Darren Oldag | CPU Architecture: | Any |
[23 Jan 2008 22:16]
Adam Dixon
[23 Jan 2008 23:35]
Joshua Ganderson
Appears that the history object retrieved for this server is returning a null alarm level. I don't believe that should be possible however and I'm likely to need some help to track this down since I'll be unable to repeat.
[28 Jan 2008 19:23]
Sloan Childers
There was not enough information to tell how it got in this state... but the monitor history in the MEM repository was out of sync with itself. Basically, there were history entries that had no "current" state associated with it, which (theoretically) is impossible. In order to get the customer up and running as soon as possible, I'm just going to suggest we clean up the database for the messed up server. there are several approaches -- some are surgical fixes, and some are brute force. I'll let you and the customer decide which is most appropriate. 1) Get rid of that server and start over... you can try to delete the server from the UI. (in the normal fashion from the manager servers tab). if that is not working, shut down the agent for this mysqld. shut down MEM (tomcat). "delete from inv_agents where agent_id=14". restart tomcat. start up the agent. 2) clean up the history only, leaving existing server data intact. stop MEM (tomcat). "delete from monitor_history where server_id=14". restart tomcat. you should be good to go. it may take a couple of data collection cycles from the agent before the server comes "up" again. Let me know if there are any more questions. Oldag
[23 Apr 2008 18:50]
Gary Whizin
The Support issue was closed. We cannot reproduce it, so unless there's additional feedback we're unable to help with this...
[23 May 2008 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".