Bug #43125 error message launching mysql-monitor
Submitted: 23 Feb 2009 23:16 Modified: 9 Aug 2010 12:37
Reporter: Pozzi Jean-Paul Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version: OS:Linux
Assigned to: Michael Schuster CPU Architecture:Any
Tags: monitor agent ssl

[23 Feb 2009 23:16] Pozzi Jean-Paul

When launching the agent I get the message :
Starting MySQL Enterprise agent service...ssh-keygen: /opt/mysql/enterprise/agent/lib/mysql-proxy/libcrypto.so.0.9.8: no version information available (required by ssh-keygen)

Occurs on Suse 64 bits and Debian 32 bits.


JP Pozzi

./mysql-monitor-agent --version
mysql-proxy 0.7.0
  glib2: 2.16.3
  libevent: 1.4.6-stable
  proxy: 0.7.0
  monitor: 0.7.0
  MySQL Monitor Agent(agent):
  admin: 0.7.0

How to repeat:

Launch monitor agent
[10 Mar 2009 16:28] Gary Whizin
We use that to provide a more unique host ID. If it's not available we fall back to the mac address of the box.

Can you clarify: is it logging but working anyway? Or is it shutting down?
[10 Mar 2009 18:46] Pozzi Jean-Paul
All is working, only the message is disturbing.
I do not try SSH connection.

AS my evaluation time has only 4 days left I don't know if
I will enough time to test all functions.


JP Pozzi
[1 May 2009 9:52] Jan Kneschke
We call "ssh-keygen" to extract the host-id from the ssh-host-key.

As we also set LD_LIBRARY_PATH to point to our own libraries (incl. a bundled libopenssl.so) this leads to a mismatch of our binaries being linked against th bundled openssl and ssh-keygen linked against the system-provided libopenssl.

As a workaround run the ssh-keygen command by hand:

  $ ssh-keygen -l -f /etc/ssh/ssh_host_key.pub  | awk  '{print $2}'
  $ echo 'agent-host-id = 82:01:1d:38:42:77:69:58:5b:11:4c:f9:48:68:93:31' >> mysql-monitor-agent.ini
[20 Oct 2009 16:37] Enterprise Tools JIRA Robot
Jan Kneschke writes: 
Proposal: before we call ssh-keygen unset the LD_LIBRARY_PATH internally.
[22 Mar 2010 17:25] Enterprise Tools JIRA Robot
Keith Russell writes: 
Patch installed in versions =>
[25 Mar 2010 14:43] Enterprise Tools JIRA Robot
Carsten Segieth writes: 
checked OK with
[25 Mar 2010 15:26] MC Brown
A note has been added to the 2.1.2 changelog: 

        Starting the agent could lead to an error regarding
        the <command>ssh-keygen</command> tool and a missing library
[1 Jun 2010 15:23] Enterprise Tools JIRA Robot
Jan Kneschke writes: 
Patch was:

revno: 1560
committer: michael.schuster@sun.com
branch nick: agent2.1
timestamp: Mon 2010-03-15 05:55:38 -0700
  tentative fix for EM-3143 "error message launching mysql-monitor" (untested)
[15 Jun 2010 20:52] Chris Calender
Re-opening this bug (and setting to "verified") as it appears in 2.2.

2010-06-15 16:03:16: (critical) MySQL Monitor Agent started.
2010-06-15 16:03:16: (critical) Running 'sh -c "ssh-keygen -l -f /etc/ssh/ssh_host_dsa_key.pub | awk '{print \"ssh:{\"$2\"}\"}'"' failed with the following message on stderr.
Falling back to MAC address detection.
ssh-keygen: /usr/local/mysql-agent/lib/libcrypto.so.0.9.8: no version information available (required by ssh-keygen)

MEM Agent:
MEM Server:
[9 Aug 2010 12:36] Michael Schuster
synchronisation with jira seems to have failed here, so closing manually.
[9 Aug 2010 12:37] Michael Schuster
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

[16 Sep 2010 9:12] Mark Leith
This was resolved in the 2.2.2 release.