Bug #41260 mysql-monitor-agent fails on solaris 10, uses wrong tr
Submitted: 5 Dec 2008 13:44 Modified: 27 Feb 2009 14:48
Reporter: Johan Idrén Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version: OS:Solaris (sol10x86)
Assigned to: Mark Matthews CPU Architecture:Any

[5 Dec 2008 13:44] Johan Idrén
Agent startup fails on Solaris 10 with:

# ./mysql-monitor-agent start
Bad string 
ERROR! /opt/mysql/enterprise/agent/etc/mysql-monitor-agent.ini has to have a [mysql-proxy].pid-file setting

Caused by unexpected behavior of 'tr'

How to repeat:
Install latest agent on Solaris 10, try to start it.

Suggested fix:
Use /usr/xpg4/bin/tr on Solaris 10 instead.
[5 Dec 2008 18:25] Sloan Childers
this is a bug in the init.d script we distribute... assigning to Jan
[19 Feb 2009 0:12] Keith Russell
Patch applied in version =>
[27 Feb 2009 14:48] Tony Bedford
An entry was added to the 2.0.5 changelog:

Agent startup failed on Solaris 10. The error generated was:

# ./mysql-monitor-agent start
Bad string 
ERROR! /opt/mysql/enterprise/agent/etc/mysql-monitor-agent.ini has to have a
[mysql-proxy].pid-file setting

This was caused by unexpected behavior of the tr command.