Error: write EPIPE

Questions
1

Describe the issue/error/question

Im getting the error below almost every 10minutes. Can someone explain me have to fix it?

What is the error message (if any)?

Error: write EPIPE at afterWriteDispatched (node:internal/stream_base_commons:160:15) at writeGeneric (node:internal/stream_base_commons:151:3) at Socket._writeGeneric (node:net:905:11) at Socket._write (node:net:917:8) at writeOrBuffer (node:internal/streams/writable:391:12) at _write (node:internal/streams/writable:332:10) at Socket.Writable.write (node:internal/streams/writable:336:10) at Connection._send (/usr/local/lib/node_modules/n8n/node_modules/pg/lib/connection.js:146:24) at Connection.sendSCRAMClientFinalMessage (/usr/local/lib/node_modules/n8n/node_modules/pg/lib/connection.js:139:10) at Client._handleAuthSASLContinue (/usr/local/lib/node_modules/n8n/node_modules/pg/lib/client.js:258:21)

Information on your n8n setup

  • n8n version:
    Lastest
  • Database you’re using (default: SQLite):
    Postgres
  • Running n8n with the execution process [own(default), main]:
    Main
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]:
    Google Cloud Run
2

@DonHolmen This error means that the TCP connection between the n8n instance and the postgres database is broken.
Since you are seeing the error regularly, that’d imply that there are regular network issues that are causing the TCP connection to be dropped.
Are you using Cloud SQL for hosting postgres? or is the DB running elsewhere?

2 Likes
3

Okay, thats weird. Could it be because of Cloud Run’s autoscaling?

Im using Cloud SQL for postgres.

4

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