Console request failed error

Error: console request failed.

What is the error message (if any)?

We are having this error, we’ve seen this from versions as old a 0.18X, and I think is related to a ulimit of the docker deployment environment and how the pg–protocol works, but I was unable to find information about the error in internet. I’m hopping somebody knows more about the internal way pg nodes work and giveme a light to follow.

The solution is to reboot the nodes, i just works.

{"execution":{"id":"3076831","url":"https://[redacted]/workflow/XX/executions/3076831","error":{"length":43,"name":"error","severity":"ERROR","code":"XX000","message":"Console request failed","stack":"error: Console request failed\n at Parser.parseErrorMessage (/usr/local/lib/node_modules/n8n/node_modules/pg-protocol/dist/parser.js:287:98)\n at Parser.handlePacket (/usr/local/lib/node_modules/n8n/node_modules/pg-protocol/dist/parser.js:126:29)\n at Parser.parse (/usr/local/lib/node_modules/n8n/node_modules/pg-protocol/dist/parser.js:39:38)\n at TLSSocket.<anonymous> (/usr/local/lib/node_modules/n8n/node_modules/pg-protocol/dist/index.js:11:42)\n at TLSSocket.emit (node:events:517:28)\n at TLSSocket.emit (node:domain:489:12)\n at addChunk (node:internal/streams/readable:335:12)\n at readableAddChunk (node:internal/streams/readable:308:9)\n at TLSSocket.Readable.push (node:internal/streams/readable:245:10)\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)"},"lastNodeExecuted":"api_saldo_log","mode":"webhook"},"workflow":{"id":"XX","name":"[cards]XXXX"}}

Please share your workflow

The it happens in different workflows when running Postgresql nodes.

Share the output returned by the last node

Information on your n8n setup

  • **n8n version: 1.12.0
  • Database (default: SQLite): Postgresql
  • n8n EXECUTIONS_PROCESS setting (default: own, main): queue
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker with elasticbeantalk with queue
  • Operating system: Amazon Linux

Hey @sebasortiz.dev,

That looks like an issue with Postgres, what version of Postgres are you running?

We run Postgresql in AWS RDS, version 13.10 updated to last minor

That version should be ok, Does postgres log anything?