Fehlermeldung "mysqld funktioniert nicht mehr" - Ursache?

Irgendwelche Probleme mit XAMPP für Windows? Dann ist hier genau der richtige Ort um nachzufragen.

Fehlermeldung "mysqld funktioniert nicht mehr" - Ursache?

Postby djmugge » 16. September 2018 12:50

Ich knabber mich seit etwa 4 Wochen am mysql Dienst fest. Die installierte Version 3.2.2 von XAMPP auf einem Windows 7 Ultimate 32bit hatte immer funktioniert. Es gibt keinen nachvollziehbaren Grund, weshalb der Dienst nicht mehr funktioniert. Andere Datenbank-Anwendungen funktionieren problemlos, die Dienste werden ALLE (FireBird Datenbank für eine Buhl Data Büroanwendung) vorher deaktiviert und beendet.

Einen Fehler konnte ich beheben - in der my.ini waren die Pfade von XAMPP und mysql nicht korrekt. da hatte sich der Fehlerteufel eingeschlichen. Das habe ich korrigiert. Nun startet mysql, beendet sich aber nach ca. 10 Sekunden wieder. Ich habe von den Fehlermeldungen jeweils einen Screenshot gemacht.

Image

Image


Dazu hab ich noch das Logfile was mir aber auch nicht weiterhilft. Wahrscheinlich seh ich die Syntax vor lauter Codezeilen nicht mehr..... :mrgreen:

2018-09-16 13:47:06 1eec 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.
2018-09-16 13:47:06 7916 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-09-16 13:47:06 7916 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-09-16 13:47:06 7916 [Note] InnoDB: The InnoDB memory heap is disabled
2018-09-16 13:47:06 7916 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-09-16 13:47:06 7916 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-09-16 13:47:06 7916 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-09-16 13:47:06 7916 [Note] InnoDB: Using generic crc32 instructions
2018-09-16 13:47:06 7916 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-09-16 13:47:06 7916 [Note] InnoDB: Completed initialization of buffer pool
2018-09-16 13:47:06 7916 [Note] InnoDB: Highest supported file format is Barracuda.
2018-09-16 13:47:06 7916 [Note] InnoDB: The log sequence number 1840393569 in ibdata file do not match the log sequence number 1840393579 in the ib_logfiles!
2018-09-16 13:47:10 7916 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace projekt_manager/FTS_0000000000000100_DELETED uses space ID: 243 at filepath: .\projekt_manager\fts_0000000000000100_deleted.ibd. Cannot open tablespace systemhausshop/s_emarketing_partner which uses space ID: 243 at filepath: .\systemhausshop\s_emarketing_partner.ibd
InnoDB: Error: could not open single-table tablespace file .\systemhausshop\s_emarketing_partner.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.
180916 13:47:10 [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.25-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
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 = 787107 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!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?fix_length_and_dec@subselect_partial_match_engine@@UAEXPAPAVItem_cache@@@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!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
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.


Hoffe auf eure Hilfe

Danke
djmugge
 
Posts: 1
Joined: 16. September 2018 12:36
XAMPP version: 3.2.2
Operating System: Windows 7 Ultimate 32bit

Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 13 guests