New install, self-hosting. Execution never ends, keeps spinning

Describe the issue/error/question

Can’t execute any workflows. I click “Execute Workflow”, the spinner starts spinning and never stops. I click the “Stop” icon, another spinner appears and never stops spinning either.

Then I stop the docker container, and only then do I get a message in the UI about the workflow completing successfully.

docker-compose.yml

version: "2"

services:
  n8n:
    image: n8nio/n8n
    container_name: "n8n"
    hostname: "n8n"
    restart: always
    ports: 
      - 54356:5678
 
    environment:
      - NODE_ENV=production
      - GENERIC_TIMEZONE="Europe/Kiev"
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=user
      - N8N_BASIC_AUTH_PASSWORD=password
      - N8N_HOST=n8n.mysite.com
      - WEBHOOK_URL=https://n8n.mysite.com/
      - N8N_PROTOCOL=https
      - N8N_PERSONALIZATION_ENABLED=false
      - N8N_DIAGNOSTICS_ENABLED=false
      - N8N_LOG_LEVEL=debug
    volumes:
      - /home/user/n8n/data:/home/node/.n8n

What is the error message (if any)?

n8n    | 2022-01-13T16:58:52.835Z | debug    | Wait tracker querying database for waiting executions {"file":"WaitTracker.js","function":"getwaitingExecutions"}
n8n    | 2022-01-13T16:58:55.152Z | verbose  | Initializing n8n sub-process {"pid":22,"file":"WorkflowRunnerProcess.js","function":"runWorkflow"}
n8n    | 2022-01-13T16:58:55.159Z | debug    | Received child process message of type start for execution ID 5. {"executionId":"5","file":"WorkflowRunner.js"}
n8n    | 2022-01-13T16:58:55.209Z | verbose  | Workflow execution started {"file":"WorkflowExecute.js","function":"processRunExecutionData"}
n8n    | 2022-01-13T16:58:55.212Z | debug    | Start processing node "Start" {"node":"Start","file":"WorkflowExecute.js"}
n8n    | 2022-01-13T16:58:55.213Z | debug    | Received child process message of type processHook for execution ID 5. {"executionId":"5","file":"WorkflowRunner.js"}
n8n    | 2022-01-13T16:58:55.213Z | debug    | Running node "Start" started {"node":"Start","file":"WorkflowExecute.js"}
n8n    | 2022-01-13T16:58:55.215Z | debug    | Running node "Start" finished successfully {"node":"Start","file":"WorkflowExecute.js"}
n8n    | 2022-01-13T16:58:55.216Z | debug    | Executing hook (hookFunctionsPush) {"executionId":"5","sessionId":"jwcv7gc1wsj","file":"WorkflowExecuteAdditionalData.js","function":"workflowExecuteBefore"}
n8n    | 2022-01-13T16:58:55.217Z | debug    | Send data of type "executionStarted" to editor-UI {"dataType":"executionStarted","sessionId":"jwcv7gc1wsj","file":"Push.js","function":"send"}
n8n    | 2022-01-13T16:58:55.218Z | verbose  | Workflow execution finished successfully {"file":"WorkflowExecute.js","function":"processSuccessExecution"}
n8n    | 2022-01-13T16:58:55.232Z | debug    | Received child process message of type processHook for execution ID 5. {"executionId":"5","file":"WorkflowRunner.js"}
n8n    | 2022-01-13T16:58:55.234Z | debug    | Executing hook on node "Start" (hookFunctionsPush) {"executionId":"5","sessionId":"jwcv7gc1wsj","file":"WorkflowExecuteAdditionalData.js","function":"nodeExecuteBefore"}
n8n    | 2022-01-13T16:58:55.235Z | debug    | Send data of type "nodeExecuteBefore" to editor-UI {"dataType":"nodeExecuteBefore","sessionId":"jwcv7gc1wsj","file":"Push.js","function":"send"}
n8n    | 2022-01-13T16:58:55.237Z | debug    | Received child process message of type processHook for execution ID 5. {"executionId":"5","file":"WorkflowRunner.js"}
n8n    | 2022-01-13T16:58:55.238Z | debug    | Executing hook on node "Start" (hookFunctionsPush) {"executionId":"5","sessionId":"jwcv7gc1wsj","file":"WorkflowExecuteAdditionalData.js","function":"nodeExecuteAfter"}
n8n    | 2022-01-13T16:58:55.239Z | debug    | Send data of type "nodeExecuteAfter" to editor-UI {"dataType":"nodeExecuteAfter","sessionId":"jwcv7gc1wsj","file":"Push.js","function":"send"}
n8n    | 2022-01-13T16:58:55.240Z | debug    | Received child process message of type processHook for execution ID 5. {"executionId":"5","file":"WorkflowRunner.js"}
n8n    | 2022-01-13T16:58:55.242Z | debug    | Executing hook (hookFunctionsSave) {"executionId":"5","file":"WorkflowExecuteAdditionalData.js","function":"workflowExecuteAfter"}
n8n    | 2022-01-13T16:58:55.248Z | debug    | Received child process message of type end for execution ID 5. {"executionId":"5","file":"WorkflowRunner.js"}
n8n    | 2022-01-13T16:58:55.265Z | debug    | Executing hook (hookFunctionsPush) {"executionId":"5","sessionId":"jwcv7gc1wsj","file":"WorkflowExecuteAdditionalData.js","function":"workflowExecuteAfter"}
n8n    | 2022-01-13T16:58:55.267Z | debug    | Save execution progress to database for execution ID 5  {"executionId":"5","file":"WorkflowExecuteAdditionalData.js","function":"workflowExecuteAfter"}
n8n    | 2022-01-13T16:58:55.268Z | debug    | Send data of type "executionFinished" to editor-UI {"dataType":"executionFinished","sessionId":"jwcv7gc1wsj","file":"Push.js","function":"send"}
n8n    | 2022-01-13T16:59:52.855Z | debug    | Wait tracker querying database for waiting executions {"file":"WaitTracker.js","function":"getwaitingExecutions"}
n8n    | 2022-01-13T17:00:52.875Z | debug    | Wait tracker querying database for waiting executions {"file":"WaitTracker.js","function":"getwaitingExecutions"}

Please share the workflow

{
  "nodes": [],
  "connections": {}
}

I’m just trying to get the app to work at all, so I’m only running the basic “Start” node

Share the output returned by the last node

There is not output, because execution gets stuck in a loop (at least as far as the UI is concerned) and never ends

Information on your n8n setup

  • n8n version: latest
  • Database you’re using (default: SQLite): default
  • Running n8n with the execution process [own(default), main]: default
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: docker

What else I tried

Was using the Brave browser initially. Tried with Chromium too. Then disabled every extension in Chromium and tried again. Got the same behavior every time :frowning:

Hey @elmaester,

Have you tried adding a set node to see if it does anything? Maybe it just fails if there is no nodes.

Hey @jon

I initially tried to read an RSS feed and it behaved the same. Also Interval and cron job. There’s no difference

That is odd, have you tried deleting the container and the stored data from the volume and setting it up again?

It certainly is odd, seeing how nobody else seems to be having similar problems. I’m at a loss.

And yes, I have tried deleting the container and the data, before asking my question. Nothing changed.