Bug #48992 Changes to server stats are not applied after changing them: needs restart
| Submitted: | 23 Nov 2009 13:22 | Modified: | 15 Feb 2010 15:33 |
|---|---|---|---|
| Reporter: | Geert Vanderkelen | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
| Version: | 5.2.8 | OS: | MacOS (10.6.2) |
| Assigned to: | Maksym Yehorov | CPU Architecture: | Any |
[28 Jan 2010 10:41]
Maksym Yehorov
Failed to repeat on latest, tried in osx and linux.
[12 Feb 2010 22:22]
Johannes Taxacher
changes are reflected now after restarting the admin profile
[15 Feb 2010 15:33]
Tony Bedford
An entry has been added to the 5.2.16 changelog: If the command for checking server status was changed in a server instance, the change did not take effect unless MySQL Workbench was restarted.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
Description: In Workbench Server Administration: If you change the way an instance is gathering Server Stats, the changes only take effect when you restart workbench or start the instance for the first time. How to repeat: * Start Workbench * Open an instance and see the CPU stats working (if at all that is) * close the tab * Change something to the Server Stats in 'Manager Server Instances', e.g. "/usr/bin/uptime | wba_token(' ', 8)" instead of /usr/bin/uptime | wba_token(' ', 10) * Open the instance again, it is broken * Now fix it like it was and open the instance again: no change. * Restart Workbench * Open the instance, and it should again work.