MySQL Bugs: #54567: Opening SQL Editor throws OverviewBE::get

Bug #54567	Opening SQL Editor throws OverviewBE::get_node: invalid node 0.1.0
Submitted:	16 Jun 2010 20:48	Modified:	22 Jun 2010 16:44
Reporter:	John David	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.22.OSS.RC	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
It asked me to report a bug.
All I did was double click on the connection to fire up the editor.
I've seen this a couple of times and closing/restarting the editor seems to clear it.

100616 10:45:54 mysqld_safe mysqld from pid file /var/lib/mysql/anstaafl.pid ended
100616 10:46:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100616 10:46:11 [Note] Plugin 'FEDERATED' is disabled.
100616 10:46:11  InnoDB: Started; log sequence number 1 4024621143
100616 10:46:11 [Note] Event Scheduler: Loaded 0 events
100616 10:46:11 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.47-community-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)

BTW is there any way to shut off having the editor ask you if you want to save your sql?
A lot of times, I go into the database with queries and have no need or want to save anything.

How to repeat:
Not a clue.
It just happens (sometimes) when I start an Editor session on a database with all Innodb tables.

Thank you for the bug report. That's trying to connect with a remote Linux server?. Thanks in advance.

Yes.
It's a remote linux server running RHEL4 Update 8.

[root@anstaafl mysql]# cat /etc/redhat-release
Red Hat Enterprise Linux WS release 4 (Nahant Update 8)
[root@anstaafl mysql]# uname -a
Linux anstaafl 2.6.9-89.ELsmp #1 SMP Mon Apr 20 10:34:33 EDT 2009 i686 i686 i386 GNU/Linux

Old, decrepit OS, yes, I know but I'm stuck with it. (Sigh)
I'm vigorously lobbying to upgrade it to RHEL5 (just for the additional support).

Many thanks for writing a bug report.

This could be a server bug ... we need to know the error log and general log from server ... of course only the last entries.

We need to know which command that Workbench is sending to the server is responsible for the server crash.

Suzanne,

There are no errors posted in the server error log.
I get the startup message and that's pretty much it.
To give you a little background, this database is a test database.

It's a copy (not even a backup and restore) from a 4.1.12 server...
I stopped the server, untarred the files into /var/lib/mysql/dbname and restarted it.

mysql  Ver 14.7 Distrib 4.1.12, for redhat-linux-gnu (i386) using readline 4.3

It used to be entirely MyISAM tables and I was looking into what it would take to convert it to innodb with/using 5.1.47.

I looked back through the error log and there's nothing but the db startup message.
There are also old messages like the following which I believe comes from failed attampts at foreign key creation...

100611 14:19:34 [Warning] Invalid (old?) table or database name '#sql-6f4_b'

Could you let me know where the general log might be as it's not in /var/lib/mysql or /var/log.

I took a note for the "prevent editor from asking for saving the content on close" feature request.

I wish I could provide more info to you to track down the error.

As to my request for a "Do not Save" feature.

ThankyouThankyouThankyou...

A lot of times, I'm just going in to look at something or correct a record that an app didn't handle properly.  If I had say 5 or more editor windows open, exiting WorkBench becomes really tedious as you have to go through the save script dialogs over and over.

Please, check if this ever happens with a newer version, 5.2.24.

I will upgrade to 5.2.24 as soon as it becomes available.
Sorry about handing in a bug with no rca and no known way to reproduce it.
I'd throw this one in your equivalent of "Monitor" for now.

If there are any logging switches or anything else you'd like me to turn on, I'd be happy to.
As I said, this is a test database with no impact to our production environment.

Duplicates the bug #52648.