System Crash

Alles, was MariaDB und MySQL betrifft, kann hier besprochen werden.

System Crash

Postby Babsy Taenzer » 01. August 2019 19:24

hallo forum,

habe einen crash mit meinem system. phpadmin 4.8., mariadb 10.1.

ich habe mit einem anderen programm ein systembackup für den gesamten computer zurückgeholt, danach ließ sich das mysql nicht mehr starten.
das xampp-panel findet das port 3306 für den mysqlserver nicht.
das fehlerprotokoll aus der logdatei lege ich mit bei.
der datenbestand ist in backups gesichert und damit erst einmal nicht das problem.
eigentlich wollte ich mariadb 10.3.16.msi installieren. doch das ist auch schief gegangen. so war ich gezwungen das systembackup zurückzuholen.
nun stehe ich da und habe gar nichts mehr.



mfg
B.

anlage
------------

2019-08-01 18:27:00 7332 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
2019-08-01 18:27:01 1ca4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2019-08-01 18:27:01 7332 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-08-01 18:27:01 7332 [Note] InnoDB: The InnoDB memory heap is disabled
2019-08-01 18:27:01 7332 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-08-01 18:27:01 7332 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-08-01 18:27:01 7332 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-08-01 18:27:01 7332 [Note] InnoDB: Using generic crc32 instructions
2019-08-01 18:27:01 7332 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2019-08-01 18:27:01 7332 [Note] InnoDB: Completed initialization of buffer pool
2019-08-01 18:27:01 7332 [Note] InnoDB: Highest supported file format is Barracuda.
2019-08-01 18:27:01 7332 [Note] InnoDB: The log sequence number 215164336 in ibdata file do not match the log sequence number 3194192761 in the ib_logfiles!
2019-08-01 18:27:04 7332 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace b10/allgemeine@0020haftpflicht1 uses space ID: 6708 at filepath: .\b10\allgemeine@0020haftpflicht1.ibd. Cannot open tablespace b10wpv/allgemeine@0020haftpflicht1 which uses space ID: 6708 at filepath: .\b10wpv\allgemeine@0020haftpflicht1.ibd
InnoDB: Error: could not open single-table tablespace file .\b10wpv\allgemeine@0020haftpflicht1.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
190801 18:27:04 [ERROR] mysqld got exception 0x80000003 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.29-MariaDB
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1994009 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?set_derivation@Field@@UAEXW4Derivation@@I@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Babsy Taenzer
 
Posts: 6
Joined: 26. January 2018 19:35
XAMPP version: 4.7.7
Operating System: Windows 10

Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 2 guests