Bug #40085 Agent installer does not recognise the socket file.
Submitted: 16 Oct 2008 16:02 Modified: 11 Nov 2008 14:59
Reporter: Matthew Montgomery Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version: OS:Linux
Assigned to: BitRock Merlin CPU Architecture:Any
Tags: agent socket

[16 Oct 2008 16:02] Matthew Montgomery
When going through the command line agent setup a socket file is not accepted for the monitored instance.

I am able to use the TCP port during the installer and manually change to using a socket file within agent-instance.ini file.

How to repeat:
MySQL Socket []: /tmp/mysql50.sock

MySQL Username []: root

MySQL Password :
Re-enter :
Warning: The specified path
is not a file
Press [Enter] to continue : 
Monitored Database Information

IMPORTANT: The agent user account specified below requires special MySQL privileges.

Visit the following URL for more information:

MySQL Socket [/tmp/mysql50.sock]: 
matt@bouchon:~/mysql/monitoring/merlin/2.0$ ls -l /tmp/mysql50.sock 
srwxrwxrwx 1 matt matt 0 2008-10-13 19:25 /tmp/mysql50.sock
[16 Oct 2008 17:35] Andy Bang
I see the same problem using the GUI installer on Linux.  I get a message saying:

"The specified path
is not a file."

I can connect with mysql --protocol=socket and --socket=/var/lib/mysql/mysql.sock, so it's working.

When I do an ls -l in /var/lib/mysql I see:

srwxrwxrwx 1 mysql mysql        0 Oct 16 10:25 mysql.sock

so it's there.
[17 Oct 2008 11:04] BitRock Merlin
Patch sent to Keith.
[17 Oct 2008 20:57] Keith Russell
Patch applied in version =>
[29 Oct 2008 2:50] Marcos Palacios
Verified fixed in build
[11 Nov 2008 14:59] Tony Bedford
An entry was added to the 2.0 changelog:

When using the command line agent setup program, a socket file was not accepted for the monitored instance.