MySQL Bugs: #1853: MySQL RPM Does not work on RedHat AS3

Bug #1853	MySQL RPM Does not work on RedHat AS3
Submitted:	16 Nov 2003 18:43	Modified:	27 Aug 2004 22:53
Reporter:	Boyd Gerber	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	MySQL-4.0.16	OS:	Linux (RedHat AS3)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
 Yes, I am using the RPM's from the MySQL site. I have tried it on 4
  separate servers and all had the same results.

  >
  >  >
  >  > Trying to make MySQl 4.0.16 run on a Opteron with ReHat AS3 but stuck
with this error on every rpm install. I just downloaded the source and will try
to compile to see if a diferent error happens.
  >  >
  >  > 031111 10:17:07  mysqld started
  >  > mysqld got signal 11;
  >  > This could be because you hit a bug. It is also possible that this
binary
  >  > or one of the libraries it was linked against is corrupt, improperly
built,
  >  > or misconfigured. This error can also be caused by malfunctioning
hardware.
  >  > We will try our best to scrape up some info that will hopefully help
diagnose
  >  > the problem, but since we have already crashed, something is definitely
wrong
  >  > and this may fail.
  >  >
  >  > key_buffer_size=536870912
  >  > read_buffer_size=2093056
  >  > max_used_connections=0
  >  > max_connections=100
  >  > threads_connected=0
  >  > It is possible that mysqld could use up to
  >  > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 933487 K
  >  > bytes of memory
  >  > Hope that's ok; if not, decrease some variables in the equation.
  >  >
  >  > 031111 10:17:07  mysqld ended
  >

How to repeat:
Install RPM and try to start MySQL

root@lws197 mysql]# scripts/mysql_install_db
WARNING: The host 'lws197.allegro.pl' could not be looked up with resolveip.
This probably means that your libc libraries are not 100 % compatible
with this binary MySQL version. The MySQL daemon, mysqld, should work
normally with the exception that host name resolving will not work.
This means that you should use IP addresses instead of hostnames
when specifying MySQL privileges !
Preparing db table
Preparing host table
Preparing user table
Preparing func table
Preparing tables_priv table
Preparing columns_priv table
Installing all prepared tables
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Installation of grant tables failed!

Examine the logs in ./data for more information.
You can also try to start the mysqld daemon with:
./bin/mysqld --skip-grant &
You can use the command line tool
./bin/mysql to connect to the mysql
database and look at the grant tables:

shell> ./bin/mysql -u root mysql
mysql> show tables

Try 'mysqld --help' if you have problems with paths. Using --log
gives you a log in ./data that may be helpful.

The latest information about MySQL is available on the web at
http://www.mysql.com
Please consult the MySQL manual section: 'Problems running mysql_install_db',
and the manual section that describes problems on your OS.
Another information source is the MySQL email archive.
Please check all of the above before mailing us!
And if you do mail us, you MUST use the ./bin/mysqlbug script!
[root@lws197 mysql]# host lws197.allegro.pl
lws197.allegro.pl has address 192.168.88.197

Same happens on RH3 AS on IA64.

bug#1840 has been marked as a duplicate of this one

Unfortunately there is not much we can currently do about this without having
access to RH AS 3 systems - work is in progress to install these releases on
our AMD64 and IA64 build hosts.

Update: by now, we do have RHAS3 development systems on IA32, AMD64 and IA64 and were able
to confirm the segfaults (on AMD64 and IA64) - they are probably due to the static linking against
older glibc versions. However the standard 4.0.20 Linux/x86 RPM worked - only the 64bit platforms
are affected.

Bug #4354 was marked as a duplicate of this bug.

We have now built RHAS3 RPM packages for AMD64 and IA64. They are available for testing from
here:

ftp://ftp.mysql.com/pub/mysql/download/mysql-4.0.20-rhas3/

If they prove to be stable, we will put them on the public download pages, as well. Feedback is welcome!

One additional comment about these binaries - they were built using gcc 3.2.3 as shipped with RHAS3

Bug #4062 was marked as a duplicate of this bug.

Any possible fix for fedora core 2 on AMD 64.

There gcc is 3.3.3-7 right now so I didn't try to install the AS3 packages.

The compiler installed on the target system does not matter much - these packages do not depend
on any specific compiler version installed.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".