The session <id> is not registered

[Cristi_Milea]

Describe the issue/error/question

I think I broke it…

After trying to manually run my flows, I sometimes get infinite loading on the “Execute Workflow” button, can’t stop it and if I refresh, all hell goes loose.

To get it running again, I’m cleaning manually the executions from my database running DELETE FROM execution_entity;, clear cache from browser (and initiate a new incognito session, because the old browser window is now doomed).

Sometimes I even need to recreate the docker container, as restarting does nothing.

What is the error message (if any)?

The session "988p0ix6klj" is not registered.
The session "988p0ix6klj" is not registered.
The session "988p0ix6klj" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
Attempt to read execution was blocked due to insufficient permissions
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.
The session "84yoeda3322" is not registered.

Access to n8n db is ok, host, user and password all functional.

Also, after this happens, If I refresh the page, I get a blank page and this in the console:

[Error] SyntaxError: No identifiers allowed directly after numeric literal
	(anonymous function) (ParameterInputList-fe1383b3.js:53)

And in MariaDB logs I found a lot of these:

2023-03-05 18:26:21 160 [Warning] Aborted connection 160 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)

Please share the workflow

It happens randomly on all flows.

Share the output returned by the last node

Flows don’t run anymore. Difficult to get it back running.

Information on your n8n setup

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

[Cristi_Milea]

This is the last flow of mine that got into this error:

It’s like this for about 10 minutes:

After I refresh the page I get this blank page:

Lots of logs like this in the db:

2023-03-05 18:33:29 185 [Warning] Aborted connection 185 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:33:49 186 [Warning] Aborted connection 186 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:34:26 187 [Warning] Aborted connection 187 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:34:41 188 [Warning] Aborted connection 188 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:35:21 190 [Warning] Aborted connection 190 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:35:41 191 [Warning] Aborted connection 191 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:36:21 192 [Warning] Aborted connection 192 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:36:40 193 [Warning] Aborted connection 193 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:37:21 194 [Warning] Aborted connection 194 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)
2023-03-05 18:37:41 195 [Warning] Aborted connection 195 to db: 'n8n' user: 'n8n' host: 'n8n-n8n-1.ee-global-backend-network' (Got an error reading communication packets)

LE: In order to connect again to n8n web gui, I need to close the safari incognito and open a new one, as it seems the old session is broken for good

LE2: it’s even worse now. could not get back in no matter how many incognito’s I opened. Had to run again DELETE FROM execution_entity; in order to make access the web app again…

[Cristi_Milea]

I’m running out of “tricks” to access the web app…

1. I cleared browser cache
2. Opened a new incognito
3. Deleted all executions
4. Restarted the container

Still the same error in console after refreshing the page.
As long as I don’t refresh… it works.

[MutedJam]

Hi @Cristi_Milea, I am very sorry to hear you’re having trouble. The error seems to be thrown by this file, with which I am unfortunately not familiar. Perhaps @netroy has an idea what might be causing these errors for you?

[netroy]

Are you running MariaDB also in a container?

[Cristi_Milea]

Yes. n8n in a container, MariaDB in a different container.

[keajer]

I have the same issue with running an imported workflow. I can do any of my own workflows fine.

[Jon]

Hey @keajer,

Can you open a new topic and complete the template so we can make sure the issue you are seeing is the same and not just similar

[netroy]

@Cristi_Milea This looks like there are some kind of connectivity issues between the n8n and mariadb.
That’s the reason behind the Got an error reading communication packets errors.
The The session "*" is not registered. errors are coming from the frontend disconnecting from the backend in the middle of a manual execution.

Can you please run a new docker-compose setup, and try to reproduce this issue there? That way we can (hopefully) isolate the issue, to be able to fix it.

[Cristi_Milea]

Hi and sorry for the late response. Unfortunately my deadline was close so I decided to move n8n from MariaDB to Postgres and the errors disappeared.
Managed to finish my sync workflow without getting into this bug, so maybe there was something wrong in the database. Sorry again, for I couldn’t help with more debugging on this.

[rostamiani]

n8n 0.217.2
postgres 11

I have similar problem with Postgres. I imported all workflows from SQLite version
And there is a lot of Postgres errors like this at docker logs:

2023-04-18 06:30:33.919 UTC [2573768] STATEMENT:  INSERT INTO "public"."workflow_statistics"("count", "latestEvent", "name", "workflowId") VALUES ($1, $2, $3, $4)
2023-04-18 06:30:35.017 UTC [2573768] ERROR:  duplicate key value violates unique constraint "workflow_statistics_pkey"
2023-04-18 06:30:35.017 UTC [2573768] DETAIL:  Key ("workflowId", name)=(5, data_loaded) already exists.
2023-04-18 06:30:35.017 UTC [2573768] STATEMENT:  INSERT INTO "public"."workflow_statistics"("count", "latestEvent", "name", "workflowId") VALUES ($1, $2, $3, $4)
2023-04-18 06:30:35.136 UTC [2573768] ERROR:  duplicate key value violates unique constraint "workflow_statistics_pkey"
2023-04-18 06:30:35.136 UTC [2573768] DETAIL:  Key ("workflowId", name)=(5, production_success) already exists.
2023-04-18 06:30:35.136 UTC [2573768] STATEMENT:  INSERT INTO "public"."workflow_statistics"("count", "latestEvent", "name", "workflowId") VALUES ($1, $2, $3, $4)
2023-04-18 08:02:17.834 UTC [2569723] LOG:  could not receive data from client: Connection timed out
2023-04-18 10:42:51.015 UTC [2597960] ERROR:  duplicate key value violates unique constraint "workflow_statistics_pkey"
2023-04-18 10:42:51.015 UTC [2597960] DETAIL:  Key ("workflowId", name)=(10, manual_error) already exists.
2023-04-18 10:42:51.015 UTC [2597960] STATEMENT:  INSERT INTO "public"."workflow_statistics"("count", "latestEvent", "name", "workflowId") VALUES ($1, $2, $3, $4)
2023-04-18 10:43:55.753 UTC [2597987] ERROR:  duplicate key value violates unique constraint "workflow_statistics_pkey"
2023-04-18 10:43:55.753 UTC [2597987] DETAIL:  Key ("workflowId", name)=(10, manual_error) already exists.
2023-04-18 10:43:55.753 UTC [2597987] STATEMENT:  INSERT INTO "public"."workflow_statistics"("count", "latestEvent", "name", "workflowId") VALUES ($1, $2, $3, $4)
2023-04-18 10:45:04.164 UTC [2598098] ERROR:  duplicate key value violates unique constraint "workflow_statistics_pkey"
2023-04-18 10:45:04.164 UTC [2598098] DETAIL:  Key ("workflowId", name)=(10, manual_success) already exists.
2023-04-18 10:45:04.164 UTC [2598098] STATEMENT:  INSERT INTO "public"."workflow_statistics"("count", "latestEvent", "name", "workflowId") VALUES ($1, $2, $3, $4)
2023-04-18 11:01:25.738 UTC [2587028] LOG:  could not receive data from client: Connection timed out
2023-04-18 13:00:13.239 UTC [2611107] ERROR:  duplicate key value violates unique constraint "workflow_statistics_pkey"
2023-04-18 13:00:13.239 UTC [2611107] DETAIL:  Key ("workflowId", name)=(4, production_error) already exists.
2023-04-18 13:00:13.239 UTC [2611107] STATEMENT:  INSERT INTO "public"."workflow_statistics"("count", "latestEvent", "name", "workflowId") VALUES ($1, $2, $3, $4)

[MutedJam]

Hi @rostamiani, I am sorry to hear you’re having trouble. The PostgreSQL errors don’t seem to be related to the main problem discussed in this thread, you’d want to follow this one instead for updates.

[Loan_J]

Hi,
Getting about the same error on an npm setup:

{"level":"error","message":"The session \"ozhgc8rkdoi\" is not registered.","metadata":{"file":"abstract.push.js","function":"send","sessionId":"ozhgc8rkdoi","timestamp":"2023-06-08T08:56:58.251Z"}}
{"level":"error","message":"The session \"ozhgc8rkdoi\" is not registered.","metadata":{"file":"abstract.push.js","function":"send","sessionId":"ozhgc8rkdoi","timestamp":"2023-06-08T08:56:58.251Z"}}

I have ~~600k lines of logs like this