[N8N]- Self Hosted Instance -> Worker logs -> Lost/Recovered Redis connection

Questions
,
1

I am using a self-hosted instance of n8n, and I’ve noticed and in the worker logs we have many instance of the below errors logs on a daily basis and frequent basis.

N8N version 1.71.3

Would be thankful if anyone can highlight the issue if it is related with some configuration at my end. Thank You
n8n worker is now ready

  • Version: 1.71.3

  • Concurrency: 10

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Worker started execution 16525 (job 11716)

Worker finished execution 16525 (job 11716)

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Worker started execution 16528 (job 11718)

Worker finished execution 16528 (job 11718)

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Lost Redis connection. Trying to reconnect in 1s… (0s/10s)

Recovered Redis connection

Worker started execution 16529 (job 11719)

Worker finished execution 16529 (job 11719)

Worker started execution 16530 (job 11721)

Worker finished execution 16530 (job 11721)

Worker started execution 16534 (job 11724)

Worker finished execution 16534 (job 11724)

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

@Sandeep These frequent Redis disconnections can be fixed by:

  1. Increase connection timeout settings:
QUEUE_BULL_REDIS_CONNECTION_TIMEOUT=30000
QUEUE_BULL_REDIS_TIMEOUT=30000
  1. Enable Redis keepalive:
QUEUE_BULL_REDIS_KEEP_ALIVE_DELAY=15000
  1. Check for network issues
  2. Monitor Redis memory usage
  3. Update to latest n8n version:
  • Newer versions (1.80+) have improved Redis connection handling

Updating n8n might be your easiest solution if you are lucky

4

Thanks @Yo_its_prakash We did update the N8N version to 1.8.2 and after that there are very few instances of such errors. We will keep monitoring and thanks for your advice.

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.