Bug #57958 agent fails to start after agent upgrade from 2.2 -> 2.3 if no proxy in 2.2

• Submitted: 3 Nov 2010 18:07
• Modified: 4 Jan 2011 22:30
• Reporter: Bill Weber
• Status: Closed
• Category: MySQL Enterprise Monitor: Installing
• Severity: S2 (Serious)
• Version: 2.3.0.2036
• OS: Any
• Assigned to: BitRock Merlin
• CPU Architecture: Any

[3 Nov 2010 18:07] Bill Weber

Description:
If the Proxy was not enabled when installing the 2.2 agent, the agent will gets the following error and does not start after upgrading to 2.3:

2010-11-03 10:34:23: (critical) agent-items-xml.c:33: lua_pcall(): ...prise/agent/share/mysql-monitor-agent/items/quan.lua:11: attempt to index global 'proxy' (a nil value)
2010-11-03 10:34:23: (critical) agent.c:590: reading item-file no. 0 (name: '/opt/mysql/enterprise/agent/share/mysql-monitor-agent/items/quan.lua') failed
2010-11-03 10:34:23: (critical) mainloop.c:267: applying config of plugin MySQL Monitor Agent failed
2010-11-03 10:34:23: (critical) mysql-proxy-cli.c:596: Failure from chassis_mainloop. Shutting down.

Workaround:

remove "share/mysql-monitor-agent/items/quan.lua" from "agent-item-files" in mysql-monitor-agent.ini

How to repeat:
- install 2.2 agent and uncheck option to enable proxy (not the default)
- upgrade install 2.3 and keep option to enable proxy unchecked (default)

[3 Nov 2010 19:17] Enterprise Tools JIRA Robot

Andy Bang writes: 
Please remove "share/mysql-monitor-agent/items/quan.lua" from "agent-item-files" in mysql-monitor-agent.ini if the Proxy is not enabled during upgrade.

[12 Nov 2010 11:13] BitRock Merlin

Patch sent to Andy

[18 Nov 2010 1:05] Enterprise Tools JIRA Robot

Andy Bang writes: 
In build 2.3.1.2039.

[18 Nov 2010 19:19] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
tested OK in 2.3.1.2039; test added to Hudson

[4 Jan 2011 22:30] John Russell

Added to 2.3.1 change log:

If the proxy was not enabled in MySQL Enterprise Monitor 2.2, an upgrade
to 2.3 could fail.