Bug #52198 Service name is not honoured in MEM agent installer details
Submitted: 19 Mar 2010 4:26 Modified: 14 Jun 2010 9:24
Reporter: Jonathon Coombes Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version:2.2 OS:Linux
Assigned to: BitRock Merlin CPU Architecture:Any
Tags: BitRock, installer, mem

[19 Mar 2010 4:26] Jonathon Coombes
The MEM 2.2 agent installer gives the option to specify your service script name. It defaults to 'mysql-monitor-agent' and recognises that the script already exists.

When the name is changed e.g. mysql-monitor-agent22, it continues the install and creates the new service script. However at the end of the agent installation, the installer says to activate the new install using 'mysql-monitor-agent' instead of the new service name.

This will not occur often, but if people want to run multiple agents, or to use their own naming convention, this could be a problem.

How to repeat:
Install MEM 2.2 agent and change the service script name from the default.

Suggested fix:
Change the installer to either use the modified service script name, or add documentation to the step to explain the change in name.
[19 Apr 2010 8:31] BitRock Merlin
The installer shows the following page at the end of the installation:

"The MySQL Enterprise Monitor Agent was successfully installed. To start the Agent please invoke:
/home/user/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent start"

This information is correct, the script name in "<installdir>/etc/init.d" folder is "mysql-monitor-agent" always. 

The script name that the user specified during the installation is for the script that it is installed at "/etc/init.d" folder. This is only valid if the installer has been started as root user.

Although the information is correct, a possible solution is to replace the text with the following lines:

"The MySQL Enterprise Monitor Agent was successfully installed. To start the Agent please invoke:
/etc/init.d/mysql-monitor-agent-2 start"

Notice that this information will only be shown if the installer has root privileges. Please let us know the best approach for you.
[21 Apr 2010 16:42] Andy Bang
That sounds like a good approach to us.
[22 Apr 2010 8:15] BitRock Merlin
Patch sent to Keith.
[23 Apr 2010 17:34] Enterprise Tools JIRA Robot
Andy Bang writes: 
In build
[26 Apr 2010 13:05] Enterprise Tools JIRA Robot
Carsten Segieth writes: 
build was svc mgr only --> QA is still waiting on an agent build that contains this fix
[3 Jun 2010 18:22] Enterprise Tools JIRA Robot
Carsten Segieth writes: 
checked OK in (GA)
[14 Jun 2010 9:24] MC Brown
A note has been added to the 2.2.0 changelog: 

        When performing an installation of &merlin_server; or                                                                            
        &merlin_agent; and specifying an alternative service name                                                                        
        during installation, the installer would recommend using the                                                                     
        generic, not custom, service management script to initiate the