Bug #27995 /etc/init.d/mysql have too scarce error reporting

• Submitted: 21 Apr 2007 0:21
• Modified: 10 Jan 2008 13:38
• Reporter: Mads Martin Joergensen
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.0
• OS: Any
• Assigned to: Jonathan Perkin
• CPU Architecture: Any

[21 Apr 2007 0:21] Mads Martin Joergensen

Description:
If the initscript cannot start mysql due to not finding the binaries, the error message simply is:

Couldn't find MySQL manager or server

How to repeat:
Use a bad basedir

Suggested fix:
--- mysql.init.orig     2007-04-21 02:13:23.000000000 +0200
+++ mysql.init  2007-04-21 02:15:00.000000000 +0200
@@ -311,7 +311,7 @@
       fi
       exit $return_value
     else
-      log_failure_msg "Couldn't find MySQL manager or server"
+      log_failure_msg "Couldn't find MySQL manager at $manager or server at $bindir/mysqld_safe"
     fi
     ;;

[5 Nov 2007 16:48] Jonathan Perkin

Fix committed in http://lists.mysql.com/commits/37108

[10 Jan 2008 13:38] Paul DuBois

No changelog entry needed.