Bug #38409 Upgrading MySQL server needs an agent restart in order to show up on the UI
Submitted: 28 Jul 2008 16:14 Modified: 21 Jan 2010 7:40
Reporter: Diego Medina Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version:2.0.0.7016 OS:Any
Assigned to: Darren Oldag CPU Architecture:Any
Tags: windmill

[28 Jul 2008 16:14] Diego Medina
Description:
If you are monitoring one instance of mysql server (mysqld) and then upgrade that mysqld.

The new "version" of the mysql server will not show up on the UI

How to repeat:
1- install an order version of mysqld (5.0.x)
2- install the monitor
3- install the agent
4- start the agent, monitor and mysqld
5- see the mysqld instance show up on the dashboard
6- stop the mysqld
7- install a new version of the mysql server
8- start the new mysld
9- go to the UI, this server will not show up
[28 Jul 2008 16:17] Diego Medina
The work around is to restart the agent, but for customers monitoring 30+ servers, we would be adding one more step to each server upgrade.
[16 Sep 2008 7:09] Simon Mudd
The real solution is to collect the information the first time the agent connects to the server.

Current MySQL implementations don't allow you to change the version dynamically so further requests of the version number SHOULD NOT change, and are therefore pointless.

If the connection goes away (typical if you upgrade the server) the agent is disconnected, so it connects again and collects the new version.
[13 Jan 2009 11:33] Tony Bedford
An entry was added to the 2.0 changelog:

Important Note: If you are monitoring one instance of MySQL server (mysqld) and then upgrade that MySQL server, the correct version of the MySQL server is not displayed in the Dashboard. This is a known issue that will be fixed in future versions of MySQL Enterprise Monitor.
[15 Sep 2009 16:36] Enterprise Tools JIRA Robot
Gary Whizin writes: 
* Workaround is to use the new Refresh feature on the menu on the Manage Servers page.
* Rename "Refresh" to "Refresh Inventory"
* Longterm should consider inventory deltas
* Meanwhile, Doc team should tell users to hit Refresh Inventory if they upgrade mysql
[14 Jan 2010 1:03] Enterprise Tools JIRA Robot
Keith Russell writes: 
Patch available in builds => 2.1.1.1138.
[15 Jan 2010 19:58] Enterprise Tools JIRA Robot
Diego Medina writes: 
agent log
[15 Jan 2010 19:58] Enterprise Tools JIRA Robot


Attachment: 10267_mysql-monitor-agent.log (text/plain), 1.44 MiB.

[15 Jan 2010 21:09] Enterprise Tools JIRA Robot
Diego Medina writes: 
the way the service manager does it on 2.2 works just fine
[15 Jan 2010 22:40] Enterprise Tools JIRA Robot
Keith Russell writes: 
Patch installed in versions => 2.1.1.1140.
[20 Jan 2010 16:56] Enterprise Tools JIRA Robot
Diego Medina writes: 
Verified fixed on 2.1.1.1140
[21 Jan 2010 7:40] MC Brown
A note has been added to the 2.1.1 changelog: 

        If you are monitoring one instance of MySQL server                                                                                                 
        <command>mysqld</command> and then upgrade that MySQL server,                                                                                      
        the correct version of the MySQL server is not displayed in the                                                                                    
        Dashboard. The agent will now perform a re-synchronization of                                                                                      
        the inventory if it identifies that the server has gone away and                                                                                   
        that the monitored MySQL has been upgraded.