MySQL Bugs: #24382: server inst - mysqld fails to start up on 64-bit RH

Bug #24382	server inst - mysqld fails to start up on 64-bit RH
Submitted:	17 Nov 2006 5:20	Modified:	17 Apr 2007 13:01
Reporter:	Gary Whizin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Installing	Severity:	S2 (Serious)
Version:	0.7.41	OS:	Linux (RHEL4)
Assigned to:	BitRock Merlin	CPU Architecture:	Any

Description:
 Installing
 0% ______________ 50% ______________ 100%
 ########################################
Error: Error running /home/gwhizin/monitoring100/mysql/bin/mysql
--defaults-file=/home/gwhizin/monitoring100/mysql/my.cnf -S
/home/gwhizin/monitoring100/mysql/tmp/mysql.sock -u root -e "CREATE DATABASE
merlin;" : /home/gwhizin/monitoring100/mysql/bin/mysql: error while loading
shared libraries: libncurses.so.5: cannot open shared object file: No such file
or directory

NOTE: log entry was limited to:

$cat /tmp/bitrock_installer_12014.log
Log started 11/17/06 at 05:29:28
Preferred installation mode : qt
Trying to init installer in mode gtk
Trying to init installer in mode xwindow
Trying to init installer in mode text
Mode text successfully initted

How to repeat:
install fails on 64-bit RH

The near-term plan is to have 32-bit everything running correctly in compatibility mode. We can figure out priority of native 64-bit stack, etc. later. If it's a question of enabling 32-bit compatibility libaries, we should be able to handle that with a readme.

This is the same issue as the other 64bit cases. The user needs to have two compatiblity packages installed (they are usually installed by default). Gary has this info and I understand will be included in the README

In the case of RHEL4:
libgcc-3.4.3-9.EL4.i386.rpm
ncurses-5.4-13.i386.rpm

Debian:
apt-get install libc6
apt-get install libncurses5

CentOS 4.2 x86_64:
ncurses-5.4-13.i386.rpm
glibc-2.3.4-2.13.i386.rpm

mysqlnetwork-1.1.1.5099-linux-x86_64-installer.bin tested successfull on 'rh-x86-64' (RH4 x86-64) with 2 agents connected.
More tests of the Merlin server will follow soon, but the problem described in this bug here is solved.

Added to the changelog.