Skip to content

Instantly share code, notes, and snippets.

@ondratra

ondratra/gist:614ef0d5fb5fbd75607b1b3ba8c1bd68

Created February 13, 2023 10:46
Show Gist options
  • Save ondratra/614ef0d5fb5fbd75607b1b3ba8c1bd68 to your computer and use it in GitHub Desktop.
Save ondratra/614ef0d5fb5fbd75607b1b3ba8c1bd68 to your computer and use it in GitHub Desktop.
Download ZIP
Blockscout error.log
Raw
gistfile1.txt
2023-02-13T10:26:47.176 application=db_connection [error] Postgrex.Protocol (#PID<0.189.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T10:26:47.176 application=db_connection [error] Postgrex.Protocol (#PID<0.185.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T10:26:47.176 application=db_connection [error] Postgrex.Protocol (#PID<0.190.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T10:26:47.176 application=db_connection [error] Postgrex.Protocol (#PID<0.184.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T10:26:47.177 [error] GenServer #PID<0.197.0> terminating
** (DBConnection.ConnectionError) tcp recv (idle): closed
(db_connection 2.4.3) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 3.17) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
2023-02-13T10:26:47.181 [error] GenServer #PID<0.202.0> terminating
** (DBConnection.ConnectionError) tcp recv (idle): closed
(db_connection 2.4.3) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 3.17) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
2023-02-13T10:26:47.182 [error] GenServer #PID<0.206.0> terminating
** (DBConnection.ConnectionError) tcp recv (idle): closed
(db_connection 2.4.3) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 3.17) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
2023-02-13T10:26:47.182 [error] GenServer #PID<0.210.0> terminating
** (DBConnection.ConnectionError) tcp recv (idle): closed
(db_connection 2.4.3) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 3.17) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
2023-02-13T10:26:48.353 application=db_connection [error] Postgrex.Protocol (#PID<0.190.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:26:48.637 application=db_connection [error] Postgrex.Protocol (#PID<0.185.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:26:49.184 application=db_connection [error] Postgrex.Protocol (#PID<0.184.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:26:50.080 application=db_connection [error] Postgrex.Protocol (#PID<0.189.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:26:50.164 application=ecto_sql [error] Could not create schema migrations table. This error usually happens due to the following:
* The database does not exist
* The "schema_migrations" table, which Ecto uses for managing
migrations, was defined by another library
* There is a deadlock while migrating (such as using concurrent
indexes with a migration_lock)
To fix the first issue, run "mix ecto.create".
To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create". Alternatively you may configure Ecto to use
another table and/or repository for managing migrations:
config :explorer, Explorer.Repo,
migration_source: "some_other_table_for_schema_migrations",
migration_repo: AnotherRepoForSchemaMigrations
The full error report is shown below.
2023-02-13T10:26:51.227 application=db_connection [error] Postgrex.Protocol (#PID<0.189.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:26:51.227 application=db_connection [error] Postgrex.Protocol (#PID<0.184.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:26:51.227 application=db_connection [error] Postgrex.Protocol (#PID<0.185.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:26:51.227 application=db_connection [error] Postgrex.Protocol (#PID<0.190.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:26:56.074 application=db_connection [error] Postgrex.Protocol (#PID<0.4182.0>) failed to connect: ** (Postgrex.Error) FATAL 53300 (too_many_connections) sorry, too many clients already
2023-02-13T10:30:16.509 application=db_connection [error] Postgrex.Protocol (#PID<0.4190.0>) failed to connect: ** (Postgrex.Error) FATAL 53300 (too_many_connections) sorry, too many clients already
2023-02-13T10:40:31.992 application=db_connection [error] Postgrex.Protocol (#PID<0.184.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T10:40:31.992 application=db_connection [error] Postgrex.Protocol (#PID<0.185.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T10:40:31.992 application=db_connection [error] Postgrex.Protocol (#PID<0.190.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T10:40:31.992 application=db_connection [error] Postgrex.Protocol (#PID<0.189.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T10:40:31.991 [error] GenServer #PID<0.197.0> terminating
** (DBConnection.ConnectionError) tcp recv (idle): closed
(db_connection 2.4.3) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 3.17) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
2023-02-13T10:40:32.000 [error] GenServer #PID<0.202.0> terminating
** (DBConnection.ConnectionError) tcp recv (idle): closed
(db_connection 2.4.3) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 3.17) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
2023-02-13T10:40:32.000 [error] GenServer #PID<0.206.0> terminating
** (DBConnection.ConnectionError) tcp recv (idle): closed
(db_connection 2.4.3) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 3.17) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
2023-02-13T10:40:32.001 [error] GenServer #PID<0.210.0> terminating
** (DBConnection.ConnectionError) tcp recv (idle): closed
(db_connection 2.4.3) lib/db_connection/connection.ex:100: DBConnection.Connection.connect/2
(connection 1.1.0) lib/connection.ex:622: Connection.enter_connect/5
(stdlib 3.17) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Last message: nil
State: Postgrex.Protocol
2023-02-13T10:40:33.037 application=db_connection [error] Postgrex.Protocol (#PID<0.189.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:40:33.468 application=db_connection [error] Postgrex.Protocol (#PID<0.190.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:40:34.109 application=db_connection [error] Postgrex.Protocol (#PID<0.184.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:40:34.446 application=db_connection [error] Postgrex.Protocol (#PID<0.185.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:40:34.979 application=ecto_sql [error] Could not create schema migrations table. This error usually happens due to the following:
* The database does not exist
* The "schema_migrations" table, which Ecto uses for managing
migrations, was defined by another library
* There is a deadlock while migrating (such as using concurrent
indexes with a migration_lock)
To fix the first issue, run "mix ecto.create".
To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create". Alternatively you may configure Ecto to use
another table and/or repository for managing migrations:
config :explorer, Explorer.Repo,
migration_source: "some_other_table_for_schema_migrations",
migration_repo: AnotherRepoForSchemaMigrations
The full error report is shown below.
2023-02-13T10:40:36.033 application=db_connection [error] Postgrex.Protocol (#PID<0.185.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:40:36.033 application=db_connection [error] Postgrex.Protocol (#PID<0.184.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:40:36.033 application=db_connection [error] Postgrex.Protocol (#PID<0.189.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:40:36.033 application=db_connection [error] Postgrex.Protocol (#PID<0.190.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "blockscout" does not exist
2023-02-13T10:40:41.345 application=db_connection [error] Postgrex.Protocol (#PID<0.4143.0>) failed to connect: ** (Postgrex.Error) FATAL 53300 (too_many_connections) sorry, too many clients already
2023-02-13T10:44:01.466 application=db_connection [error] Postgrex.Protocol (#PID<0.4148.0>) failed to connect: ** (Postgrex.Error) FATAL 53300 (too_many_connections) sorry, too many clients already
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment