hi!
habs heute nochmal von vorne probiert, mit raufsetzen der max_execution_time von 30 auf 300.
selber kack.
sorry, ans logfile in xampp hab ich nicht gedacht.
was ich dort sehe gefällt gar nicht:
Code:
2017-01-17 08:56:51 20c4 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.
2017-01-17 8:56:51 8388 [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.
2017-01-17 8:56:51 8388 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-01-17 8:56:51 8388 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-17 8:56:51 8388 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-17 8:56:51 8388 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-17 8:56:51 8388 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-17 8:56:51 8388 [Note] InnoDB: Using generic crc32 instructions
2017-01-17 8:56:51 8388 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-17 8:56:51 8388 [Note] InnoDB: Completed initialization of buffer pool
2017-01-17 8:56:51 8388 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-17 8:56:51 8388 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1971107 in the ib_logfiles!
2017-01-17 8:56:51 8388 [Note] InnoDB: Database was not shutdown normally!
2017-01-17 8:56:51 8388 [Note] InnoDB: Starting crash recovery.
2017-01-17 8:56:51 8388 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-17 8:56:51 8388 [Note] InnoDB: Restoring possible half-written data pages
2017-01-17 8:56:51 8388 [Note] InnoDB: from the doublewrite buffer...
2017-01-17 8:56:51 8388 [Note] InnoDB: 128 rollback segment(s) are active.
2017-01-17 8:56:51 8388 [Note] InnoDB: Waiting for purge to start
2017-01-17 8:56:51 8388 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.32-79.0 started; log sequence number 1971107
2017-01-17 8:56:51 8668 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-01-17 8:56:51 8388 [Note] Plugin 'FEEDBACK' is disabled.
2017-01-17 8:56:51 8388 [Note] Server socket created on IP: '::'.
2017-01-17 8:56:51 8388 [ERROR] mysqld.exe: Table '.\mysql\db' is marked as crashed and should be repaired
2017-01-17 8:56:51 8388 [Warning] Checking table: '.\mysql\db'
2017-01-17 8:56:51 8388 [ERROR] mysql.db: 1 client is using or hasn't closed the table properly
2017-01-17 8:56:51 8388 [ERROR] mysqld.exe: Table '.\mysql\tables_priv' is marked as crashed and should be repaired
2017-01-17 8:56:51 8388 [Warning] Checking table: '.\mysql\tables_priv'
2017-01-17 8:56:51 8388 [ERROR] mysql.tables_priv: 1 client is using or hasn't closed the table properly
2017-01-17 8:56:51 8388 [ERROR] mysqld.exe: Table '.\mysql\columns_priv' is marked as crashed and should be repaired
2017-01-17 8:56:51 8388 [Warning] Checking table: '.\mysql\columns_priv'
2017-01-17 8:56:51 8388 [ERROR] mysql.columns_priv: 1 client is using or hasn't closed the table properly
2017-01-17 8:56:51 8388 [ERROR] mysqld.exe: Table '.\mysql\procs_priv' is marked as crashed and should be repaired
2017-01-17 8:56:51 8388 [Warning] Checking table: '.\mysql\procs_priv'
2017-01-17 8:56:51 8388 [ERROR] mysql.procs_priv: 1 client is using or hasn't closed the table properly
2017-01-17 8:56:51 8388 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.19-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-01-17 9:01:54 7884 [ERROR] mysqld.exe: Table '.\mybblocal\mybb_debuglogs' is marked as crashed and should be repaired
2017-01-17 9:01:54 7884 [Warning] Checking table: '.\mybblocal\mybb_debuglogs'
2017-01-17 9:02:45 3776 [ERROR] mysqld.exe: Table '.\smflocal\smf_members' is marked as crashed and should be repaired
2017-01-17 9:02:45 3776 [Warning] Checking table: '.\smflocal\smf_members'
2017-01-17 9:03:28 7884 [ERROR] mysqld.exe: Table '.\smflocal\smf_attachments' is marked as crashed and should be repaired
2017-01-17 9:03:28 7884 [Warning] Checking table: '.\smflocal\smf_attachments'
2017-01-17 9:04:36 7884 [ERROR] mysqld.exe: Table '.\smflocal\smf_settings' is marked as crashed and should be repaired
2017-01-17 9:04:36 7884 [Warning] Checking table: '.\smflocal\smf_settings'
das gesammte log vom test heute...
da dürfte schon die smf datenback was haben?
sorry für die dumme frage: was nu?
mach sowas zum ersten mal und bin da ein bisschen dau.
hätte es sinn einen anderen smf dump einzuspielen und es nochmal versuchen?
werd noch mal mit tante google verhandeln was sie zu einer kaputten smf datenbank sagt.