Bug #3895 | MySQL Admin reports wrong server status | ||
---|---|---|---|
Submitted: | 26 May 2004 9:38 | Modified: | 10 Jun 2004 6:08 |
Reporter: | Alexei Khalimov | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Administrator | Severity: | S2 (Serious) |
Version: | 1.0.2b-alpha | OS: | FreeBSD (FreeBSD 5.2-CURRENT 17 may 2004) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[26 May 2004 9:38]
Alexei Khalimov
[26 May 2004 9:39]
Alexei Khalimov
screenshot of connection to server via tcp/ip and status "Stopped"
Attachment: mysqladm.jpg (image/jpeg, text), 19.67 KiB.
[27 May 2004 7:44]
Alfredo Kojima
This problem appears under Linux in some cases too. I need to know where is the pid file for mysql located in your system to fix it.
[27 May 2004 8:19]
Alexei Khalimov
Here it is: DB_DIR=/var/db/mysql PIDFILE=${DB_DIR}/`/bin/hostname -s`.pid Note that /var/db/mysql is set to 700 and owned by "mysql" user. AL.
[10 Jun 2004 6:08]
Alfredo Kojima
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: The problem has been fixed (in the repository) by changing the method administrator uses to check whether the instance is up. The next release should have this working in any machine, but if it doesn't, please reopen the bug.