MySQL Bugs: #40085: Agent installer does not recognise the socket file.

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:	None
Category:	MySQL Enterprise Monitor: Installing	Severity:	S3 (Non-critical)
Version:	2.0.0.7071	OS:	Linux
Assigned to:	BitRock Merlin	CPU Architecture:	Any
Tags:	agent socket

Description:
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
/tmp/mysql50.sock
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:
https://enterprise.mysql.com/docs/monitor/2.0/en/mem-install.html#mem-agent-rights

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

I see the same problem using the GUI installer on Linux.  I get a message saying:

"The specified path
/var/lib/mysql/mysql.sock
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.

Patch sent to Keith.

Patch applied in version => 2.0.0.7078.

Verified fixed in build 2.0.0.7085.

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.