Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MODULE ERROR: Electric.Replication.PostgresConnector #1278

Closed
gudgeirbui opened this issue May 17, 2024 · 5 comments · Fixed by #1292
Closed

MODULE ERROR: Electric.Replication.PostgresConnector #1278

gudgeirbui opened this issue May 17, 2024 · 5 comments · Fixed by #1292
Assignees
Labels
bug Something isn't working

Comments

@gudgeirbui
Copy link

12:22:51.165 pid=<0.2848.0> [notice]     :alarm_handler: {:set, {:system_memory_high_watermark, []}}
12:22:51.275 pid=<0.3059.0> [info] Starting ElectricSQL 0.11.1 in direct_writes mode.
12:22:51.283 pid=<0.3060.0> [info] Running Electric.Plug.Router with Bandit 1.1.3 at :::5133 (http)
12:22:51.294 pid=<0.3374.0> origin=postgres_1 [info] Postgres.Client.with_conn(%{database: ~c"postgres", host: ~c"db.x.supabase.co", ip_addr: ~c"x:x:x:x:x:x:x", ipv6: true, nulls: [nil, :null, :undefined], password: ~c"******", port: 5432, ssl: true, ssl_opts: [server_name_indication: ~c"db.yymeltmaflntkkdlspah.supabase.co"], tcp_opts: [:inet6], timeout: 5000, username: ~c"postgres"})
12:22:51.319 pid=<0.3377.0> [warning] Description: ~c"Server authenticity is not verified since certificate path validation is not enabled"
     Reason: ~c"The option {verify, verify_peer} and one of the options 'cacertfile' or 'cacerts' are required to enable this."

12:22:52.117 pid=<0.3374.0> origin=postgres_1 [info] Successfully initialized origin postgres_1 at extension version
12:22:52.119 pid=<0.3383.0> [info] Starting Proxy server listening on port 65432
12:22:52.123 pid=<0.3393.0> [error] Postgrex.Protocol (#PID<0.3393.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3392.0> [error] Postgrex.Protocol (#PID<0.3392.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3391.0> [error] Postgrex.Protocol (#PID<0.3391.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3390.0> [error] Postgrex.Protocol (#PID<0.3390.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3389.0> [error] Postgrex.Protocol (#PID<0.3389.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3388.0> [error] Postgrex.Protocol (#PID<0.3388.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3387.0> [error] Postgrex.Protocol (#PID<0.3387.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3396.0> [error] Postgrex.Protocol (#PID<0.3396.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3394.0> [error] Postgrex.Protocol (#PID<0.3394.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:52.123 pid=<0.3395.0> [error] Postgrex.Protocol (#PID<0.3395.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:53.359 pid=<0.3396.0> [error] Postgrex.Protocol (#PID<0.3396.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:53.686 pid=<0.3387.0> [error] Postgrex.Protocol (#PID<0.3387.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:53.747 pid=<0.3390.0> [error] Postgrex.Protocol (#PID<0.3390.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:54.030 pid=<0.3394.0> [error] Postgrex.Protocol (#PID<0.3394.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:54.109 pid=<0.3391.0> [error] Postgrex.Protocol (#PID<0.3391.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:54.113 pid=<0.3388.0> [error] Postgrex.Protocol (#PID<0.3388.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (db.x.supabase.co:5432): non-existing domain - :nxdomain
12:22:54.121 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

I have removed identifying info. Trying to use 0.11 with docker, works when I run with electric-sql/electric:0.10

Copy link

linear bot commented May 17, 2024

@alco alco self-assigned this May 21, 2024
@alco alco added the bug Something isn't working label May 21, 2024
@alco
Copy link
Member

alco commented May 21, 2024

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

@barrelltech
Copy link

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
Copy link
Member

alco commented Jun 4, 2024

@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.

@alco alco closed this as completed in #1292 Jun 4, 2024
alco added a commit that referenced this issue Jun 4, 2024
…ns (#1292)

Fixes #1278.

I have verified this fix by building a custom Docker image for this
commit and deploying it to a DigitalOcean droplet that has IPv6
connectivity. The sync service connected to Supabase, the Ecto repo pool
initialized successfully.
@barrelltech
Copy link

it works now in canary! Thanks for the quick fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants