n22_uml ~ # /etc/init.d/mysql start * Re-caching dependency info (mtimes differ)... * Re-caching dependency info (mtimes differ)... * Re-caching dependency info (mtimes differ)... * Re-caching dependency info (mtimes differ)... * Starting mysqld (/etc/mysql/my.cnf) ... [ ok ] n22_uml ~ # /etc/init.d/mysql status * status: started n22_uml ~ # ps -ef | grep mysqld root 2658 1658 0 17:19 tty1 00:00:00 grep mysqld Starting it manually gives: n22_uml ~ # /usr/bin/mysqld_safe --defaults-file=/etc/mysql/my.cnf Starting mysqld daemon with databases from /var/lib/mysql STOPPING server from pid file /var/run/mysqld/mysqld.pid 060308 17:20:11 mysqld ended So this could be processed to not set the status to "started", isn't it ? BTW (yes, this should be a separate bug), I got under UML: n22_uml ~ # cat /var/log/mysql/mysqld.err 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=0 read_buffer_size=258048 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 = 76399 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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... frame pointer (ebp) is NULL, did you compile with -fomit-frame-pointer? Aborting backtrace! The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Has somebody a clue, why ?
you are playing with 5.1 right ? Compiled with some options this server start fine, then crash after a little time. It's not possible to check if the server goes down after it start, need to use someting like "daemontools" by D.J.Bernstein to monitor a server after startup or the "mysqlmanager" startup script that does something similar.
>you are playing with 5.1 right ? No, I got his error both with 4.0.25-r2 and 4.1.14, but only under user mode linux after I upgraded to gcc 3.4.5 and Gentoo 2006.0 - I assume that the changed nptl flag forced a recompiling of glibc which now produce this trouble. >It's not possible to check if the server goes down after it start :-( Ok, I think this special then seems not to be worth to add much more logic to a startup script.
