error create table `migrations` (`id` int unsigned not null auto_increment primary key, `name` varchar(255), `batch` int, `migration_time` timestamp) - ER_TABLESPACE_EXISTS: Tablespace for table '`npm`.`migrations`' exists. Please DISCARD the tablespace before IMPORT
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- Yes
- Are you sure you're not using someone else's docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- Yes
Describe the bug
The log returns an error and cannot be connected to the management interface
error create table migrations (id int unsigned not null auto_increment primary key, name varchar(255), batch int, migration_time timestamp) - ER_TABLESPACE_EXISTS: Tablespace for table 'npm.migrations' exists. Please DISCARD the tablespace before IMPORT
Nginx Proxy Manager Version 2.9.3
To Reproduce Steps to reproduce the behavior: 4. See error
Expected behavior
Screenshots
Operating System Ubuntu 20.04.2
Additional context Installed in Docker
I had this issue with docker, a restart of the DB container fixed it.
is this resolved yet, am also facing the same issue
One of the solutions that may work is to restart the DB container.
Another one of my cases, the volume was corrupted/dirty so I deleted it and did the docker build/up again.
I also have this error. restarting the database did not help. I dont want to delete the volume, because i don't have it backed up.
I also have this error. restarting the database did not help. I dont want to delete the volume, because i don't have it backed up.
For your workaround you have to set the permissions manually by this script for example. Save this as startup_npm.sh in your folder from docker-compose.yml file.
docker-compose pull
docker-compose up -d
sleep 5
docker exec -it nginxproxymanager_nginxproxymanager-db_1 chown -R mysql:mysql /var/lib/mysql/nginxproxymanager
exit 0
chown -R mysql:mysql /var/lib/mysql/nginxproxymanager
this solved my problem.
I can't get, why this is not fixed till now in the base image.
Issue is now considered stale. If you want to keep it open, please comment :+1:
Issue was closed due to inactivity.