Hello N8N community? is there anyone who knows how to solve it?

Questions
,
1

Describe the problem/error/question

Failed to get executions count from Postgres: TypeError: Cannot read properties of undefined (reading ‘n_live_tup’)
Attempt to read execution was blocked due to insufficient permissions

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Describe the problem/error/question

I’m getting weird error? Is there anyone who can handle this

What is the error message (if any)?

Failed to get executions count from Postgres: TypeError: Cannot read properties of undefined (reading ‘n_live_tup’)
Attempt to read execution was blocked due to insufficient permissions
The session “w0capzkbdhl” is not registered.

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Hi @Kylychbek, I am very sorry you’re having trouble.

Perhaps you can share a few additional details about your setup? In particular, which version of n8n you are running, how you deployed n8n (especially which database including version you have in use) and which when exactly you are seeing the error (as in what action are you performing when this error occurs)?

Is this crashing n8n for you or causing any other noticeable problem apart from the error being logged?

6

I’m actually running my n8n on kubernetes deployment with N8n deployment and worker deployment image versions are 1.3.1 both, and database is Postgres 13.10, so I’m not able run my workflows since those erros appeared

7

I am afraid I don’t seem to be able to reproduce this on my end. Are you also seeing this problem with a fresh n8n instance started against an empty database? And does the issue persist for you when using the latest n8n version n8n@1.9.3?

8

i do have exact error with the same configurations

Failed to get executions count from Postgres: Cannot read properties of undefined (reading ‘n_live_tup’)
The session “jwy0821m6q” is not registered.
The session “jwy0821m6q” is not registered.
The session “jwy0821m6q” is not registered.
The session “jwy0821m6q” is not registered.
The session “jwy0821m6q” is not registered.
The session “jwy0821m6q” is not registered.
Failed to get executions count from Postgres: Cannot read properties of undefined (reading ‘n_live_tup’)

9

hello! are you suggesting to update the version of n8n?

i did try to update the version to 1.9.3, however the issue persist. please, advise

10

also, the n8n pods are restarting very often

11

Hi @Nargiza_Fernandez, I am very sorry for this. As mentioned above I was unfortunately not able to reproduce this on my using a setup like below and two active workflow querying an API.

docker-compose.yml 
services:
  postgres:
    image: postgres:13.10
    restart: unless-stopped
    environment:
      - POSTGRES_USER=n8n
      - POSTGRES_PASSWORD=n8n
      - POSTGRES_DB=n8n
    volumes:
      - ./db_data:/var/lib/postgresql/data
    ports:
      - 5432:5432
    healthcheck:
      test: ['CMD-SHELL', 'pg_isready -h localhost -U n8n -d n8n']
      interval: 5s
      timeout: 5s
      retries: 10
  redis:
    image: redis:6-alpine
    restart: unless-stopped
    healthcheck:
      test: ['CMD', 'redis-cli', 'ping']
      interval: 5s
      timeout: 5s
      retries: 10
  n8n_main:
    image: n8nio/n8n:1.9.3
    restart: unless-stopped
    environment:
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=n8n
      - DB_POSTGRESDB_USER=n8n
      - DB_POSTGRESDB_PASSWORD=n8n
      - QUEUE_HEALTH_CHECK_ACTIVE=true
      - N8N_DIAGNOSTICS_ENABLED=false
      - QUEUE_BULL_REDIS_HOST=redis
      - EXECUTIONS_MODE=queue
      - N8N_LOG_LEVEL=debug
    ports:
      - 5678:5678
    volumes:
      - ./n8n_data:/home/node/.n8n
    depends_on:
      postgres:
        condition: service_healthy
      redis:
        condition: service_healthy
  n8n_worker:
    image: n8nio/n8n:1.9.3
    restart: unless-stopped
    environment:
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=n8n
      - DB_POSTGRESDB_USER=n8n
      - DB_POSTGRESDB_PASSWORD=n8n
      - QUEUE_HEALTH_CHECK_ACTIVE=true
      - N8N_DIAGNOSTICS_ENABLED=false
      - QUEUE_BULL_REDIS_HOST=redis
      - EXECUTIONS_MODE=queue
      - N8N_LOG_LEVEL=debug
    command: worker
    volumes:
      - ./n8n_data:/home/node/.n8n
    depends_on:
      postgres:
        condition: service_healthy
      redis:
        condition: service_healthy
      n8n_main:
        condition: service_started

n8n starts as expected, and workflows are also executed as expected

So without additional details on how to reproduce the problem I am unfortunately stuck here myself, but I’ll add this to our internal bug tracker for a closer look by the engineering team.