Bug #51087 error calling wbAdmin.openAdministrator: IndexError: list index out of range
Submitted: 11 Feb 2010 11:40 Modified: 19 Feb 2010 15:57
Reporter: Greg Thomas Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.15 Revision 5053 OS:Any
Assigned to: CPU Architecture:Any

[11 Feb 2010 11:40] Greg Thomas
Description:
I've a Windows 2003 Server running MySQL 5.1.40 with a Cygwin sshd installed. 

I have enabled SSH login based administration for that server under Server Administration in the Workbench.

When I try to administer that server, the message

Could not connect to target database: error calling wbAdmin.openAdministrator: see output for details

appears in the status bar.

The output window contains the following:

Connected via ssh to xxx.xxx.xxx.xxx
Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line 133, in openAdministrator
    do_open_administrator(server_instance)
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line 109, in do_open_administrator
    adminTab = AdministratorTab(server_instance)
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line 70, in __init__
    self.ctrl_be = wb_admin_control_be.MyCtrl(server_instance_settings)
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_control_be.py", line 471, in __init__
    self.cmd_output_encoding = "cp" + result.strip(" .").split()[-1]
IndexError: list index out of range

How to repeat:
1. Install MySQL on Windows 2003.

2. Install Cygwin based OpenSSH server on Windows 2003 (http://www.netadmintools.com/art516.html)

3. Create a new server instance in Workbench for that server. Enable SSH login based authentication.

4. Attempt to administer that server.
[19 Feb 2010 11:45] Susanne Ebrecht
Can you connect to the server machine via ssh without workbench?
[19 Feb 2010 13:46] Greg Thomas
Yes; when I ssh I'm in a bash shell in a cygwin environment.
[19 Feb 2010 15:57] Greg Thomas
I've just retried this with 5.2.16, and I'm no longer getting this error. I'm guessing it was fixed in the latest build. 

OK, I've still got problems, but I think this bug can now be closed.