DB Connection Issues - Upgrade - 2.9.4

Seem to have db connection issues with every upgrade and they are probably unrelated to NPM but always best to check.

I’ve updated to 2.9.4 and since the update, the app is reporting is unhealthy with connection issues to the db. Existing rules are working but I cannot login to NPM.

App logs are showing - error select * from migrations_lock - ER_UNKNOWN_STORAGE_ENGINE: Unknown storage engine ‘InnoDB’

Every second or so. Anyone else seeing similar issues? Have removed existing containers and re-pulled without success.

This is on an RPI4.

My Docker compose -

version: ‘3’ services: app: image: ‘jc21/nginx-proxy-manager:latest’ restart: always ports: - ‘80:80’ - ‘81:81’ - ‘443:443’ environment: DB_MYSQL_HOST: “db” DB_MYSQL_PORT: 3306 DB_MYSQL_USER: “DBUSERNAME” DB_MYSQL_PASSWORD: “DBPASSWORD” DB_MYSQL_NAME: “DBNAME” volumes: - /home/pi/Docker/npm/data:/data - /home/pi/Docker/npm/letsencrypt:/etc/letsencrypt depends_on: - db db: image: ‘jc21/mariadb-aria:latest’ restart: always environment: MYSQL_ROOT_PASSWORD: ROOTPASSWORD MYSQL_DATABASE: DBNAME MYSQL_USER: DBUSERNAME MYSQL_PASSWORD: DBPASSWORD volumes: - /home/pi/Docker/npm/data/mysql:/var/lib/mysql

[Jiriteach]

Sure -

Backup your configuration first!

1. Use mysqldump to dump out the structure as a .sql file.

mysqldump -h DBHOSTNAME -u DBUSERNAME -pDBPASSWORD DBNAME > npm_mariadb_backup.sql

1. Use mysql2sqlite (https://github.com/dumblob/mysql2sqlite) to convert the parse the content in the .sql file through to a Sqlite3 database.

./mysql2sqlite npm_mariadb_backup.sql | sqlite3 npm_database.db

1. Move the new Sqlite3 database file into the correct location.

/npm/data/npm_database.db

1. Create a database configuration file for NPM to use a Sqlite3 database and save this as something like db_config.json.

{ “database”: { “engine”: “knex-native”, “knex”: { “client”: “sqlite3”, “connection”: { “filename”: “/data/npm_database.sqlite” }, “useNullAsDefault”: true } } }

1. Update the docker-compose.yml to use the Sqlite3 database.

version: ‘3’ services: app: image: ‘jc21/nginx-proxy-manager:latest’ restart: always ports: - ‘80:80’ - ‘81:81’ - ‘443:443’ environment: DB_SQLITE_FILE: “/data/npm_database.sqlite” volumes: - /home/pi/Docker/npm/data:/data - /home/pi/Docker/npm/letsencrypt:/etc/letsencrypt - /home/pi/Docker/npm/config/db_configuration.json:/app/config/production.json

Should be all that is required. Keep an eye on the log - best way to do this is via Portainer and then you can clear up the other mysql directories inside /npm/data/ as they are no longer required.

[best-74]

Ended up running a mysql dump then converting this to a sqlite3 db and using that. Works well against 2.9.4. This can be closed now. Thanks for the assistance.

Hmm, can you be helpfull and point on how to achieve this. I tried making a dump of my mariadb and convert it with at script, but when i tried to start with sqlite3 file it just deleted the file and startet from scratch.