Bug #40995 Agent update installer does not update the agent log file name
Submitted: 24 Nov 2008 20:59 Modified: 11 Dec 2008 14:19
Reporter: Marcos Palacios Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version:2.0.0.7102 OS:Any
Assigned to: BitRock Merlin CPU Architecture:Any

[24 Nov 2008 20:59] Marcos Palacios
Description:
The version 2.0 agent's log file name is "mysql-monitor-agent.log"; however, when a 1.3 agent is upgraded to 2.0, the agent log file name is still named "mysql-service-agent.log" (notice the *service* part in the name).

How to repeat:
- install a 1.3 agent
- update the agent to version 2.0
- observe the log file name

Suggested fix:
Use the new name for the log file.
[27 Nov 2008 14:18] BitRock Merlin
Patch sent to Keith.
[3 Dec 2008 3:18] Keith Russell
Patch installed in versions => 2.0.0.7112.
[3 Dec 2008 23:38] Marcos Palacios
Verified fixed in build 2.0.0.7112.
[11 Dec 2008 14:19] MC Brown
Documentation has been updated, and a note about the log file name changed has been added to the changelog.