Closed meichthys closed 3 years ago
To add a little to this, the first time the mysql error shows up in the log, it is preceded by the following. It appears that the issue happened after InnoDB created a new log file:
2021-03-08 10:20:18 0 [Note] InnoDB: Using Linux native AIO
2021-03-08 10:20:18 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-08 10:20:18 0 [Note] InnoDB: Uses event mutexes
2021-03-08 10:20:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-03-08 10:20:18 0 [Note] InnoDB: Number of pools: 1
2021-03-08 10:20:19 0 [Note] InnoDB: Using generic crc32 instructions
2021-03-08 10:20:19 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-08 10:20:19 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-08 10:20:19 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-08 10:20:19 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes
2021-03-08 10:20:19 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes
2021-03-08 10:20:23 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2021-03-08 10:20:23 0 [Note] InnoDB: New log files created, LSN=308713331
2021-03-08 10:20:24 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 801972590 is in the future! Current system log sequence number 308713493.
2021-03-08 10:20:24 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
The docker you are using is deprecated and not supported.
Ok @dlandon, Thanks!
Is there a migration path to the new docker image?
I'm currently using dlandon/zoneminder
as shown in the docker-compose.yaml file on this repo.
Should I be using dlandon/zoneminder.machine.learning
? If so, it doesn't seem to be available on docker hub 🤷♂️.
I've updated the docker compose files. The zoneminder.machine.learning docker is Private and not available yet. We are trying to fund the further development of the machine learning docker. I refer you to the read me.
Environment: I am currently running zoneminder in docker which is a VM running in a proxmox virtual environment for a few months now but every couple weeks i seem to get a corrupted database that results in the following mysql log (
/var/log/mysql/error.log
). So far i have not been able to recover from this and have needed to rebuild from scratch each time :(The docker container log looks like:
Any help would be greatly appreciated. If there's any other information i can provide, please let me know.