Hi Peter, thanks for your reply. I'm new to trying to analyse the performance of MySQL. I've been using it for a number of years and wanted to take advantage of the performance monitoring, so I upgraded to 5.6, thus causing these problems, and my lack of knowledge on the matter is now apparent. I will upgrade to 5.7 but after I get some understanding of these issues as I don't want to compound them.
Can i see historical innodb status? When i run the command, I only see as it is now.
I edited the error file and can see these from the last 'crash' at 14.06
I hope this helps
Thanks
Kieran
------------------------------------------------------------------------------
------------------------------------------------------------------------------
2022-06-27 14:06:06 6666 [Note] Plugin 'FEDERATED' is disabled.
2022-06-27 14:06:07 6666 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-06-27 14:06:07 6666 [Note] InnoDB: The InnoDB memory heap is disabled
2022-06-27 14:06:07 6666 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-06-27 14:06:07 6666 [Note] InnoDB: Memory barrier is not used
2022-06-27 14:06:07 6666 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-06-27 14:06:07 6666 [Note] InnoDB: Using Linux native AIO
2022-06-27 14:06:07 6666 [Note] InnoDB: Not using CPU crc32 instructions
2022-06-27 14:06:07 6666 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2022-06-27 14:06:07 6666 [Note] InnoDB: Completed initialization of buffer pool
2022-06-27 14:06:07 6666 [Note] InnoDB: Highest supported file format is Barracuda.
2022-06-27 14:06:07 6666 [Note] InnoDB: The log sequence numbers 11848177344427 and 11848177344427 in ibdata files do not match the log sequence number 11850988481805 in the ib_logfiles!
2022-06-27 14:06:07 6666 [Note] InnoDB: Database was not shutdown normally!
2022-06-27 14:06:07 6666 [Note] InnoDB: Starting crash recovery.
2022-06-27 14:06:07 6666 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-06-27 14:06:20 6666 [Note] InnoDB: Restoring possible half-written data pages
2022-06-27 14:06:20 6666 [Note] InnoDB: from the doublewrite buffer...
2022-06-27 14:06:06 6666 [Note] Plugin 'FEDERATED' is disabled.
2022-06-27 14:06:07 6666 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-06-27 14:06:07 6666 [Note] InnoDB: The InnoDB memory heap is disabled
2022-06-27 14:06:07 6666 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-06-27 14:06:07 6666 [Note] InnoDB: Memory barrier is not used
2022-06-27 14:06:07 6666 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-06-27 14:06:07 6666 [Note] InnoDB: Using Linux native AIO
2022-06-27 14:06:07 6666 [Note] InnoDB: Not using CPU crc32 instructions
2022-06-27 14:06:07 6666 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2022-06-27 14:06:07 6666 [Note] InnoDB: Completed initialization of buffer pool
2022-06-27 14:06:07 6666 [Note] InnoDB: Highest supported file format is Barracuda.
2022-06-27 14:06:07 6666 [Note] InnoDB: The log sequence numbers 11848177344427 and 11848177344427 in ibdata files do not match the log sequence number 11850988481805 in the ib_logfiles!
2022-06-27 14:06:07 6666 [Note] InnoDB: Database was not shutdown normally!
2022-06-27 14:06:07 6666 [Note] InnoDB: Starting crash recovery.
2022-06-27 14:06:07 6666 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-06-27 14:06:20 6666 [Note] InnoDB: Restoring possible half-written data pages
2022-06-27 14:06:20 6666 [Note] InnoDB: from the doublewrite buffer...
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 277 row operations to undo
InnoDB: Trx id counter is 38262978304
2022-06-27 14:06:24 6666 [Note] InnoDB: 128 rollback segment(s) are active.
2022-06-27 14:06:24 6666 [Note] InnoDB: Waiting for purge to start
InnoDB: Starting in background the rollback of uncommitted transactions
2022-06-27 14:06:24 2af8000af700 InnoDB: Rolling back trx with id 38262977690, 18 rows to undo
2022-06-27 14:06:24 6666 [Note] InnoDB: 5.6.41 started; log sequence number 11850988481805
2022-06-27 14:06:24 6666 [Note] InnoDB: Rollback of trx with id 38262977690 completed
2022-06-27 14:06:24 2af8000af700 InnoDB: Rolling back trx with id 38262943197, 259 rows to undo
2022-06-27 14:06:24 6666 [Note] Server hostname (bind-address): '*'; port: 3306
2022-06-27 14:06:24 6666 [Note] IPv6 is available.
2022-06-27 14:06:24 6666 [Note] - '::' resolves to '::';
2022-06-27 14:06:24 6666 [Note] Server socket created on IP: '::'.
2022-06-27 14:06:24 2af7db17a5c0 InnoDB: Error: table `tmp`.`#sql718d_436_1` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB:
http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2022-06-27 14:06:24 6666 [Note] Event Scheduler: Loaded 0 events
2022-06-27 14:06:24 6666 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.41-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)