MODULE ERROR: Electric.Replication.PostgresConnector about electric

[barrelltech]

it works now in canary! Thanks for the quick fix

[linear]

VAX-1870 MODULE ERROR: Electric.Replication.PostgresConnector

[alco]

@gudgeirbui Thanks for reporting! This is a bug in the latest release.

[barrelltech]

Not sure if it's helpful, but just wanted to let you know I'm running into the same issue. Identifying info also removed:

07:35:26.128 pid=<0.3393.0> [error] Postgrex.Protocol (#PID<0.3393.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.128 pid=<0.3392.0> [error] Postgrex.Protocol (#PID<0.3392.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.128 pid=<0.3390.0> [error] Postgrex.Protocol (#PID<0.3390.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.129 pid=<0.3389.0> [error] Postgrex.Protocol (#PID<0.3389.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.129 pid=<0.3396.0> [error] Postgrex.Protocol (#PID<0.3396.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.129 pid=<0.3388.0> [error] Postgrex.Protocol (#PID<0.3388.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.128 pid=<0.3391.0> [error] Postgrex.Protocol (#PID<0.3391.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.129 pid=<0.3387.0> [error] Postgrex.Protocol (#PID<0.3387.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.129 pid=<0.3394.0> [error] Postgrex.Protocol (#PID<0.3394.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:26.129 pid=<0.3395.0> [error] Postgrex.Protocol (#PID<0.3395.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
 WARN Reaped child process with pid: 374 and signal: SIGUSR1, core dumped? false
07:35:27.348 pid=<0.3389.0> [error] Postgrex.Protocol (#PID<0.3389.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:27.481 pid=<0.3387.0> [error] Postgrex.Protocol (#PID<0.3387.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:27.851 pid=<0.3392.0> [error] Postgrex.Protocol (#PID<0.3392.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:28.053 pid=<0.3396.0> [error] Postgrex.Protocol (#PID<0.3396.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:28.053 pid=<0.3393.0> [error] Postgrex.Protocol (#PID<0.3393.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.$SUPABASE_ID.supabase.co:5432): non-existing domain - :nxdomain
07:35:28.082 pid=<0.3374.0> origin=postgres_1 [error] PostgresConnectorSup failed to start child Electric.Satellite.ClientReconnectionInfo with reason: {%DBConnection.ConnectionError{message: "connection not available and request was dropped from queue after 2000ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\n\n  1. Ensuring your database is available and that you can connect to it\n  2. Tracking down slow queries and making sure they are running fast enough\n  3. Increasing the pool_size (although this increases resource consumption)\n  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\n\nSee DBConnection.start_link/2 for more information\n", severity: :error, reason: :queue_timeout}, [{DBConnection, :run, 3, [file: ~c"lib/db_connection.ex", line: 960, error_info: %{module: Exception}]}, {Electric.Satellite.ClientReconnectionInfo, :init, 1, [file: ~c"lib/electric/satellite/client_reconnection_info.ex", line: 855]}, {:gen_server, :init_it, 2, [file: ~c"gen_server.erl", line: 851]}, {:gen_server, :init_it, 6, [file: ~c"gen_server.erl", line: 814]}, {:proc_lib, :init_p_do_apply, 3, [file: ~c"proc_lib.erl", line: 240]}]}.
▓ ┌────────────────────────────────────────────────────────┐
▓ │  MODULE ERROR: Electric.Replication.PostgresConnector  │
▓ ┕━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┙
▓
▓ Failed to start child Electric.Satellite.ClientReconnectionInfo:
▓   {%DBConnection.ConnectionError{message: "connection not available and request was dropped from queue after 2000ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\n\n  1. Ensuring your database is available and that you can connect to it\n  2. Tracking down slow queries and making sure they are running fast enough\n  3. Increasing the pool_size (although this increases resource consumption)\n  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\n\nSee DBConnection.start_link/2 for more information\n", severity: :error, reason: :queue_timeout}, [{DBConnection, :run, 3, [file: ~c"lib/db_connection.ex", line: 960, error_info: %{module: Exception}]}, {Electric.Satellite.ClientReconnectionInfo, :init, 1, [file: ~c"lib/electric/satellite/client_reconnection_info.ex", line: 855]}, {:gen_server, :init_it, 2, [file: ~c"gen_server.erl", line: 851]}, {:gen_server, :init_it, 6, [file: ~c"gen_server.erl", line: 814]}, {:proc_lib, :init_p_do_apply, 3, [file: ~c"proc_lib.erl", line: 240]}]}
▓
▓ Please file a new issue on GitHub[1], including the contents of this error.
▓
▓ [1]: https://github.com/electric-sql/electric/issues
••• Shutting down •••
[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
 INFO Main child exited normally with code: 1
 WARN Reaped child process with pid: 380 and signal: SIGUSR1, core dumped? false
 INFO Starting clean up.
[    5.442186] reboot: Restarting system
machine has reached its max restart count (10)

Will watch the other thread for updates!

[alco]

@barrelltech Thanks for chiming in! And sorry this has taken a while to fix. We're aiming to publish a patch release with this fixed this week.