[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

MySQL break down



Hello there,

I running Debian testing on a NSLU2 but MySQL break down.
I made apt-get remove --purge mysql-server and install it new.
Before I delete the /etc/mysql.

After the install there was no new etc/mysql. I try reconfigure. Nothing help to get the default config back.

I take the default config from an other debian system.

How can I reinstall mysql?
And how it is possible to decrease the memory use?

Thanks

Dirk



May 27 14:24:02 schnek mysqld[2289]: 070527 14:24:02 - mysqld got signal 11;
May 27 14:24:02 schnek mysqld[2289]: This could be because you hit a bug. It is also possible that this binary May 27 14:24:02 schnek mysqld[2289]: or one of the libraries it was linked against is corrupt, improperly built, May 27 14:24:02 schnek mysqld[2289]: or misconfigured. This error can also be caused by malfunctioning hardware. May 27 14:24:02 schnek mysqld[2289]: We will try our best to scrape up some info that will hopefully help diagnose May 27 14:24:02 schnek mysqld[2289]: the problem, but since we have already crashed, something is definitely wrong
May 27 14:24:02 schnek mysqld[2289]: and this may fail.
May 27 14:24:02 schnek mysqld[2289]:
May 27 14:24:02 schnek mysqld[2289]: key_buffer_size=1048576
May 27 14:24:02 schnek mysqld[2289]: read_buffer_size=131072
May 27 14:24:02 schnek mysqld[2289]: max_used_connections=1
May 27 14:24:02 schnek mysqld[2289]: max_connections=100
May 27 14:24:02 schnek mysqld[2289]: threads_connected=1
May 27 14:24:02 schnek mysqld[2289]: It is possible that mysqld could use up to May 27 14:24:02 schnek mysqld[2289]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 218623 K
May 27 14:24:02 schnek mysqld[2289]: bytes of memory
May 27 14:24:02 schnek mysqld[2289]: Hope that's ok; if not, decrease some variables in the equation.
May 27 14:24:02 schnek mysqld[2289]:
May 27 14:24:03 schnek mysqld_safe[2382]: Number of processes running now: 0
May 27 14:24:03 schnek mysqld_safe[2384]: restarted
May 27 14:24:05 schnek mysqld[2387]: 070527 14:24:05 InnoDB: Database was not shut down normally!
May 27 14:24:05 schnek mysqld[2387]: InnoDB: Starting crash recovery.
May 27 14:24:05 schnek mysqld[2387]: InnoDB: Reading tablespace information from the .ibd files... May 27 14:24:05 schnek mysqld[2387]: InnoDB: Restoring possible half-written data pages from the doublewrite
May 27 14:24:05 schnek mysqld[2387]: InnoDB: buffer...
May 27 14:24:06 schnek mysqld[2387]: 070527 14:24:06 InnoDB: Starting log scan based on checkpoint at
May 27 14:24:06 schnek mysqld[2387]: InnoDB: log sequence number 0 43945.
May 27 14:24:06 schnek mysqld[2387]: InnoDB: Doing recovery: scanned up to log sequence number 0 43945 May 27 14:24:07 schnek mysqld[2387]: 070527 14:24:07 InnoDB: Started; log sequence number 0 43945 May 27 14:24:07 schnek mysqld[2387]: 070527 14:24:07 [Note] Recovering after a crash using /var/log/mysql/mysql-bin May 27 14:24:07 schnek mysqld[2387]: 070527 14:24:07 [Note] Starting crash recovery... May 27 14:24:07 schnek mysqld[2387]: 070527 14:24:07 [Note] Crash recovery finished. May 27 14:24:08 schnek mysqld[2387]: 070527 14:24:08 [Note] /usr/sbin/mysqld: ready for connections. May 27 14:24:08 schnek mysqld[2387]: Version: '5.0.38-Debian_1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution



Reply to: