Describe the issue/error/question
I have a workflow that is running pretty well, however i am running into an issue when the number of calls to the webhook is pretty high. Then I am seeing an error message in the log screen of “Unknown”
If i rerun the workflow everything works fine.
I am running n8n in docker (0.158.0). Could this be a server limitation ? I am running ubuntu with 1GB memory and 1 CPU
Hey @Surge.Media, I am sorry to hear you’re having trouble. Your assumption seems pretty likely to me. This status would typically come up if the server goes down during the workflow execution. It seems like these executions from your screenshot all happened around a similar time, so maybe your server ran out of memory?
In a first step you might want to check your docker logs around the time this has happened.
Thanks @MutedJam I will look at increasing server memory.
I am not that familiar with docker - could you let me know where i find the logs ?
Checking docker logs could be done through the
docker logs command which is documented here. So something like
docker logs --timestamps --since 2022-02-25T15:10:00Z n8n (assuming n8n is your docker container name; you might need to adjust the timestamp depending on your time zone).
As for adding more memory, I’d say it’s worth verifying whether this is actually a memory problem first.
These are some of the errors I am seeing:
(node:7) UnhandledPromiseRejectionWarning: QueryFailedError: SQLITE_BUSY: database is locked
at new QueryFailedError (/usr/local/lib/node_modules/n8n/node_modules/typeorm/error/QueryFailedError.js:11:28)
at Statement.handler (/usr/local/lib/node_modules/n8n/node_modules/typeorm/driver/sqlite/SqliteQueryRunner.js:76:38)
at Statement.replacement (/usr/local/lib/node_modules/n8n/node_modules/sqlite3/lib/trace.js:25:27)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:7) 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: 7)
(node:7) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I have gone ahead and update the server to 2 CPU + 2 GB Mem.
I guess it looks like a DB issue not being able to write fast enough ?