-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
database is locked #278
Comments
and fyi, i don't get a config.js when starting the container first time, it comes and disapear :-/ |
Are you running multiple instances of cross-seed at the same time? |
No im only running one in docker |
I have this although |
looks like that might be the culprit. Try killing that |
It came back after killing it and got this in cross-seed log |
so that line is tied to the docker it seems |
cross-seed - https://hub.docker.com/r/mmgoodnow/cross-seedcross-seed: |
can you try these steps? first, stop the docker container. Then,
|
|
Can you post your config (redacting relevant parts)? I'm somewhat out of ideas |
is there anything else that's weird about your setup? network file shares, maybe? |
Can't take lock to run migrations: update |
I'm seeing this too. Mostly when I
|
this is tentatively fixed in #341
|
I have gotten this error a lot lately though I have made a config error in the conf. so I made a new one. But the error was back
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 21)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 24)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 27)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 30)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 33)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 36)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 39)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 42)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 45)(node:1) UnhandledPromiseRejectionWarning: SqliteError: select
last_run
fromjob_log
wherename
= 'search' limit 1 - database is locked(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 48)`The text was updated successfully, but these errors were encountered: