starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #905] Migration table is already locked after re-installation #764

New issue

Closed

opened 2026-02-26 06:34:18 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 06:34:18 +03:00

Owner

Originally created by @dicktsui on GitHub (Feb 19, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/905

Hi, I'm using rpi4+omv platform. I followed the installation guide and successfully used the NPM on first setup. However I get an error message after re-install the NPM via docker-compose. I already removed the NPM(app & db) in portainer and also deleted the NPM directory (command: rm -r NPM), but the problem still exists. Would you help to solve this issue or teach me how to manually release the lock (or deleting all the rows)? Thank you very much.

[2/19/2021] [4:15:05 AM] [Migrate ] › ℹ info Current database version: 20190218060101,
Can't take lock to run migrations: Migration table is already locked,
If you are sure migrations are not running you can release the lock manually by deleting all the rows = require(migrations lock table: migrations_lock,
[2/19/2021] [4:15:05 AM] [Global ] › ✖ error Migration table is already locked,

Originally created by @dicktsui on GitHub (Feb 19, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/905 Hi, I'm using rpi4+omv platform. I followed the installation guide and successfully used the NPM on first setup. However I get an error message after re-install the NPM via docker-compose. I already removed the NPM(app & db) in portainer and also deleted the NPM directory (command: rm -r NPM), but the problem still exists. Would you help to solve this issue or teach me how to manually release the lock (or deleting all the rows)? Thank you very much. [2/19/2021] [4:15:05 AM] [Migrate ] › ℹ info Current database version: 20190218060101, Can't take lock to run migrations: Migration table is already locked, If you are sure migrations are not running you can release the lock manually by deleting all the rows = require(migrations lock table: migrations_lock, [2/19/2021] [4:15:05 AM] [Global ] › ✖ error Migration table is already locked,

kerem

2026-02-26 06:34:18 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 06:34:19 +03:00

Author

Owner

@adams-j commented on GitHub (Oct 21, 2022):

same issue here

@adams-j commented on GitHub (Oct 21, 2022): same issue here

kerem commented

2026-02-26 06:34:19 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 18, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 18, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:34:19 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 29, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 29, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#764

No description provided.

Rows
Columns