Bug #54647 exec_cmd() takes at least 3 arguments (2 given)
Submitted: 20 Jun 2010 23:31 Modified: 11 Aug 2010 15:36
Reporter: Brad Waite Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.22 OS:Windows (Windows 7 64-bit)
Assigned to: Maksym Yehorov CPU Architecture:Any

[20 Jun 2010 23:31] Brad Waite
Description:
When trying to Apply Changes to MySQL Configuration File to  a FreeBSD 7.1 host over ssh, I get the following error:

Could not Save Configuration File

There was an error saving the configurationfile: exec_cmd() takes at least 3 arguments (2 given)

System Info:

get_server_version: parsed (5, 1, 33)
MySQL Workbench OSS for Windows version 5.2.22
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 2.1.2
OS: Microsoft Windows 7 Ultimate Edition (build 7600), 64-bit
CPU: 2x Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz, 4.0 GiB RAM
Video adapter info:
Adapter type: NVIDIA GeForce 7600 GT 
Chip Type: GeForce 7600 GT
BIOS String: Version 5.73.22.51.1
Video Memory: 262144 KB
Exception in SSH Socket is closed
Traceback (most recent call last):
  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 OSS\modules\wb_admin_ssh.py", line 310, in exec_cmd
    stdin.write(pwd)
  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 OSS/python/site-packages\paramiko\file.py", line 314, in write
    self._write_all(data)
  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 OSS/python/site-packages\paramiko\file.py", line 435, in _write_all
    count = self._write(data)
  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 OSS/python/site-packages\paramiko\channel.py", line 1211, in _write
    self.channel.sendall(data)
  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 OSS/python/site-packages\paramiko\channel.py", line 762, in sendall
    raise socket.error('Socket is closed')
error: Socket is closed

How to repeat:
Change any configuration parameter->Apply...->Apply
[21 Jun 2010 21:57] MySQL Verification Team
Thank you for the bug report. Are you able to connect with remote server using the mysql.exe client?. Thanks in advance.
[21 Jun 2010 22:54] Brad Waite
mysql.exe connects with no problem using the -h, -u & -p options.
[22 Jun 2010 8:11] Susanne Ebrecht
Please attach your configuration:
connections.xml
server_instances.xml
[24 Jun 2010 13:39] Brian Kelley
This bug also affects me (in exactly the same way).

My computer details are a tad different:

MySQLWB Version: 5.2.24
Windows: XP Pro 32-bit

I've attached my connections.xml and server-instances.xml above. The two target operating systems are Solaris 10 and Ubuntu 10.04 Server.
[29 Jun 2010 8:51] Susanne Ebrecht
Did you overtake your configuration from older Workbench versions?
[29 Jun 2010 8:57] Susanne Ebrecht
Do you have same problems by using actual Workbench version 5.2.24 RC?
[29 Jun 2010 14:44] Brian Kelley
I cannot speak for the original poster, but I installed MySQLWB 5.2.24 CE RC Rev 6246 from scratch and configured it. It was the first version of MySQLWB I've ever had.
[29 Jun 2010 15:44] Brad Waite
Yes, I am using the same config as in previous Workbench versions.

I'll try 5.2.24 and report back.
[29 Jun 2010 15:48] Brad Waite
No change on 5.2.24.
[29 Jun 2010 18:04] Maksym Yehorov
Brad,

Problem found and fixed. Thanks for the report.
You can either wait till next release, or fix the issue yourself.
To fix yourself:
1.Find in the directory, where Workbench is installed, file named wb_admin_control_be.py
2.At line #883 of the found file add boolean False argument to the end of exec_cmd call. See below:
  Before:
     self.exec_cmd("/bin/rm " + dirname.strip(" \r\t\n") + "/workbench-temp-file")
  After:
     self.exec_cmd("/bin/rm " + dirname.strip(" \r\t\n") + "/workbench-temp-file", False)
3. That is it.

If you decide to fix yourself, please tell us if that helped via this bug report.

Thanks!
[1 Aug 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".
[2 Aug 2010 14:27] Brian Kelley
I have tried the fix described above, and it works on MySQLWB v5.2.24. I cannot change the status on the bug because I am not the original poster.
[11 Aug 2010 15:36] Tony Bedford
An entry has been added to the 5.2.24 changelog:

In the Configuration tab of the Administrator, after changes were applied an error was generated:

Could not Save Configuration File

There was an error saving the configurationfile: exec_cmd() takes at least 3 arguments (2
given)

This happened while connecting to a FreeBSD 7.1 server over an SSH connection.