Bug #4354 problem with resolveip during install
Submitted: 30 Jun 2004 23:05 Modified: 27 Jul 2004 13:59
Reporter: Albert Aumenta Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Installing Severity:S1 (Critical)
Version:mysql-max-4.0.20 OS:SGI's ALE 3.0 using propack 3.0
Assigned to: Assigned Account CPU Architecture:Any

[30 Jun 2004 23:05] Albert Aumenta
Description:
When installing mysql-max-4.0.20-unknown-linux-ia64 on to an ALTIX 300 running Advanced Linux Environment 3.0 and Propack 3.0. An error occurs with resolveip that affects the successful installation and running of mysql.

 

How to repeat:
after the groupadd, useradd, gunzip, ln-s steps I wttempted to run the install_db script:

[root@testmachine mysql]# scripts/mysql_install_db --user=mysql
Neither host 'testmachine.sgi.com' and 'localhost' could not be looked up with
./bin/resolveip
Please configure the 'hostname' command to return a correct hostname.
If you want to solve this at a later stage, restart this script with
the --force option

*************************************************
by running the --force option I get:

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@testmachine mysql]# scripts/mysql_install_db --force --user=mysql > /tmp/force
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.

******************************************************

here is the output of mysqlbug:

>MySQL support: [none | licence | email support | extended email support ]
>Synopsis:      <synopsis of the problem (one line)>
>Severity:      <[ non-critical | serious | critical ] (one line)>
>Priority:      <[ low | medium | high ] (one line)>
>Category:      mysql
>Class:         <[ sw-bug | doc-bug | change-request | support ] (one line)>
>Release:       mysql-4.0.20-max (Official MySQL-max binary)

>C compiler:
>C++ compiler:
>Environment:
        <machine, os, target, libraries (multiple lines)>
System: Linux testmachine.sgi.com 2.4.21-sgi300r3 #1 SMP Wed Apr 21 18:30:04 PDT 2004 ia64 ia64 ia64 GNU/Linux
Architecture: ia64

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc
GCC: Reading specs from /usr/lib/gcc-lib/ia64-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=ia64-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
Compilation info: CC='ecc'  CFLAGS='-O2 -tpp2 -ip -nolib_inline -DBIG_TABLES'  CXX='ecc'  CXXFLAGS='-O2 -tpp2 -ip -nolib_inline -DBIG_TABLES'  LDFLAGS=''  ASFLAGS=''
LIBC:
lrwxrwxrwx    1 root     root           13 Jun 22 15:42 /lib/libc.so.6.1 -> libc-2.3.2.so
-rwxr-xr-x    1 root     root     10458684 Apr 21 22:43 /lib/libc-2.3.2.so
-rw-r--r--    1 root     root      5183554 Apr 21 23:09 /usr/lib/libc.a
-rw-r--r--    1 root     root          213 Apr 21 22:39 /usr/lib/libc.so
Configure command: ./configure '--prefix=/usr/local/mysql' '--localstatedir=/usr/local/mysql/data' '--libexecdir=/usr/local/mysql/bin' '--with-comment=Official MySQL-max binary' '--with-extra-charsets=complex' '--with-server-suffix=-max' '--enable-thread-safe-client' '--enable-local-infile' '--disable-shared' '--with-client-ldflags=-all-static' '--with-mysqld-ldflags=-all-static' '--with-raid' '--with-embedded-server' '--with-innodb' 'CC=ecc' 'CFLAGS=-O2 -tpp2 -ip -nolib_inline -DBIG_TABLES' 'CXXFLAGS=-O2 -tpp2 -ip -nolib_inline -DBIG_TABLES' 'CXX=ecc'

***********************************
If I run resolve IP by itself with an argument

[root@testmachine bin]# ./resolveip testmachine
Segmentation fault
[root@testmachine bin]#

Suggested fix:
I have no suggested fix.
[2 Jul 2004 6:08] Matthew Lord
I was able to repeat this on sgi1.mysql.com using standard-4.0.20 and standard-4.1.3-beta.
[23 Jul 2004 19:03] Albert Aumenta
I obtained the same resolvip error while using SUSE 9.0 on the ALTIX
[27 Jul 2004 13:59] Lenz Grimmer
This bug was marked as a duplicate of Bug #1853
[3 Mar 2005 14:45] jerry robertson
I also experienced this problem.  To fix I had to specify the alias for my
hostname in the /etc/hosts file.

I previously had my hostname set as 
localhost   ip.ip.ip.ip
www2.*.*  ip.ip.ip.ip
after aliasing just 
www2 ip.ip.ip.ip, everything worked.