mysqld got signal 4

Pagina: 1
Acties:

  • MrHighStone
  • Registratie: November 2001
  • Laatst online: 03-02-2023
Heeft iemand enig idee wat deze melding betekent? Ik kan mysqld niet installeren op mijn redhat (gebaseerd op ClarkConnect) machine.

Uitgeprobeerde config:
Pentium 166 mmx
32mb RAM
2 GB harddisk en later met een 13 GB harddisk
RedHat 7.0 en later met Redhat 7.2

Wanneer ik het in een VMware machine doe lukt het wel.
Kan het aan de hoeveelheid intern geheugen liggen?

Onderstaande foutmelding verschijnt:
[root@hyperion shared]# rpm -ivh --force --nodeps MySQL-3.23.49-1.i386.rpm
MySQL ##################################################
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 4;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked agaist 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
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Bogus stack limit or frame pointer, fp=0xbffff0f8, stack_bottom=0x75725f, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x38696f6b is invalid pointer
thd->thread_id=0

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 0 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
Installation of grant tables failed!

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

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

Try 'mysqld --help' if you have problems with paths. Using --log
gives you a log in /var/lib/mysql 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 /usr/bin/mysqlbug script!
Starting mysqld daemon with databases from /var/lib/mysql
020226 12:00:51 mysqld ended

Een file op de A12 is nooit grappig...


  • deadinspace
  • Registratie: Juni 2001
  • Laatst online: 16-08 16:08

deadinspace

The what goes where now?

Hmm, signal 4 is SIGILL, die is niet heel gaaf. De kernel deelt die uit als een programma een ILLegal instruction uitvoert.
Is het toevallig geen mysql gecompiled voor een hogere CPU dan jij hebt (voor pII bijvoorbeeld, of voor pI-mmx, terwijl je CPU toch geen mmx blijkt te hebben ofzo)?