Ron Olsen;177955 Wrote: > OK, delete the mysql-error-log.txt file so we can start over. > > Try this again, and make sure you're using the 5.0.26 version of mysqld > as described in my previous post. > > Post the output of "ps ax | grep mysqld" shortly after starting > slimserver. > > Also post the contents of the mysql-error-log.txt file.
ks33912 ~ # /etc/init.d/slimserver start & [1] 14343 ks33912 ~ # * Starting slimserver ... ps ax | grep mysqld 8413 ? Ssl 0:00 /usr/sbin/mysqld --defaults-file=/etc/mysql/my.cnf --basedir=/usr --datadir=/var/lib/mysql --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock 19728 pts/0 R+ 0:00 grep mysqld [ ok ] I try to be as fast as I can... The mysql log: 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 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=4 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3055 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 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. 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 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=4 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3055 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 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. -- Alexis ------------------------------------------------------------------------ Alexis's Profile: http://forums.slimdevices.com/member.php?userid=816 View this thread: http://forums.slimdevices.com/showthread.php?t=32451 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
