MySQL Bugs: #43125: error message launching mysql-monitor

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:	None
Category:	MySQL Enterprise Monitor: Agent	Severity:	S3 (Non-critical)
Version:	2.0.4.7141	OS:	Linux
Assigned to:	Michael Schuster	CPU Architecture:	Any
Tags:	monitor agent ssl

Description:
Hello,

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.

Regards

JP Pozzi

PS:
./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): 2.0.4.7141
  admin: 0.7.0

How to repeat:

Launch monitor agent

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?

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.

Regards

JP Pozzi

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}'
  82:01:1d:38:42:77:69:58:5b:11:4c:f9:48:68:93:31
  $ echo 'agent-host-id = 82:01:1d:38:42:77:69:58:5b:11:4c:f9:48:68:93:31' >> mysql-monitor-agent.ini

Jan Kneschke writes: 
Proposal: before we call ssh-keygen unset the LD_LIBRARY_PATH internally.

Keith Russell writes: 
Patch installed in versions => 2.1.2.1160.

Carsten Segieth writes: 
checked OK with 2.1.2.1160

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

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
message:
  tentative fix for EM-3143 "error message launching mysql-monitor" (untested)

Re-opening this bug (and setting to "verified") as it appears in 2.2.

2010-06-15 16:03:16: (critical) MySQL Monitor Agent 2.2.1.1717 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: 2.2.1.1717
MEM Server: 2.2.1.1721

synchronisation with jira seems to have failed here, so closing manually.

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

    http://dev.mysql.com/doc/en/installing-source.html

This was resolved in the 2.2.2 release.