Bug #52216 agent update installer creates wrong 'agent-mgmt-username = ...' entry in .ini
Submitted: 19 Mar 2010 12:55 Modified: 26 Mar 2010 12:57
Reporter: Carsten Segieth Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Installing Severity:S2 (Serious)
Version:2.2.0.1651 OS:Any
Assigned to: BitRock Merlin CPU Architecture:Any

[19 Mar 2010 12:55] Carsten Segieth
Description:
During an update from 2.1.0.1093(GA) to 2.2.0.1651 the value 'agent-mgmt-username' is not created correct from the 'agent-mgmt-hostname' in the existing install. The following samples are all created with the same settings for user and password:

# 2.1.0.1093 fresh install
agent-mgmt-hostname = http://uuuu%40agent:pppp%40agent@qa-merlin.mysql.com:48080/heartbeat

# after update 2.1.0.1093 to 2.2.0.1651
agent-mgmt-hostname = http://qa-merlin.mysql.com:48080/heartbeat
agent-mgmt-username = agent
agent-mgmt-password = pppp@agent

# 2.2.0.1651 fresh install
agent-mgmt-hostname = http://qa-merlin.mysql.com:48080/heartbeat
agent-mgmt-username = uuuu@agent
agent-mgmt-password = pppp@agent

Work around:
------------
After updating the agent installaation edit the .ini file and fix the wrong password.

How to repeat:
- install 2.1.0.1093:    mysqlmonitoragent-2.1.0.1093-windows-installer.exe --installdir D:\Merlin\inst\agent\2.1.0.1093\winxp\IBM --mysqlhost 127.0.0.1 --mysqlport 3351 --mysqluser agent --mysqlpassword mysql --checkmysqlhost yes --managerhost qa-merlin.mysql.com --managerport 48080 --agentuser uuuu@agent --agentpassword pppp@agent --proxyport 44044 --mode unattended

- update to 2.2.0.1651:  mysqlmonitoragent-2.2.0.1651-windows-update-installer.exe --installdir D:\Merlin\inst\agent\2.1.0.1093\winxp\IBM --mode unattended --enableaggregator 1 --aggregatorport 44400 --enableproxy 1 --createaccount 1 --rootuser root --rootpassword xxxx --servicename "MySQL Enterprise Monitor Agent - 2.2.0.1651 (upd 2.1.0.1093)"

- see that the agent cannot connect to the dashboard after update
- check mysql-monitor-agent.ini, compare user/password settings with version from before the update
[19 Mar 2010 12:59] Carsten Segieth
- related to: Bug#48219 MEM upgrader does not escape special characters
- but in my case the install works except of the wrong setting, and after the .ini was fixed the agent works.
[19 Mar 2010 22:01] Enterprise Tools JIRA Robot
Andy Bang writes: 
Sounds like the url-encoded @ sign (%40) is confusing the parser.
[25 Mar 2010 15:01] BitRock Merlin
Patch sent to Keith.
[25 Mar 2010 17:03] Enterprise Tools JIRA Robot
Keith Russell writes: 
Patch pushed to installer repository.
[25 Mar 2010 18:40] Enterprise Tools JIRA Robot
Keith Russell writes: 
Patch installed in versions => 2.2.0.1611.
[26 Mar 2010 7:01] Carsten Segieth
looking at yesterday's build number I think build 2.2.0.1661 was meant, not 1611 ;-)
[26 Mar 2010 12:57] Enterprise Tools JIRA Robot
Carsten Segieth writes: 
OK in 2.2.0.1661