hab seit 2 tagen dabien64 drauf nachdem der 32bit zweig nichtmehr installen wollte.
nun hab ich das problem dass ich nichtmahl mehr in phpmyadmin kommen , im syslog steht immer folgendes:
Code: Alles auswählen
Mar 15 17:40:18 debian mysqld[11409]: mysqld got signal 11;
Mar 15 17:40:18 debian mysqld[11409]: This could be because you hit a bug. It is also possible that this binary
Mar 15 17:40:18 debian mysqld[11409]: or one of the libraries it was linked against is corrupt, improperly built,
Mar 15 17:40:18 debian mysqld[11409]: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 15 17:40:18 debian mysqld[11409]: We will try our best to scrape up some info that will hopefully help diagnose
Mar 15 17:40:18 debian mysqld[11409]: the problem, but since we have already crashed, something is definitely wrong
Mar 15 17:40:18 debian mysqld[11409]: and this may fail.
Mar 15 17:40:18 debian mysqld[11409]:
Mar 15 17:40:18 debian mysqld[11409]: key_buffer_size=33554432
Mar 15 17:40:18 debian mysqld[11409]: read_buffer_size=131072
Mar 15 17:40:18 debian mysqld[11409]: max_used_connections=2
Mar 15 17:40:18 debian mysqld[11409]: max_connections=100
Mar 15 17:40:18 debian mysqld[11409]: threads_connected=1
Mar 15 17:40:18 debian mysqld[11409]: It is possible that mysqld could use up to
Mar 15 17:40:18 debian mysqld[11409]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 250367 K
Mar 15 17:40:18 debian mysqld[11409]: bytes of memory
Mar 15 17:40:18 debian mysqld[11409]: Hope that's ok; if not, decrease some variables in the equation.
Mar 15 17:40:18 debian mysqld[11409]:
Mar 15 17:40:18 debian mysqld_safe[11426]: Number of processes running now: 0
Mar 15 17:40:18 debian mysqld_safe[11428]: restarted
Mar 15 17:40:18 debian mysqld[11431]: 050315 17:40:18 InnoDB: Database was not shut down normally!
Mar 15 17:40:18 debian mysqld[11431]: InnoDB: Starting crash recovery.
Mar 15 17:40:18 debian mysqld[11431]: InnoDB: Reading tablespace information from the .ibd files...
Mar 15 17:40:18 debian mysqld[11431]: InnoDB: Restoring possible half-written data pages from the doublewrite
Mar 15 17:40:18 debian mysqld[11431]: InnoDB: buffer...
Mar 15 17:40:18 debian mysqld[11431]: 050315 17:40:18 InnoDB: Starting log scan based on checkpoint at
Mar 15 17:40:18 debian mysqld[11431]: InnoDB: log sequence number 0 50741.
Mar 15 17:40:18 debian mysqld[11431]: InnoDB: Doing recovery: scanned up to log sequence number 0 50787
Mar 15 17:40:18 debian mysqld[11431]: InnoDB: Last MySQL binlog file position 0 79, file name /var/log/mysql/mysql-bin.000154
Mar 15 17:40:18 debian mysqld[11431]: 050315 17:40:18 InnoDB: Flushing modified pages from the buffer pool...
Mar 15 17:40:18 debian mysqld[11431]: 050315 17:40:18 InnoDB: Started; log sequence number 0 50787
Mar 15 17:40:18 debian mysqld[11431]: /usr/sbin/mysqld: ready for connections.
Mar 15 17:40:18 debian mysqld[11431]: Version: '4.1.10a-Debian_1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution
#2013 - Lost connection to MySQL server during query
hat jemand lösungsvorschläge?
Linux debian 2.6.8-10-amd64-k8 #1 Fri Jan 28 04:54:33 CET 2005 x86_64 GNU/Linux
Code: Alles auswählen
ii libdbd-mysql-p 2.9003-4 A Perl5 database interface to the MySQL data
ii libmysqlclient 4.0.24-1 mysql database client library
ii libmysqlclient 4.1.10a-1 mysql database client library
ii mysql-client-4 4.1.10a-1 mysql database client binaries
rc mysql-common 4.0.24-1 mysql database common files (e.g. /etc/mysql
ii mysql-common-4 4.1.10a-1 mysql database common files (e.g. /etc/mysql
rc mysql-server 4.0.24-1 mysql database server binaries
ii mysql-server-4 4.1.10a-1 mysql database server binaries
ii mysqlcc 0.9.4-4 The official GUI interface for MySQL
ii php4-mysql 4.3.10-9 MySQL module for php4
