Bug #52648 Workbench OverviewBE::get_node:invalid node 0.0.0
Submitted: 7 Apr 2010 8:54 Modified: 20 Sep 2010 13:12
Reporter: Tony Walker Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.17 OSS, 5.2.25, 5.2.26 CE OS:Windows (XP SP3)
Assigned to: Alfredo Kojima CPU Architecture:Any

[7 Apr 2010 8:54] Tony Walker
Description:
When opening a SQL editor connection for a remote server, I received the error OverviewBE::get_node:invalid node 0.0.0. No table overview was displayed. This happened twice in a row.
Without closing Workbench, I opened a local server SQL editor with no issues.
When I opened the remote server SQL editor again, it worked.

No intricate details of the error can be reported, as it's stopped happening.

The remote server was on a machine over a fixed VPN, using standard TCP/IP, to port 5036, using root (so nothing untoward there - this matches the MySQL DB setup on the remote server). No compression was in use when this error occurred.

The version information is:
x32 on x32Checked server status: Server is running.get_server_version: parsed (5, 1, 37)
MySQL Workbench OSS for Windows version 5.2.17
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 1.5.0 - Build 6.14.10.4873
OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)
CPU: 2x Intel(R) Core(TM)2 Duo CPU     T5670  @ 1.80GHz, 2.0 GiB RAM
Video adapter info:
Adapter type: Mobile Intel(R) 965 Express Chipset Family
Chip Type: Mobile Intel(R) 965 Express Chipset Family
BIOS String: Intel Video BIOS
Video Memory: 393216 KB

How to repeat:
I can't repeat it at the moment - whatever caused the issue is now gone.
[7 Apr 2010 8:57] Tony Walker
Forgot to mention:
MySQL DB version: 5.1.45-community.
[7 Apr 2010 10:47] MySQL Verification Team
Thank you for the bug report. I couldn't repeat please re-open this bug report if you will able to provide instructions step by step and repeatable behavior. Thanks in advance.
[22 Jun 2010 16:41] Sergei Tkachenko
Managed to repeat. This is a race condition issue. It's expected to be fixed now.
[24 Jun 2010 9:00] Mike Lischke
Since this is a bug produced by a race condition it is hard to verify it happens or, after fix, that it really is fixed. However, I had a special case (when deleting objects) where I frequently saw this error, which now is gone. So I have a strong feeling this problem is solved. Hence I close the report.

If it turns out there is still some hidden issue with that then please create a new bug report.
[24 Jun 2010 9:02] Tony Walker
FYI, refreshing the table data most times ensures that the overview is displayed, so I tend to agree with the prognosis of a race condition.
Thanks for all your work - I appreciate it!
[24 Jun 2010 14:15] Alfredo Kojima
Set bug #54777 as duplicate
[29 Jun 2010 13:36] Tony Bedford
An entry has been added to the 5.2.25 changelog:

When a SQL Editor connection for a remote server was opened, the following error was generated:

OverviewBE::get_node:invalid node 0.0.0.
[14 Jul 2010 6:24] Gautam Murugesh
I recently upgraded from 5.2 OSS Beta to 5.2.25CE and mow get the invalide node 0.1.1 error every time I stat up a connection to my remote server. This never happened earlier.
[14 Jul 2010 7:23] Tony Walker
Confirmed I still get the issue, but it's intermittent. Mostly 2 out of the 3 times it's happened) this is resolved by pressing the refresh button. Once I had to disconnect and reconnect to resolve the issue.
[20 Jul 2010 8:55] Roel Van de Paar
Issue still seems to be happening. 

See also bug #55389
[22 Jul 2010 6:03] Susanne Ebrecht
The following bug reports are duplicates of this bug here:

bug #54622
bug #54777
bug #55133
bug #55279
bug #55259
bug #55346
bug #55380
bug #55417
bug #55431
[22 Jul 2010 7:08] Susanne Ebrecht
Bug #55469 is set as duplicate of this bug here.
[22 Jul 2010 20:55] MySQL Verification Team
Bug http://bugs.mysql.com/bug.php?id=55380 duplicate of this one.
[26 Jul 2010 10:21] Johannes Taxacher
Bug #55533 has been marked as duplicate of this one
[27 Jul 2010 20:27] Alfredo Kojima
marked bug #55590
[30 Jul 2010 9:24] Roel Van de Paar
Marked as duplicates of this one: bug #55632 | bug #54529

Seeing:
OverviewBE::get_node:invalid node 0.0.0
OverviewBE::get_node:invalid node 0.0.1
OverviewBE::get_node:invalid node 0.0.2
[30 Jul 2010 11:09] Johannes Taxacher
Bug #55628 has been marked as a duplicate of this one
[2 Aug 2010 17:26] Johannes Taxacher
Bug #55695 has been marked as duplicate of this one
[2 Aug 2010 18:03] Johannes Taxacher
sorry, typo in my previous comment: 
Bug #55694 is a duplicate of this one
[2 Aug 2010 21:17] Johannes Taxacher
Bug #55682 marked as duplicate of this one
[4 Aug 2010 10:52] Susanne Ebrecht
Bug #55728 has marked as duplicate of this bug here
[4 Aug 2010 14:30] MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=55746 marked as duplicate of this one.
[4 Aug 2010 17:01] Alfredo Kojima
There is a test binary of the next release, with a potential fix for this issue included here: ftp://ftp.mysql.com/pub/mysql/download/gui-tools/mysql-workbench-gpl-5.2.26pre3-win32-noin...

Please try that binary and see if you can repeat this issue.
[5 Aug 2010 8:02] Roel Van de Paar
Marked as duplicates of this one: bug #55253 | bug #54974 | bug #55009 | bug #54970 | bug #53680 | bug #55253 | bug #55485 | bug #55640 | bug #55667 | bug #55489 | bug #54774

Also seeing: 
OverviewBE::get_node:invalid node 0.1.0
OverviewBE::get_node:invalid node 0.2.0
OverviewBE::get_node:invalid node 0.6.1
[9 Aug 2010 12:18] Johannes Taxacher
Bug #55781 has been marked as duplicate of this one
[10 Aug 2010 6:52] Susanne Ebrecht
Bug #55420 is set as duplicate of this bug here.
[10 Aug 2010 6:53] Susanne Ebrecht
Bug #55858 is set as duplicate of this bug here.
[10 Aug 2010 7:29] Susanne Ebrecht
Bug #55872 is set as duplicate of this bug here
[10 Aug 2010 12:44] Susanne Ebrecht
Bug #55879 was marked as duplicate of this bug here.
[11 Aug 2010 15:06] [ name withheld ]
Still a bug in 5.2.26, although the error message is now "Invalid node index".
[12 Aug 2010 12:10] Susanne Ebrecht
Bug #55943 was set as duplicate of this bug here.
[13 Aug 2010 12:44] Johannes Taxacher
Bug #55913 has been marked as duplicate of this one
[13 Aug 2010 15:50] Johannes Taxacher
Bug #55967 has been marked as duplicate of this one
[16 Aug 2010 9:10] Johannes Taxacher
Bug #55985 has been marked as duplicate of this one
[16 Aug 2010 13:05] Johannes Taxacher
Bug #56011 has been marked as duplicate of this one
[16 Aug 2010 15:11] Johannes Taxacher
Bug #56018 has been marked as duplicate of this one
[17 Aug 2010 15:20] Johannes Taxacher
Bug #56039 has been marked as duplicate of this one
[17 Aug 2010 18:20] MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=56056 marked as duplicate of this one.
[18 Aug 2010 16:23] MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=56090 marked as duplicate of this one.
[20 Aug 2010 10:04] Johannes Taxacher
Bug #56135 has been marked as duplicate of this one
[23 Aug 2010 11:38] Johannes Taxacher
Bug #56160 has been marked as duplicate of this one
[25 Aug 2010 14:27] Johannes Taxacher
Bug #56252 has been marked as duplicate of this one
[25 Aug 2010 15:16] Tony Walker
I recently updated to 5.2.26.
I have yet to experience this problem since I upgraded (I've connected to remote servers 5 times today, including ones that have previously given me this error) so perhaps a final fix came through with this last release? Any comments from others that confirm/deny this?
[25 Aug 2010 23:28] MySQL Verification Team
See http://bugs.mysql.com/bug.php?id=56272.
[26 Aug 2010 13:58] Johannes Taxacher
Bug #56290 has been marked as duplicate of this one
[28 Aug 2010 10:37] Sveta Smirnova
Bug #55389 was marked as duplicate of this one.
[30 Aug 2010 11:07] Johannes Taxacher
Bug #56339 has been marked as duplicate of this one
[30 Aug 2010 11:11] Johannes Taxacher
Bug #56341 has been marked as duplicate of this one
[31 Aug 2010 13:42] Alfredo Kojima
marked bug #56407 as duplicate
[31 Aug 2010 15:37] Alfredo Kojima
marked bug #56409 as duplicate
[31 Aug 2010 15:44] Tony Walker
Confimed that the bug still affects the latest version of the Workbench (5.2.26CE). 
The problem appears to remain the same (i.e. it only occurs on first opening of the remote connection) as does the resolution (close the connection and reopen). The error message seems to be slightly changing as time goes by, however (all variations on the "node" theme).
It also seems to only affect me when I first open Workbench, and my first connection is a remote one. After I fix the first one, it doesn't seem to matter whether I close or reopen workbench - it seems to work first time after that.

Was that any help?
[1 Sep 2010 13:37] Alfredo Kojima
WB 5.2.27 has some additional fixes attempting to address this issue, please try and see if it resolves it.
[10 Sep 2010 5:51] Alfredo Kojima
I think this can be closed as there has been no signs of this bug since 5.2.27 was released.
[15 Sep 2010 11:16] Johannes Taxacher
Bug #56773 has been marked as duplicate of this one
[16 Sep 2010 19:13] Johannes Taxacher
can be closed as fixed in 5.2.27
[20 Sep 2010 13:13] Tony Bedford
Changelog modified to note that fix for #52648 went into 5.2.27
[14 Oct 2010 10:27] Johannes Taxacher
Bug #57444 has been marked as duplicate of this one
[12 Nov 2010 12:34] Johannes Taxacher
Bug #58161 has been marked as duplicate of this one
[17 Nov 2010 14:44] Johannes Taxacher
Bug #58252 has been marked as duplicate of this one
[18 Nov 2010 8:03] Johannes Taxacher
Bug #58276 has been marked as duplicate of this one