Hallo
ich bin etwas frisch auf owncloud und mysql unterwegs. und habe noch einen INTERNEN SERVERFEHLER (von der WEB Page gemeldet) und einen REBOOT ein Problem mit dem MYSQL Server.
Auf der WEB Page sieht man interner Serverfehler.
Auf der Console kommt diese Meldung:
**
/etc/mysql# ERROR 2013 (HY000) at line 1: Lost connection to MySQL server during query
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
***************
Im Syslog steht (das BINDING auf 0.0.0.0 habe ich wegen den Fehler geändert, weil ich dachte komme von aussen ran)
****
Mar 13 00:59:19 raspi01 mysqld: 150313 0:59:19 InnoDB: Page checksum 1801656042, prior-to-4.0.14-form checksum 839741651
Mar 13 00:59:19 raspi01 mysqld: InnoDB: stored checksum 4017239245, prior-to-4.0.14-form stored checksum 839741651
Mar 13 00:59:19 raspi01 mysqld: InnoDB: Page lsn 0 645643984, low 4 bytes of lsn at page end 645643984
Mar 13 00:59:19 raspi01 mysqld: InnoDB: Page number (if stored to page already) 318,
Mar 13 00:59:19 raspi01 mysqld: InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
Mar 13 00:59:19 raspi01 mysqld: InnoDB: Page may be an 'inode' page
Mar 13 00:59:19 raspi01 mysqld: InnoDB: Database page corruption on disk or a failed
Mar 13 00:59:19 raspi01 mysqld: InnoDB: file read of page 318.
Mar 13 00:59:19 raspi01 mysqld: InnoDB: You may have to recover from a backup.
Mar 13 00:59:19 raspi01 mysqld: InnoDB: It is also possible that your operating
Mar 13 00:59:19 raspi01 mysqld: InnoDB: system has corrupted its own file cache
Mar 13 00:59:19 raspi01 mysqld: InnoDB: and rebooting your computer removes the
Mar 13 00:59:19 raspi01 mysqld: InnoDB: error.
Mar 13 00:59:19 raspi01 mysqld: InnoDB: If the corrupt page is an index page
Mar 13 00:59:19 raspi01 mysqld: InnoDB: you can also try to fix the corruption
Mar 13 00:59:19 raspi01 mysqld: InnoDB: by dumping, dropping, and reimporting
Mar 13 00:59:19 raspi01 mysqld: InnoDB: the corrupt table. You can use CHECK
Mar 13 00:59:19 raspi01 mysqld: InnoDB: TABLE to scan your table for corruption.
Mar 13 00:59:19 raspi01 mysqld: InnoDB: See also
http://dev.mysql.com/doc/refman/5.5/en/ ... overy.html
Mar 13 00:59:19 raspi01 mysqld: InnoDB: about forcing recovery.
Mar 13 00:59:19 raspi01 mysqld: InnoDB: Ending processing because of a corrupt database page.
Mar 13 00:59:19 raspi01 mysqld: 150313 0:59:19 InnoDB: Assertion failure in thread 2773931104 in file buf0buf.c line 3620
Mar 13 00:59:19 raspi01 mysqld: InnoDB: We intentionally generate a memory trap.
Mar 13 00:59:19 raspi01 mysqld: InnoDB: Submit a detailed bug report to
http://bugs.mysql.com
.
Mar 13 00:59:19 raspi01 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Mar 13 00:59:19 raspi01 mysqld: InnoDB: immediately after the mysqld startup, there may be
Mar 13 00:59:19 raspi01 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Mar 13 00:59:19 raspi01 mysqld: InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/ ... overy.html
Mar 13 00:59:19 raspi01 mysqld: InnoDB: about forcing recovery.
Mar 13 00:59:19 raspi01 mysqld: 23:59:19 UTC - mysqld got signal 6 ;
Mar 13 00:59:19 raspi01 mysqld: This could be because you hit a bug. It is also possible that this binary
Mar 13 00:59:19 raspi01 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Mar 13 00:59:19 raspi01 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 13 00:59:19 raspi01 mysqld: We will try our best to scrape up some info that will hopefully help
Mar 13 00:59:19 raspi01 mysqld: diagnose the problem, but since we have already crashed,
Mar 13 00:59:19 raspi01 mysqld: something is definitely wrong and this may fail.
Mar 13 00:59:19 raspi01 mysqld:
Mar 13 00:59:19 raspi01 mysqld: key_buffer_size=16777216
Mar 13 00:59:19 raspi01 mysqld: read_buffer_size=131072
Mar 13 00:59:19 raspi01 mysqld: max_used_connections=1
Mar 13 00:59:19 raspi01 mysqld: max_threads=151
Mar 13 00:59:19 raspi01 mysqld: thread_count=1
Mar 13 00:59:19 raspi01 mysqld: connection_count=1
Mar 13 00:59:19 raspi01 mysqld: It is possible that mysqld could use up to
Mar 13 00:59:19 raspi01 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346093 K bytes of memory
Mar 13 00:59:19 raspi01 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Mar 13 00:59:19 raspi01 mysqld:
Mar 13 00:59:19 raspi01 mysqld: Thread pointer: 0xffffffffb90122e8
Mar 13 00:59:19 raspi01 mysqld: Attempting backtrace. You can use the following information to find out
Mar 13 00:59:19 raspi01 mysqld: where mysqld died. If you see no messages after this, something went
Mar 13 00:59:19 raspi01 mysqld: terribly wrong...
Mar 13 00:59:19 raspi01 mysqld: stack_bottom = ffffffffa556cdbc thread_stack 0x30000
Mar 13 00:59:19 raspi01 mysqld:
Mar 13 00:59:19 raspi01 mysqld: Trying to get some variables.
Mar 13 00:59:19 raspi01 mysqld: Some pointers may be invalid and cause the dump to abort.
Mar 13 00:59:19 raspi01 mysqld: Query (ffffffffb9062168): SELECT `appid`, `configkey`, `configvalue` FROM `oc_preferences` WHERE `userid` = 'Byte'
Mar 13 00:59:19 raspi01 mysqld: Connection ID (thread ID): 1
Mar 13 00:59:19 raspi01 mysqld: Status: NOT_KILLED
Mar 13 00:59:19 raspi01 mysqld:
Mar 13 00:59:19 raspi01 mysqld: The manual page at
http://dev.mysql.com/doc/mysql/en/crashing.html
contains
Mar 13 00:59:19 raspi01 mysqld: information that should help you find out what is causing the crash.
Mar 13 00:59:20 raspi01 mysqld_safe: Number of processes running now: 0
Mar 13 00:59:20 raspi01 mysqld_safe: mysqld restarted
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 [Note] Plugin 'FEDERATED' is disabled.
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 InnoDB: The InnoDB memory heap is disabled
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 InnoDB: Compressed tables use zlib 1.2.7
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 InnoDB: Using Linux native AIO
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 InnoDB: Initializing buffer pool, size = 128.0M
Mar 13 00:59:20 raspi01 mysqld: 150313 0:59:20 InnoDB: Completed initialization of buffer pool
Mar 13 00:59:21 raspi01 mysqld: 150313 0:59:21 InnoDB: highest supported file format is Barracuda.
Mar 13 00:59:21 raspi01 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 646450548
Mar 13 00:59:21 raspi01 mysqld: 150313 0:59:21 InnoDB: Database was not shut down normally!
Mar 13 00:59:21 raspi01 mysqld: InnoDB: Starting crash recovery.
Mar 13 00:59:21 raspi01 mysqld: InnoDB: Reading tablespace information from the .ibd files...
Mar 13 00:59:21 raspi01 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
Mar 13 00:59:21 raspi01 mysqld: InnoDB: buffer...
Mar 13 00:59:21 raspi01 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 646450558
Mar 13 00:59:21 raspi01 mysqld: 150313 0:59:21 InnoDB: Waiting for the background threads to start
Mar 13 00:59:22 raspi01 mysqld: 150313 0:59:22 InnoDB: 5.5.41 started; log sequence number 646450558
Mar 13 00:59:22 raspi01 mysqld: 150313 0:59:22 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
Mar 13 00:59:22 raspi01 mysqld: 150313 0:59:22 [Note] - '0.0.0.0' resolves to '0.0.0.0';
Mar 13 00:59:22 raspi01 mysqld: 150313 0:59:22 [Note] Server socket created on IP: '0.0.0.0'.
Mar 13 00:59:22 raspi01 mysqld: 150313 0:59:22 [Note] Event Scheduler: Loaded 0 events
Mar 13 00:59:22 raspi01 mysqld: 150313 0:59:22 [Note] /usr/sbin/mysqld: ready for connections.
Mar 13 00:59:22 raspi01 mysqld: Version: '5.5.41-0+wheezy1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
******
Frage: KLAR WAS KANN ICH ALS FRISCHLING MACHEN, AUSSER NEUINSTALLATION...
´Für Hilfe wäre ich dankbar.
DAU User
Byterunner
Statistics: Posted by Byterunner — Fri Mar 13, 2015 2:10 am