Just wondering if anyone is experiencing
Just wondering if anyone is experiencing this and if there is anyway to solve this.
I think what ill do for the time being is to also put direct connections to the DB and figure out how to failover during these hours.
on the pg side of things:
2024-07-31 10:38:16.201 UTC [569089] [unknown]@[unknown] LOG: invalid length of startup packet
2024-07-31 10:20:26.462 UTC [568369] postgres@db LOG: could not receive data from client: Connection timed out
2024-07-31 10:20:26.462 UTC [568369] postgres@db LOG: unexpected EOF on client connection with an open transaction
5 Replies
Which DB provider are you using? Can you DM me your Hyperdrive config?
Also taking a look. Still the same config,
bd2f...?I use hetzner in falkenstein, self-hosted dedicated server. One vm with pg and 1 replication. I did try supabase and cockroachdb but for other reasons I opted for self host.
Ok, so to look through this, I do see exactly the 1 hour timeout block you're describing. I can also confirm that this is almost entirely exclusive to your config. I'm going to move to DM's for privacy while we debug this.
Oh really. Yes anything would be helpful. Thank you.