MySQL Bugs: #50785: Workbench Server Admin for freeBSD doesn't work

Bug #50785	Workbench Server Admin for freeBSD doesn't work
Submitted:	1 Feb 2010 9:54	Modified:	13 May 2010 22:53
Reporter:	Max Gaga	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.15	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	freebsd, server admin, wrong commands

Description:
when creating a new server instance selecting freeBSD it shows up as type LINUX.
The commands for "MySQL Management" and "Server Status" are plain wrong and the server shows up as not working (only the connection works).

How to repeat:
Create a freeBSD server connection

Suggested fix:
Adopt the commands

Thank you for the problem report. Verified just as described. Indeed, /etc/init.d/mysql is a wrong script to use in case of FreeBSD.

Hi

Could someone please provide the correct values to use for FreeBSD?

admin template file for FreeBSD

Attachment: FreeBSD_(MySQL_Package).xml (application/xml, text), 635 bytes.

Please replace the file Ive uploaded with the same name file that was shipped and see if it works.
If it does not, please provide the correct values so we can include them.

I've installed the xml-file. 
After restarting workbench and selecting the instance in the GUI I get an error-msg in the browser statusbar: "could not connect to target database: error calling WbAdmin.openAdministrator: see output for details".

How can I check the output?

Alfredo,

on FreeBSD it is /usr/local/etc/mysql-server start/stop

okay, maybe I'm too dumb to handle this program...
If I select "output window" in the HOME screen nothing happens, and I have to start the connection of "server administration" in the home screen. 
Therefore: no output window!

Hi Can you confirm whether the problem persists with the latest 5.2.17/18 release?
They have updated profiles for FreeBSD

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".