Blockscout error.log 2

gistfile1.txt

2023-02-13T13:20:04.951 application=db_connection [error] Postgrex.Protocol (#PID<0.185.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T13:20:04.951 application=db_connection [error] Postgrex.Protocol (#PID<0.189.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T13:20:04.951 application=db_connection [error] Postgrex.Protocol (#PID<0.190.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T13:20:04.951 application=db_connection [error] Postgrex.Protocol (#PID<0.184.0>) failed to connect: ** (DBConnection.ConnectionError) tcp recv (idle): closed
2023-02-13T13:20:04.951 [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-13T13:20:04.958 [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-13T13:20:04.959 [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-13T13:20:04.961 [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-13T13:20:05.980 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-13T13:20:06.358 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-13T13:20:06.387 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-13T13:20:07.320 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-13T13:20:07.698 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-13T13:20:07.937 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-13T13:20:08.959 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-13T13:20:08.959 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-13T13:20:08.959 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-13T13:20:08.959 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