Bug #51404 | Workbench shows incorrect server status when SSH is NOT configured | ||
---|---|---|---|
Submitted: | 22 Feb 2010 21:20 | Modified: | 23 Feb 2010 17:49 |
Reporter: | Tony Leding | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
Version: | 5.2.18 | OS: | MacOS |
Assigned to: | CPU Architecture: | Any | |
Tags: | admin, mac, osx, server, workbench |
[22 Feb 2010 21:20]
Tony Leding
[23 Feb 2010 8:06]
Susanne Ebrecht
Many thanks for writing a bug report. Unfortunately, without ssh the "ps" command is not able to work. This is not a bug.
[23 Feb 2010 17:49]
Tony Leding
Hmmm - that's not true - the ps command does not require SSH to be executed. I have done this literally thousands of times on boxes that only have telnet enabled and no SSH. I only gave the ps command example as a means of testing to make sure the server was down but I had no idea it is the actual mechanism used by WB to check the server state. I had assumed, possibly wrongly so, that WB would use the same mechanism to check server state remotely as it does locally which does not require SSH. Can you please clarify how WB checks server state when connected remotely? If it currently does use SSH, can this not be changed? Thanks.