| Bug #52151 | Intermittent No data for System Health | ||
|---|---|---|---|
| Submitted: | 17 Mar 2010 18:29 | Modified: | 13 Dec 2010 16:32 |
| Reporter: | Tyler Williamson | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
| Version: | 5.2.15 OSS | OS: | Windows (Windows 7) |
| Assigned to: | Mike Lischke | CPU Architecture: | Any |
| Tags: | no data, server health, system | ||
[25 Mar 2010 2:46]
MySQL Verification Team
Thank you for the bug report.
[21 May 2010 17:54]
Maksym Yehorov
I can not repeat the issue from windows 7 to oracle enterprise linux 5.5.
[2 Jun 2010 0:14]
John Haney
I see the same thing. DB is 5.0.89 running on RHEL. Client is 5.5.21 on Windows XP. It has happened on previous versions as well.
[1 Oct 2010 12:38]
Mike Lischke
This problem cannot entirely be fixed. If your CPU load is high or the server connection slow so that no data comes in then WB shows that. This is on purpose to let you know if something is wrong. However, I increased the timeout from 5 to 15 seconds, so this does not show up too often, e.g. for short drops.
[8 Dec 2010 21:41]
Johannes Taxacher
fix confirmed in repository
[13 Dec 2010 16:32]
Tony Bedford
An entry has been added to the 5.2.31 changelog: In the Administrator, system health displayed NO DATA.
Description: MySQL Server 5.0.77 CentOS 5.3 # Customize this script to suit your system if necessary # Shell function names and output format must be maintained get_cpu_info = /usr/bin/uptime | wba_token(' ', 10) get_mem_info = free | wba_filter(Mem:) | wba_token(' ', 3) get_mem_total = free | wba_filter(Mem:) | wba_token(' ', 1) These settings in MySQL Workbench cause SYSTEM HEALTH to continuously flash NO DATA and then come back with the stats. Without these config settings, if they are removed, the SYSTEM HEALTH is fine. How to repeat: Add the get_cpu_info, get_mem_info, and get_mem_total Suggested fix: Do not know