Bug #53609 Reports system load/memory of SSH tunnel host, not of remote MySQL instance
Submitted: 12 May 2010 20:28 Modified: 24 Jul 2010 7:22
Reporter: Anderson Vitous Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:5.2.21 OS:MacOS
Assigned to: CPU Architecture:Any

[12 May 2010 20:28] Anderson Vitous 
Description:
Configured and tested a connection to a remote MySQL server instance using TCP/IP through SSH (tunnel).  Verified connection succeeds.  Opened 'Server Administration' for new instance in Workbench GUI.  Server Health graphs look correct, as do the server system/status variables.  However, the small graphs for SYSTEM Load and Mem appear to reflect values for the host I'm using for the SSH tunnel, not for the host where the remote MySQL instance is running.

I can verify this because the SYSTEM graph is showing load avg 3.8, which is accurate for the 5 min load average of the ssh tunnel host, but is way off from what the mysql instance's host shows in top (0.2 currently).

How to repeat:
Configure remote connection using TCP/IP through SSH as noted above.

Helps to choose a host for SSH tunnel which has drastically different load average and memory usage than the one running the remote MySQL instance.

Open new connection for administration; observe the server version is correctly reflected, as are the mysql system/status variables, but the SYSTEM load/mem graphs will reflect for the ssh tunnel host.
[14 May 2010 12:42] Susanne Ebrecht 
Do you use a proxy?
[14 Jun 2010 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".
[15 Jun 2010 0:08] Anderson Vitous 
No proxy was in use for this.  The intermediate host was the one directly connected to from my desktop through which to run the ssh tunnel to the final database host.
[15 Jun 2010 0:14] Anderson Vitous 
Changing back to 'Open'
[22 Jun 2010 12:12] Alfredo Kojima 
In the Server Instance Profile, you have to set the host IP to the final DB machine, not the tunnel machine.
Open the Manage Server Instances editor and check if that info is the one you expect (not the DB connection, but the SSH Shell Connection).
[24 Jul 2010 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".