Bug #37293 Agent init script requires pid file absolute path for 'stop' to work
Submitted: 9 Jun 2008 20:53 Modified: 11 Jun 2008 22:08
Reporter: Marcos Palacios Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: BitRock Merlin CPU Architecture:Any

[9 Jun 2008 20:53] Marcos Palacios
The absolute path for the pid file is needed (in mysql-monitor-agent.ini) in order for the init script (etc/init.d/mysql-monitor-agent) to see the pid file UNLESS the script is run from the installation directory.

With the agent running, if we run the script from another directory, we get:

$ /Applications/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent stop
 ERROR! MySQL Enterprise agent PID file could not be found!

$ /Applications/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent status
MySQL Enterprise agent does not appear to be running

However, when we do a 'start' it works and creates the pid file:

$ /Applications/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent start
Starting MySQL Enterprise agent service...

How to repeat:
See description.
[9 Jun 2008 21:03] Keith Russell
Is this related to 37196?
[11 Jun 2008 15:14] BitRock Merlin
Patch sent to Keith
[11 Jun 2008 20:20] Keith Russell
Patch applied in agent versions =>
[11 Jun 2008 22:08] Marcos Palacios
Verified fixed in bld