| Bug #59965 | MySQL Work Bench Statistics WMI poll errorr (output included) | ||
|---|---|---|---|
| Submitted: | 5 Feb 2011 15:33 | Modified: | 14 Jul 2011 15:26 |
| Reporter: | Erwin de Haan | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench: Administration | Severity: | S2 (Serious) |
| Version: | 5.2.31, 5.2.33b | OS: | Windows (7 x64; XP x64) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Stats Graphes, WMI Query Error | ||
[5 Feb 2011 15:33]
Erwin de Haan
[5 Feb 2011 15:35]
Erwin de Haan
Screenshot of the empty graphs.
Attachment: mysqlworkbencherrorrscreenshot.png (image/x-png, text), 23.51 KiB.
[5 Feb 2011 15:38]
Erwin de Haan
Also adding users as stated in an older bug report also doesn't work. It seems that the WMI implemetation is failing, no offense.
[7 Feb 2011 17:17]
MySQL Verification Team
I couldn't repeat on Vista 64-bit.
[13 Feb 2011 14:06]
Valeriy Kravchuk
Was this new installation of 5.2.31 or you upgraded from some older version and use existing instances?
[13 Feb 2011 17:08]
Erwin de Haan
Mmm I cant really remember. I think it's an upgrade but I'm not sure. Should I try to re-install?
[16 Feb 2011 10:51]
MySQL Verification Team
Yes try to re-install. Thanks in advance.
[16 Feb 2011 15:56]
Erwin de Haan
After re-install this is the output:
WMIShell: Set filters for local windows cli
Exception in thread Thread-2:
Traceback (most recent call last):
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\python\threading.py", line 525, in __bootstrap_inner
self.run()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\python\threading.py", line 477, in run
self.__target(*self.__args, **self.__kwargs)
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 642, in poll_sources
cmd.poll()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 531, in poll
value = self.query(wmi_session, 'PercentProcessorTime', "SELECT PercentProcessorTime FROM Win32_PerfFormattedData_PerfOS_Processor WHERE Name = '_Total'")
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 513, in query
res = self.wmi.wmiQuery(session, query)
SystemError: Workbench.wmiQuery(): WMI query execution failed.
Ongeldige klasse
I guess this is the same error.
[26 Feb 2011 23:28]
Don Cook
I also have this problem on Windows XP x64.
Today I did a new install of mysql-workbench-gpl-5.2.31a-win32.msi.
After setup I tried to create a new account which failed with an error dialog of "Unhandled exception: Error adding account <xxxxxx>".
I cleared the log and restarted the database and I noticed the same information in the output down to and include the "Invalid class" line.
<pre>
WMIShell: Set filters for local windows cli
Exception in thread Thread-2:
Traceback (most recent call last):
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\python\threading.py", line 525, in __bootstrap_inner
self.run()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\python\threading.py", line 477, in run
self.__target(*self.__args, **self.__kwargs)
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 642, in poll_sources
cmd.poll()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 531, in poll
value = self.query(wmi_session, 'PercentProcessorTime', "SELECT PercentProcessorTime FROM Win32_PerfFormattedData_PerfOS_Processor WHERE Name = '_Total'")
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 513, in query
res = self.wmi.wmiQuery(session, query)
SystemError: Workbench.wmiQuery(): WMI query execution failed.
Invalid class
Option verbose skipped because of missing value
Option standalone skipped because of missing value
Option one-thread skipped because of missing value
Option des-key-file skipped because of missing value
Option innodb_rollback_on_timeout skipped because of missing value
Option slave-skip-errors skipped because of missing value
Option large-pages skipped because of missing value
Option bootstrap skipped because of missing value
ctrl_be: Query Error Error executing 'Field 'authentication_string' doesn't have a default value'
INSERT INTO mysql.user (User, Host, Password, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv, Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv, Execute_priv, Repl_slave_priv, Repl_client_priv, Create_view_priv, Show_view_priv, Create_routine_priv, Alter_routine_priv, Create_user_priv, Event_priv, Trigger_priv, Create_tablespace_priv, max_questions, max_updates, max_connections, max_user_connections, ssl_cipher, x509_issuer, x509_subject) VALUES ('<xxxxxx>', '%', PASSWORD('<xxxxxx>'), 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 0, 0, 0, 0, '', '', '').
SQL Error: 1364
Traceback (most recent call last):
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_security.py", line 628, in commit
self._selected_user.save()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_security_be.py", line 656, in save
raise Exception("Error adding account %s@%s: %s"%(self.username, self.host, e))
Exception: Error adding account <xxxxxx>:
</pre>
[26 Feb 2011 23:32]
Erwin de Haan
added XP x64 to description
[27 Feb 2011 0:33]
Don Cook
I hope this doesn't cloud the issue but,...
I uninstalled the 5.2.31a, removed all the files still left in the folder, and installed mysql-workbench-gpl-5.2.27-win32.msi which I previously had running on another machine with WXP32.
When I selected Manage Security on the Home tab, and selected the local instance, an error poped up in the status bar area that said (including typo):
"Error in sercurityManager module: error calling WbAdmin.openSecurityManager: see output for details"
I believe this is the same thing that 5.2.31a said, possibly without the typo.
The output with 5.2.27 is different and is below, but is there a version that will run in 32-bit mode on x64?
Traceback (most recent call last):
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 288, in openSecurityManager
tab = do_open_administrator(server)
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 144, in do_open_administrator
adminTab = AdministratorTab(server_instance)
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 90, in __init__
self.ctrl_be = wb_admin_control_be.MyCtrl(server_instance_settings)
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_control_be.py", line 548, in __init__
self.remote_admin_enabled = int(self.settings.serverInfo["remoteAdmin"]) != 0 and not disable_remote_admin
TypeError: int() argument must be a string or a number, not 'NoneType'
[27 Feb 2011 11:03]
Erwin de Haan
mmm this is getting weird...
[12 May 2011 16:12]
Alfredo Kojima
Please try with 5.2.33b and report if the problem persists
[12 Jun 2011 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".
[13 Jun 2011 9:50]
Erwin de Haan
Well same problem occurs in revision 7508:
maybe different output:
WMIShell: Set filters for local windows cli
Exception in thread Thread-2:
Traceback (most recent call last):
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\python\threading.py", line 525, in __bootstrap_inner
self.run()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\python\threading.py", line 477, in run
self.__target(*self.__args, **self.__kwargs)
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 660, in poll_sources
cmd.poll()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 548, in poll
value = self.query(wmi_session, 'PercentProcessorTime', "SELECT PercentProcessorTime FROM Win32_PerfFormattedData_PerfOS_Processor WHERE Name = '_Total'")
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 530, in query
res = self.wmi.wmiQuery(session, query)
SystemError: Workbench.wmiQuery(): WMI query execution failed.
Ongeldige klasse
Note: this server is a local instance. I haven';t tried using and non-local instance. I can try if I find some time.
[14 Jun 2011 4:41]
Valeriy Kravchuk
What about 5.2.34?
[14 Jun 2011 13:19]
Erwin de Haan
ok i deinstalled .33 and installed .34 (rev 7780)
output:
WMIShell: Set filters for local windows cli
Exception in thread Thread-2:
Traceback (most recent call last):
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\Python\Lib\threading.py", line 530, in __bootstrap_inner
self.run()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\Python\Lib\threading.py", line 483, in run
self.__target(*self.__args, **self.__kwargs)
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 666, in poll_sources
cmd.poll()
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 554, in poll
value = self.query(wmi_session, 'PercentProcessorTime', "SELECT PercentProcessorTime FROM Win32_PerfFormattedData_PerfOS_Processor WHERE Name = '_Total'")
File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wba_monitor_be.py", line 536, in query
res = self.wmi.wmiQuery(session, query)
SystemError: Workbench.wmiQuery(): WMI query execution failed.
Ongeldige klasse
so pretty much the same.
[14 Jun 2011 15:26]
Armando Lopez Valencia
Hello Erwin. Can you please try with our zip version (http://dev.mysql.com/downloads/mirror.php?id=402744) and unzip it in c:\. Also, do you have any distribution on python installed in your machine? Thanks.
[14 Jul 2011 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".
