MySQL Bugs: #9283: Dumps core when installing on Solaris 10 i86

Bug #9283	Dumps core when installing on Solaris 10 i86
Submitted:	18 Mar 2005 17:03	Modified:	29 Sep 2005 13:12
Reporter:	Steve Hassan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S2 (Serious)
Version:	4.x	OS:	SunOS 5.10 Generic i86pc
Assigned to:		CPU Architecture:	Any

Description:
I installed mysql-standard-4.1.10a-pc-solaris2.10-i386 onto my Solaris 10 i86 platform and it does a core dump as soon as i execute scripts/mysql_install_db --user=mysql.

How to repeat:
Try to install mysql-standard-4.1.10a-pc-solaris2.10-i386 on Solaris 10 i86 which you can download from here

http://www.sun.com/software/solaris/get.jsp

Download Solaris for x64/x86 - CD image

Please verifiy if you followed the Manual instructions and you have the
privileges in the relevant directory?

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

I followed the MySql manual precisely and i was the root user.

i tried again with mysql-standard-4.1.11-pc-solaris2.10-i386, but still no luck.
here's a stack trace:

-bash-3.00# ln -s /usr/local/mysql-standard-4.1.11-pc-solaris2.10-i386 mysql
-bash-3.00# cd mysql
-bash-3.00# scripts/mysql_install_db --user=mysql
Installing all prepared tables
Illegal Instruction - core dumped
Installation of system 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!
-bash-3.00#

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".

I have attempted the installation of 4.1.10, 4.1.11, 4.1.12, -max, and 5.0.6beta and all report exactly the same error as listed above.  Are there some libraries or something that are expected that don't come with a default Solaris 10_x86 installation?  I've been going over this quite a few times.  I duplicate the exact same steps that I use on a Solaris 10 SPARC machine (with the differing packages) and do not have problems with that platform...

Marcos

I am having the exact same problem as Steve. My Stack trace looks exactly the same.  When I try to check the ./data for a log, there is none.  I was wondering if there was any update to this issue.

Thanks

After trying both the Standard pkg.gz and the Standard binary tar.gz, installs of 4.1.12 on a Solaris 10_x86 box, I received the same errors as Mr. Hassan.
 
I then tried to install the source distribution of 4.1.12.  I got by the core dump error after running the mysql_install_db command and got MySql up and running.

Possibly there is some bug with the pkg's or binaries for Solaris 10 i86 platforms.

Dave

I get a core dump when running mysqld as well.
It's quite surprising that this very serious bug hasn't been looked into much yet.

Do you also experience the same problem with the tarball:
http://dev.mysql.com/get/Downloads/MySQL-4.1/mysql-standard-4.1.13-pc-solaris2.10-i386.tar...

Same problem here

What a nasty comment, you're database has a major bug with a major commerical OS on the AMD-64 / i386 platform that now has huge up-take because of containers and it's free price and all we get is smirks we're not providing enough information? I can send you the damn core dump in CD-ROM format and mail it to you if it'll help.

How do we fix this?

Perhaps weight of numbers will precipitate a response?

I have the precise same problem as outlined by all those above. Experience so far with Solaris10 suggests that it may just as likely be a Sun problem, since they seem remarkably unable to produce an OS that actually has useful and correct documentation or installs bug-free where they say it will - but let's face it, MySQL will have to solve the problem, because Sun sure won't.

Feedback, please?

I've been having the same problem. Solaris 10 i86. Gosh, I'd love to have it fixed!

I notice this bug is listed under bug search as "awaiting feedback" (or similar) and has not been allocated to anyone. It is not clear to me from the above what "feedback" is being awaited, more from the user/developer side (i.e. us)?? If so, WHAT? I will happily try to provide whatever is required to get this bug into the "live" and allocated status.

Same problem here. I installed the 'Core components' of Solaris 10 on a PIII machine, not the full distribution if this is any help.

Dear MySQL users on Solaris 10 x86 platform!

We (developers and support engineers) are still waiting for your feedback to the Matthew Lord's request dated July 27th:

"Do you also experience the same problem with the tarball: 
http://dev.mysql.com/get/Downloads/MySQL-4.1/mysql-standard-4.1.13-pc-solaris2.10-i386.tar..."

If you see the same problem on this (still latest) version, please, write a comment and change version to something more reasonable than just 4.x

That is what "Need Feedback" status mean.

Dear MySQL developers and support engineers,
Yes. Yes. Yes.
I have eagerly tried each version as released and the problem persists. Tried:
mysql-standard-4.1.12a-pc-solaris2.10-i386.tar.gz
mysql-standard-4.1.13-pc-solaris2.10-i386.tar.gz

I note that the release notes for each of these version do not mention anything about this bug, so it was only blind hopefulness that made me try. I don't intend to waste my time anymore trying new releases until the notes mention this bug as being addressed.

Please understand that, from a user's perspective, throwing back a bug-report like this with what appears to be an irrelevant request for further information (see comment on release notes) can look like a technique for stalling and keeping the number of active bugs down. I'm sure it's not, but it could look that way.

Was unable to repeat with 4.1.14 today (being logged as a normal user, not root). Here is the log of my actions:

-bash-3.00$ ln -s mysql-standard-4.1.14-pc-solaris2.10-i386 mysql
-bash-3.00$ cd mysql
-bash-3.00$ scripts/mysql_install_db
Installing all prepared tables
Fill help tables

To start mysqld at boot time you have to copy support-files/mysql.server
to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
./bin/mysqladmin -u root password 'new-password'
./bin/mysqladmin -u root -h sol10-x86 password 'new-password'
See the manual for more instructions.

You can start the MySQL daemon with:
cd . ; ./bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests

Please report any problems with the ./bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at https://order.mysql.com
-bash-3.00$ ls -l data
total 16
drwxr-xr-x   2 vkravchuk vkravchuk    4096 Aug 27 16:13 mysql
drwxr-xr-x   2 vkravchuk vkravchuk    4096 Aug 18 13:58 test
-bash-3.00$ bin/mysqld_safe &
[1] 17925
-bash-3.00$ Starting mysqld daemon with databases from /users/vkravchuk/mysql-st
andard-4.1.14-pc-solaris2.10-i386/data

-bash-3.00$ cat data/*.err
050827 16:13:41  mysqld started
-bash-3.00$ uname -a
SunOS sol10-x86 5.10 Generic i86pc i386 i86pc
-bash-3.00$ ps -ef | grep vkravchuk
vkravchu 17939 17925   0 16:13:41 pts/3       0:00 /users/vkravchuk/mysql-standa
rd-4.1.14-pc-solaris2.10-i386/bin/mysqld --default

I tried 4.1.14 today. here is the log of my actions:
# pwd
/usr/sfw
# ls
bin                                            man
doc                                            mysql-standard-4.1.14-pc-solaris2.10-i386.tar
i386-sun-solaris2.10                           sbin
include                                        share
info                                           src
lib                                            swat
libexec
# gtar -zxf mysql-standard-4.1.14-pc-solaris2.10-i386.tar
# rm mysql-standard-4.1.14-pc-solaris2.10-i386.tar
# ln -s mysql-standard-4.1.14-pc-solaris2.10-i386 mysql
# ls -la
total 50
drwxr-xr-x  11 root     bin          512 Aug 30 19:12 .
drwxr-xr-x  35 root     sys         1024 Aug 15 06:15 ..
drwxr-xr-x   3 root     bin         5632 Aug 13 14:07 bin
lrwxrwxrwx   1 root     root           9 Aug 13 14:03 doc -> share/doc
drwxr-xr-x   4 root     bin          512 Aug 13 13:54 i386-sun-solaris2.10
drwxr-xr-x  22 root     bin         1024 Aug 13 14:07 include
lrwxrwxrwx   1 root     root          10 Aug 13 14:03 info -> share/info
drwxr-xr-x  24 root     bin         5120 Aug 13 14:07 lib
drwxr-xr-x   3 root     bin          512 Aug 13 13:54 libexec
lrwxrwxrwx   1 root     root           9 Aug 13 13:57 man -> share/man
lrwxrwxrwx   1 root     root          41 Aug 30 19:12 mysql -> mysql-standard-4.1.14-pc-solaris2.10-i386
drwxr-xr-x  14 8917     other        512 Aug 30 19:11 mysql-standard-4.1.14-pc-solaris2.10-i386
drwxr-xr-x   2 root     bin          512 Aug 13 14:04 sbin
drwxr-xr-x  20 root     bin          512 Aug 13 14:03 share
lrwxrwxrwx   1 root     root           9 Aug 13 13:02 src -> share/src
drwxr-xr-x   6 root     bin          512 Aug 13 13:02 swat
# cd mysql;ls -la
total 106
drwxr-xr-x  14 8917     other        512 Aug 30 19:11 .
drwxr-xr-x  11 root     bin          512 Aug 30 19:12 ..
-rw-r--r--   1 8917     other      19071 Aug 18 03:06 COPYING
-rw-r--r--   1 8917     other       5116 Aug 18 21:32 EXCEPTIONS-CLIENT
-rw-r--r--   1 8917     other       8301 Aug 18 21:32 INSTALL-BINARY
-rw-r--r--   1 8917     other       1937 Aug 18 03:06 README
drwxr-xr-x   2 8917     other       1536 Aug 18 21:58 bin
-rwxr-xr-x   1 8917     other        801 Aug 18 21:58 configure
drwxr-x---   4 8917     other        512 Aug 18 21:58 data
drwxr-xr-x   2 8917     other        512 Aug 18 21:58 docs
drwxr-xr-x   2 8917     other       1536 Aug 18 21:58 include
drwxr-xr-x   2 8917     other        512 Aug 18 21:58 lib
drwxr-xr-x   3 8917     other        512 Aug 18 21:58 man
drwxr-xr-x   7 8917     other        512 Aug 18 21:58 mysql-test
drwxr-xr-x   2 8917     other        512 Aug 18 21:58 scripts
drwxr-xr-x   3 8917     other        512 Aug 18 21:58 share
drwxr-xr-x   5 8917     other       1024 Aug 18 21:58 sql-bench
drwxr-xr-x   2 8917     other        512 Aug 18 21:58 support-files
drwxr-xr-x   2 8917     other        512 Aug 18 21:58 tests
# PATH=$PATH:/usr/sfw/mysql-standard-4.1.14-pc-solaris2.10-i386/bin
# echo $PATH
/usr/sbin:/usr/bin:/usr/sfw/mysql-standard-4.1.14-pc-solaris2.10-i386/bin
# ./scripts/mysql_install_db --user=mysql
Installing all prepared tables
Illegal Instruction - core dumped
Installation of system 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!
# exit
bash-3.00$ exit
exit

This is a brand new Solaris 10 install on Pentium III x86 box, no other software installed apart from GNU tar. Logged in as root.
???

The only difference I can see among our attempts is that you performed yours as root (I have no root privileges on our test machines), and you told nothing about creating mysql user and group (see http://dev.mysql.com/doc/mysql/en/installing-binary.html). So, does mysql user really exist?

And what is the content of *.err file in your ./data directory that should be created while running mysql_install_db?

Have you checked the  MD5 checksum for the .tar.gz you had downloaded?

Can you, please, try to install as conventional user, not root (as I did) and report about the results.

Hi Valeriy,
user mysql and group mysql exist, see screen dump of /etc/passwd below. User and group created both via command-line, then again via Solaris system administration GUI tool - same result both ways, core dump.
checked MD5 - ok (checked on all previous version tried, too).
repeated as user 'andy' member of sysadmin group - same result, core dump.
changed ownership of all files and directories to 'andy:sysadmin' and repeated - same result, core dump.
repeated as both 'root' and 'andy' without the '--user=mysql' directive - same result, core dump.
no error file generated in /usr/sfw/mysql/data - see screen dump below.

# more /etc/passwd
root:x:0:0:Super-User:/:/sbin/sh
daemon:x:1:1::/:
bin:x:2:2::/usr/bin:
sys:x:3:3::/:
adm:x:4:4:Admin:/var/adm:
lp:x:71:8:Line Printer Admin:/usr/spool/lp:
uucp:x:5:5:uucp Admin:/usr/lib/uucp:
nuucp:x:9:9:uucp Admin:/var/spool/uucppublic:/usr/lib/uucp/uucico
smmsp:x:25:25:SendMail Message Submission Program:/:
listen:x:37:4:Network Admin:/usr/net/nls:
gdm:x:50:50:GDM Reserved UID:/:
webservd:x:80:80:WebServer Reserved UID:/:
nobody:x:60001:60001:NFS Anonymous Access User:/:
noaccess:x:60002:60002:No Access User:/:
nobody4:x:65534:65534:SunOS 4.x NFS Anonymous Access User:/:
andy:x:100:14:me:/home/andy:/bin/sh
mysql:x:101:10:mysql daemon:/home/mysql:/bin/sh
# cd /usr/sfw/mysql
# ls -la data
total 8
drwxr-x---   4 andy sysadmin     512 Aug 18 21:58 .
drwxr-xr-x  14 andy sysadmin     512 Aug 31 00:08 ..
drwxr-x---   2 andy sysadmin     512 Aug 18 21:58 mysql
drwxr-x---   2 andy sysadmin     512 Aug 18 21:58 test
# ls -la data/mysql
total 4
drwxr-x---   2 andy sysadmin     512 Aug 18 21:58 .
drwxr-x---   4 andy sysadmin     512 Aug 18 21:58 ..
# ls -la data/test
total 4
drwxr-x---   2 andy sysadmin     512 Aug 18 21:58 .
drwxr-x---   4 andy sysadmin     512 Aug 18 21:58 ..
# exit

Also tried again after editing $HOME/.profile for 'andy' and adding the required PATH there: /usr/sfw/mysql-standard-4.1.14-pc-solaris2.10-i386/bin
(rather than doing it dynamically for the session).

Same result, core dump.

Hi: I'm trying to install the mysql-standard-4.1.14-pc-solaris2.10-i386 on solaris 10 in x86, I got a core dump, but also I tryed this, hope this helps:

bash-3.00# ./bin/mysqld --skip-grant &
[1] 724
bash-3.00# ./bin/mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
[1]+  Illegal Instruction     (core dumped) ./bin/mysqld --skip-grant

I'm a root and I installed the full solaris and oem distribution.

I also have this problem. I can't add anything to the lots of information which has already been provided. I'm posting simply to emphasis that this is a widespread and serious problem.

The only thing that may be worth mentioning is that I am running this at present on an old machine which has only 128M of memory. It may be useful to compare hardware as we don't appear to have much else to go on.

sol10-x86 machine I used for verifying this bus is Intel Pentium 4 2.4 GHz with
1 GB RAM. 

As for installing on 128 Mb - not sure it is good idea. I was able to install early release of Solaris 10 onto 96 Mb, console mode only, but it is really low memory.

What "swap -a" gives you before you try to install?

Would other reporters provide something special about the harware used when observing this bug?

swap -s reports

total:  48804k bytes allocated + 15424k reserved + 64228k used, 595548k available

I understand your concern about installing with only 128M of memory. I'm merely experimenting at present which is why I'm using an old spare machine. If I get some time, I'll try and find some extra memory for this machine and try again.

If it is memory, I would have expected to see a message on the console though.

Hardware details as requested
Generic PC
PIII 550 MHz
512 Mb RAM
2 x 60 Gb IDE HDD
Solaris 10 (full distro.) installed from DVD media, no hardware or other problems reported. Almost no other packages installed, just GNU tar, Samba, Apache and GNU C++.

An afterthought...since you can't replicate this, have you replaced or patched any standard Solaris 10 packages on the testing box? The versions of some packages that ship with Solaris are already known to be idiosyncratic. Mine is standard solaris (except GNU tar). Maybe you should build a totally standard box to try to replicate this?

Results of pkginfo -l from the test machine

Attachment: sol10_x86_pkginfo.txt.gz (application/x-gzip, text), 50.72 KiB.

I had uploaded the results of pkginfo -l command (see Files tab) from the machine I used to repeat you problem. You can compare the results with yours and inform me about any difference.

> Maybe you should build a totally standard box to try to replicate this?

It is not possible for me right now, but I'll keep trying to find a free machine for this, if you'll find large deviations from standard in the machine I used.

Thanks, but no thanks.

I've decided to make the switch and set up our new server environment with PostgreSQL (http://www.postgresql.org).

Anyway, I hope this problem is eventually acknowledged and fixed for the sake of those who have to stick with MySQL. I need to move forward at this time.

This bug was marked as a duplicate of bug#6772

The compile flags for the Solaris 8/9/10 x86 binaries indeed contained "-xtarget=native".
They have now been changed to "-xtarget=generic" to support PIII systems as well and to
avoid the "illegal instruction" crash.

The upcoming releases of MySQL (4.0.27, 4.1.15 and 5.0.14) will be built with these flags.

I am finally able to get mysql to work.  It seems that the suggested compile flags are incorrect.  I used

CFLAGS="-O3 -pipe -march=pentium"
CXXFLAGS="-O2 -pipe -march=pentium"

(I probably should make the -O levels match.)

Previously after compiling from source I would do a "make test" and it would immediately dump core.  At the moment it's currently plowing through the tests.

Previously the compile flags I had tried which produced core dumps are:

CXXFLAGS="-fPIC -O2 \
       -fomit-frame-pointer \
       -felide-constructors \
       -fno-exceptions \
       -fno-rtti \
       -march=pentium"
CFLAGS="-fPIC -O3 -pipe -fomit-frame-pointer -march=pentium"

I'm using gcc-3.4.5.

Sorry, I spoke too soon; there were a bunch of options to ./configure that I also took out.  I'm now narrowing it down to which ./configure option is causing the problem...