MySQL Bugs: #50003: Server Administration crashes

Bug #50003	Server Administration crashes
Submitted:	30 Dec 2009 17:27	Modified:	5 Feb 2010 10:28
Reporter:	Markus Gschwendt	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.11 beta	OS:	Linux (Ubuntu 9.10 amd64)
Assigned to:	Maksym Yehorov	CPU Architecture:	Any
Tags:	crash server administration

Description:
WB crashes on opening an administration connection to a server.
in terminal: ** Message: function call error

double clicking an item in the list does nothing but some output in the terminal: ** Message: function call error

i will attache some output from terminal

"testing" the connection in "manage server instances" works
"open connection to start query" works

How to repeat:
open WB
choose "server administration"
select a server in the dialog
click "ok"

Suggested fix:
should open server admin connection and gui

terminal output on wb crash

Attachment: wb5.2.11beta-serveradmin-crash.txt (text/plain), 1.93 KiB.

terminal output on double click (no crash, gui does nothing)

Attachment: wb5.2.11beta-serveradmin-error.txt (text/plain), 1.76 KiB.

sorry, os version was wrong

How did you install Workbench?

Which script do you use for start/stop server?
Where is your my.cnf?

Is your server localhost or remote?

Did you disable/enable sudo?

How did you install Workbench?
.deb from mysql download site.

Is your server localhost or remote?
remote, mysql-server-5.0, 5.0.51a-3ubuntu5.4
server: ubuntu 8.04 LTS

sudo is enabled on server and client machine.

i just installed wb on my laptop (same package as above)

and figured out this bug might be an issue with the ssh feature.
because i wanted simply to administrate user and schema.
if i go through the wizard "new server instance" i can login but it says "server is not running". only the dump feature shows a mask which seems to be broken in some graphical way on my screen (1200x800, laptop).

if i manually configure the settings (ssh) like the instance created by the wizard, i get messages about entering an ssh password, missing ssh keys and non existing user. but i disabled ssh in the dialog.

Markus,

I am not able to follow you totally.

When you will google or search here in our bug system for Workbench bugs and search word ssh key then you will figure out we have tons of problems at the moment with ssh key.

I first thought your bug here is a duplicate.

But you said you disabled ssh.

And my question now is ... how will you be able to edit my.cnf or something like this without ssh?

How will you read/write/execute files on your remote server when you don't use Workbench?

The only little bit senseful alternative I have in my mind would be mounting the filesystem from remote server. But then server would be local and not remote anymore.

sorry, i don't understand why you are asking about my.cnf. i'm talking about workbench. did i miss something? does wb need a my.cnf?

i will provide some screenshots, maybe it's hard to explain what i did on which place in workbench.

settings after creating instance with 'new server instance' wizard. ssh disabled.

Attachment: Screenshot-Manage_Server_Instances.png (image/png, text), 58.73 KiB.

settings after creating instance manually 'manage server instances'. ssh disabled.

Attachment: Screenshot-Manage_Server_Instances_manual.png (image/png, text), 61.16 KiB.

Markus,

does workbench needs my.cnf?
Yes and No.
The server works without but we have some bugs on topic my.cnf and workbench.
I want to make sure that you didn't just run into one of these.

But why did I ask you about ssh and my.cnf?

Very easy answer ...

What is the administrator section doing? Some ad-hocs:
- start/stop the server
- changing configure values
- dumping/restoring
- my dream would be: cooking coffee

Honestly, how does this work? How are you doing all this stuff without a graphical interface?

1) you connect to the server machine ... usually via ssh

And all the rest you will do in this remote shell e.g.:
$ sudo /etc/init.d/mysql start
$ vi /etc/mysql/my.cnf
$ mysqldump blabla

Ok, we could fight if mysqldump should be executed on server or client machine but all the rest ... you need to do on server machine.

Also already checking if server is running or not ... you need to ask on server machine.

Our development just chose ssh here for connecting. I think you agree that ssh is a better choice then telnet or so.

But back to the topic:

MySQL server 5.0 died last year (End of Life).

Workbench only support server 5.1 at the moment.

I have homgene Ubuntu here too ... 9.04/9.10 and couldn't repeat your problem.

So, I fear it is either related to the server version or to ssh.

Or to your python version .... 2.6 should work.

In any case it shouldn't crash but I am unable to figure out why it is crashing without being able to repeat it.

Ok, Susanne, but i don't need ssh for operations on databases and tables. 

MySQL Server 5.0...
That's the latest in the Ubuntu 8.10 LTS repos.
Maybe i should file a report about the end of life of on launchpad.
I think, such packages should be more up to date on a LTS version of a distro.

python is 2.6.4 on the desktop machine (ubuntu 9.10)

Markus,

that is crazy ....

Asking Synaptic I will get MySQL 5.1 asking apt-cache search mysql I will only get MySQL 5.0.

It really seems that Ubuntu is making something weird here.

Anyway, I need to know if you have same problems by using MySQL 5.1.

searching mysql-server: are you on ubuntu server, 64bit, 8.04 LTS? i don't have synaptic on a server.
i get 5.1 on karmic and 5.0 on 8.04 LTS, even with apt-cache.
but in april we should get a new LTS release.

sorry, next 5 weeks i have not the time to install mysql-server 5.1 on the server, and i have only the production machine to test wb against a server at the moment.

Markus,

take your time. I will let this in status open until you will answer.

Can't repeat with latest sources.

seems to be solved in 5.2.15, even with old server version 5.0.

but the only tab which is usable is "data dump" all others are schowing: "server is not running", but this might be a different bug to be reported.

thanks!

Many thanks for your feedback. I will close this bug report now.