| Bug #41224 | agent installer fails for Linux ia64 (generic glibc2.3 installer): libssl.so.4 | ||
|---|---|---|---|
| Submitted: | 4 Dec 2008 12:15 | Modified: | 21 Sep 2009 10:53 |
| Reporter: | Carsten Segieth | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Agent | Severity: | S1 (Critical) |
| Version: | 2.0.2.7128 | OS: | Linux (IA64) |
| Assigned to: | Kent Boortz | CPU Architecture: | Any |
| Tags: | build | ||
[4 Dec 2008 12:15]
Carsten Segieth
[8 Jan 2009 16:09]
Carsten Segieth
with 2.0.2.7128 there is an installer for IA64, but it fails on RHEL5, SLES10 and SLES9 with the same "libssl.so.4 missing" error (where it worked on a RHAS4-IA64 box): ------------------------------------------------------------------------------- /nfstmp2/merlin/packages/2.0.2.7128/agents/mysqlmonitoragent-2.0.2.7128-linux-glibc2.3-ia64-64bit-installer.bin --installdir /nfstmp2/merlin/agent/2.0.2.7128/rhel5-ia64-64bit/rhel5-ia64-a --mysqlhost win2003a-x86 --mysqlport 36009 --mysqluser agent --mysqlpassword mysql --checkmysqlhost yes --managerhost qa-merlin --managerport 28080 --agentuser pino@agent --agentpassword onip@agent --proxyport 24044 --mode unattended Problem running post-install step. Installation may not complete correctly Error running /nfstmp2/merlin/agent/2.0.2.7128/rhel5-ia64-64bit/rhel5-ia64-a/bin/mysql-monitor-agent --defaults-file=/nfstmp2/merlin/agent/2.0.2.7128/rhel5-ia64-64bit/rhel5-ia64-a/etc/mysql-monitor-agent.ini --plugins=agent --agent-generate-uuid=true : 2009-01-08 11:28:38: (critical) loading module '/nfstmp2/merlin/agent/2.0.2.7128/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libagent.so' failed: libssl.so.4: cannot open shared object file: No such file or directory 2009-01-08 11:28:38: (critical) setting --plugin-dir=<dir> might help 2009-01-08 11:28:38: (critical) shutting down normally
[22 Jan 2009 16:09]
Carsten Segieth
still happens with 2.0.4.7138 on e.g. rhel5-ia64-a: [mysqldev@rhel5-ia64-a rhel5-ia64-a]$ bin/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 2009-01-22 17:05:37: (critical) loading module '/nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libagent.so' failed: libssl.so.4: cannot open shared object file: No such file or directory 2009-01-22 17:05:37: (critical) setting --plugin-dir=<dir> might help [mysqldev@rhel5-ia64-a rhel5-ia64-a]$ locate libssl.so /home/mysqldev/bs/linux-rhel5-ia64/merlin-agent-2.0-64bit/inst/openssl/lib/libssl.so /home/mysqldev/bs/linux-rhel5-ia64/merlin-agent-2.0-64bit/inst/openssl/lib/libssl.so.0.9.8 /home/mysqldev/bs/merlin/agent-2.0-64bit/inst/mysql-proxy/lib/mysql-proxy/libssl.so /home/mysqldev/bs/merlin/agent-2.0-64bit/inst/mysql-proxy/lib/mysql-proxy/libssl.so.0.9.8 /home/mysqldev/bs/merlin/agent-2.0-64bit/inst/openssl/lib/libssl.so /home/mysqldev/bs/merlin/agent-2.0-64bit/inst/openssl/lib/libssl.so.0.9.8 /home/mysqldev/merlin-agent-2.0-64bit/inst/mysql-proxy/lib/mysql-proxy/libssl.so /home/mysqldev/merlin-agent-2.0-64bit/inst/mysql-proxy/lib/mysql-proxy/libssl.so.0.9.8 /home/mysqldev/merlin-agent-2.0-64bit/inst/openssl/lib/libssl.so /home/mysqldev/merlin-agent-2.0-64bit/inst/openssl/lib/libssl.so.0.9.8 /lib/libssl.so.0.9.8b /lib/libssl.so.6 /usr/lib/libssl.so
[22 Jan 2009 16:20]
Carsten Segieth
[mysqldev@rhel5-ia64-a rhel5-ia64-a]$ ldd ./lib/mysql-proxy/libagent.so linux-gate.so.1 => (0xa000000000000000) libgthread-2.0.so.0 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libgthread-2.0.so.0 (0x20000008000c0000) librt.so.1 => /lib/librt.so.1 (0x20000008000e4000) libgmodule-2.0.so.0 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libgmodule-2.0.so.0 (0x2000000800104000) libdl.so.2 => /lib/libdl.so.2 (0x2000000800120000) libglib-2.0.so.0 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libglib-2.0.so.0 (0x2000000800138000) libxml2.so.2 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libxml2.so.2 (0x20000008002a0000) libpcre.so.0 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libpcre.so.0 (0x200000080057c000) libcurl.so.4 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libcurl.so.4 (0x20000008005c8000) libmysqlclient.so.15 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libmysqlclient.so.15 (0x2000000800640000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x2000000800918000) libnsl.so.1 => /lib/libnsl.so.1 (0x2000000800960000) libm.so.6.1 => /lib/libm.so.6.1 (0x200000080099c000) libevent-1.4.so.2 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libevent-1.4.so.2 (0x2000000800a70000) libmysql-proxy.so.0 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libmysql-proxy.so.0 (0x2000000800ab4000) libsigar.so.0 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libsigar.so.0 (0x2000000800af8000) libpthread.so.0 => /lib/libpthread.so.0 (0x2000000800b34000) libc.so.6.1 => /lib/libc.so.6.1 (0x2000000800b70000) /lib/ld-linux-ia64.so.2 (0x2000000800000000) libz.so.1 => /usr/lib/libz.so.1 (0x2000000800df0000) libssl.so.4 => not found libcrypto.so.4 => not found libresolv.so.2 => /lib/libresolv.so.2 (0x2000000800e24000) libmysql-chassis.so.0 => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/libmysql-chassis.so.0 (0x2000000800e58000) liblua-5.1.1.so => /nfstmp2/merlin/agent/2.0.4.7138/rhel5-ia64-64bit/rhel5-ia64-a/lib/mysql-proxy/liblua-5.1.1.so (0x2000000800e78000)
[29 Jun 2009 17:40]
Keith Russell
Kent, If this isn't something you can help with, can you please re-assign to the correct person?
[2 Jul 2009 12:30]
Kent Boortz
A package created by the new build setup in Trondheim doesn't have this problem. Trace from host 'rhel5-ia64-a' % cd mysql-proxy-0.7.0.0-linux-glibc2.3-ia64-64bit % ldd lib/mysql-proxy/libagent.so | fgrep ssl libssl.so.0.9.8 => not found % bin/mysql-monitor-agent --version mysql-proxy 0.7.0 glib2: 2.16.6 libevent: 1.4.6-stable proxy: 0.7.0 monitor: 0.7.0 MySQL Monitor Agent(agent): 2.1.0.1071 admin: 0.7.0 The suggested action is to move all of the build to the Trondheim setup, avoiding mantaining two setups.
[16 Jul 2009 16:13]
Enterprise Tools JIRA Robot
Carsten Segieth writes: build 2.1.0.1076 (created in Trondheim) was tested successfull on all IA64 boxes, including the 3 failing ones.
[20 Jul 2009 15:12]
Tony Bedford
An entry was added to the 2.1.0 changelog: The generic Linux IA64 glibc2.3 Agent installer was missing from the build.
[12 Aug 2009 14:13]
Leandro Morgado
I see this in RHEL5 for 2.0.5.7153 too: Installing 0% ______________ 50% ______________ 100% ########################################Warning: Problem running post-install s tep. Installation may not complete correctly Error running /opt/mysql/enterprise/agent/bin/mysql-monitor-agent --defaults-file=/opt/mysql/enterprise/agent/etc/mysql-monitor-agent.ini --plugins=agent --agent-generate-uuid=true : 2009-08-10 12:03:35: (critical) loading module '/opt/mysql/enterprise/agent/lib/mysql-proxy/libagent.so' failed: libssl.so.4: cannot open shared object file: No such file or directory 2009-08-10 12:03:35: (critical) setting --plugin-dir=<dir> might help 2009-08-10 12:03:35: (critical) shutting down normally Press [Enter] to continue : # mysqlmonitorage(32704): unaligned access to 0x6000000001997b6c, ip=0x2000000004d c6520 mysqlmonitorage(32704): unaligned access to 0x6000000001997b74, ip=0x2000000004d c6521 mysqlmonitorage(32704): unaligned access to 0x6000000001997b7c, ip=0x2000000004d c6530 mysqlmonitorage(32704): unaligned access to 0x6000000001997b84, ip=0x2000000004d c6531 mysqlmonitorage(32704): unaligned access to 0x6000000001997b8c, ip=0x2000000004d c6540
[12 Aug 2009 14:42]
Leandro Morgado
This seems to still be a problem on 2.0.5.7153. Kent will look into this and hopes to provide a fix by early next week. Thanks Kent!
[31 Aug 2009 8:54]
Enterprise Tools JIRA Robot
Carsten Segieth writes: installer / agent build 2.0.6.7159 tested successfull on all platforms that were failing before.
[31 Aug 2009 14:04]
Leandro Morgado
I tested this again on: -bash-3.1$ uname -a Linux MaskedHostname 2.6.18-53.1.4.el5 #1 SMP Wed Nov 14 10:37:54 EST 2007 ia64 ia64 ia64 GNU/Linux This time the install went well. Log below: ========================================== -bash-3.1$ ./mysqlmonitoragent-2.0.6.7159-linux-glibc2.3-ia64-64bit-installer.bi n mysqlmonitorage(16564): unaligned access to 0x6000000000c90e8c, ip=0x2000000004a e95f0 mysqlmonitorage(16564): unaligned access to 0x6000000000c90e94, ip=0x2000000004a e95f1 mysqlmonitorage(16564): unaligned access to 0x6000000000c90e9c, ip=0x2000000004a e9600 mysqlmonitorage(16564): unaligned access to 0x6000000000c90ea4, ip=0x2000000004a e9601 mysqlmonitorage(16564): unaligned access to 0x6000000000c90eac, ip=0x2000000004a e9610 Language Selection Please select the installation language [1] English - English [2] Japanese - 日本語 Please choose an option [1] : 1 ---------------------------------------------------------------------------- Welcome to the MySQL Enterprise Monitor Agent Setup Wizard. ---------------------------------------------------------------------------- Installation directory Please specify the directory where MySQL Enterprise Monitor Agent will be instal led Installation directory [/users/lmorgado/mysql/enterprise/agent]: How will the agent connect to the database it is monitoring? [1] TCP/IP [2] Socket Please choose an option [1] : 1 ---------------------------------------------------------------------------- Monitored Database Information IMPORTANT: The agent user account specified below requires special MySQL privile ges. Visit the following URL for more information: https://enterprise.mysql.com/docs/monitor/2.0/en/mem-install.html#mem-agent-righ ts MySQL hostname or IP address [127.0.0.1]: Validate MySQL hostname or IP address [Y/n]: n MySQL Port [3306]: MySQL Username []: root MySQL Password : Re-enter : ---------------------------------------------------------------------------- Query Analyzer Configuration MySQL Proxy enables Query Analyzer by listening on the port specified below for client connections that are then passed through to a backend MySQL database serv er. It is not needed for basic monitoring functionality, but is required for Que ry Analyzer. Visit the following URL for more information: https://enterprise.mysql.com/docs/monitor/2.0/en/mem-query-analysis.html Enable Proxy (recommended) [Y/n]: Proxy Port [4040]: Backend Host: 127.0.0.1 (cannot be changed) Backend Port: 3306 (cannot be changed) ---------------------------------------------------------------------------- MySQL Enterprise Monitor Options Hostname or IP address []: mytestserver.com Tomcat Server Port [18080]: Tomcat SSL Port [18443]: Use SSL? [y/N]: y Agent Username [agent]: Agent Password : Re-enter : ---------------------------------------------------------------------------- Configuration Report Here are the settings you specified: Installation directory: /users/lmorgado/mysql/enterprise/agent Monitored MySQL Database: ------------------------- Hostname or IP address: 127.0.0.1 Port: 3306 MySQL username: root MySQL password: pass Query Analyzer Configuration ------------------------- Proxy Enabled: yes Proxy Port: 4040 MySQL Enterprise Monitor: ------------------------- Hostname or IP address: mytestserver.com Tomcat Server Port: 18080 Tomcat SSL Port: 18443 Press [Enter] to continue : Use SSL: 1 Agent username: agent Press [Enter] to continue : ---------------------------------------------------------------------------- Setup is now ready to begin installing MySQL Enterprise Monitor Agent on your co mputer. Do you want to continue? [Y/n]: y ---------------------------------------------------------------------------- Please wait while Setup installs MySQL Enterprise Monitor Agent on your computer . Installing 0% ______________ 50% ______________ 100% #################### ##################### mysqlmonitorage(16564): unaligned access to 0x6000000001c51bcc, ip=0x2000000004a ea520 mysqlmonitorage(16564): unaligned access to 0x6000000001c51bd4, ip=0x2000000004a ea521 mysqlmonitorage(16564): unaligned access to 0x6000000001c51bdc, ip=0x2000000004a ea530 mysqlmonitorage(16564): unaligned access to 0x6000000001c51be4, ip=0x2000000004a ea531 mysqlmonitorage(16564): unaligned access to 0x6000000001c51bec, ip=0x2000000004a ea540 ---------------------------------------------------------------------------- Start MySQL Enterprise Monitor Agent Info to start MySQL Enterprise Monitor Agent The MySQL Monitor Agent was successfully installed. To start the MySQL Agent please invoke: /users/lmorgado/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent start You have not installed the MySQL Service Agent as the root user. Therefore it could not be configured to auto-start on reboot. See the Installation section of the MySQL Enterprise Monitor documentation for instructions on how to do this manually. Press [Enter] to continue : ---------------------------------------------------------------------------- Setup has finished installing MySQL Enterprise Monitor Agent on your computer. View Readme File [Y/n]: n -bash-3.1$ uname -a Linux rhel5-ia64-a.mysql.com 2.6.18-53.1.4.el5 #1 SMP Wed Nov 14 10:37:54 EST 20 07 ia64 ia64 ia64 GNU/Linux -bash-3.1$ cat /etc/issue Red Hat Enterprise Linux Server release 5.1 (Tikanga) Kernel \r on an \m -bash-3.1$ mysql/enterprise/agent/etc/init.d/mysql-monitor-agent status MySQL Enterprise agent does not appear to be running -bash-3.1$ mysql/enterprise/agent/etc/init.d/mysql-monitor-agent start Starting MySQL Enterprise agent service... [ OK ] -bash-3.1$ mysql/enterprise/agent/etc/init.d/mysql-monitor-agent status MySQL Enterprise agent is running
[21 Sep 2009 10:53]
Tony Bedford
Changelog updated to reflect also fixed for 2.0.6.
