Bug #30071 MySQL connection information needs tweaking in configuration report

• Submitted: 26 Jul 2007 14:50
• Modified: 28 Aug 2007 15:08
• Reporter: Mark Leith
• Status: Closed
• Category: MySQL Enterprise Monitor: Installing
• Severity: S3 (Non-critical)
• Version: 1.2.0
• OS: Any
• Assigned to: BitRock Merlin
• CPU Architecture: Any

[26 Jul 2007 14:50] Mark Leith

Description:
The dashboard "configuration report" is inaccurate. It says: 

"Use the following command to login to the Monitoring and Advisory 
 Service database: mysql -uservice_manager -pxxx -P3306"

What is missing, so that this works, is either the socket location or a '-h127.0.0.1'.

How to repeat:
Try to connect to the installed MySQL server with the connection parameters defined. 

Suggested fix:
Add either:

-h 127.0.0.1
-S /path/to/mysql/tmp/mysql.sock

[26 Jul 2007 22:14] BitRock Merlin

Patch sent to Keith

[31 Jul 2007 3:24] Keith Russell

Patch installed in versions => 1.2.0.6839

[28 Aug 2007 15:08] Peter Lavin

Noted in the docs.