Closed whyoon closed 3 years ago
Were any permissions changed when synology was restarted? NAS can be kind of finnicky with UID's and all that but otherwise if it was an unclean shutdown it could be some sort of corruption.
There was this issue where the [ERROR]
lines are the same as yours, but there wasn't any commented solution on what might have caused those specific errors
https://github.com/docker-library/mariadb/issues/330#issuecomment-721479491
But I would try asking over at the Docker Community Forums, Docker Community Slack, or Stack Overflow. Since these repos aren't really a user-help forum
Unlike #330 you have data evidenced by log sequence number 889916432; transaction id 378
Try running the container with --skip-grant-tables to get past the errors.
Then if it starts:
docker exec -ti {container} mysql
(keep this open)create user user@'%'....; grant all on db.* to user@'%'
to perform the initialization that was lost.I would like to know the history how you got into this state so hopefully it can be avoided.
I am using mariadb in the docker of the synology. mariadb will not run after the synology is restarted as shown below. How can I recover it? Please help me.