pi@raspberrypi:~ $ docker-compose stop teslamate2
Stopping pi_teslamate2_1 ... done
pi@raspberrypi:~ $ docker-compose up teslamate2
Starting pi_teslamate2_1 ... done
Attaching to pi_teslamate2_1
teslamate2_1 | 2021-02-14 08:30:05.207 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:05.207 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:06.910 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:08.050 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:08.138 [error] Could not create schema migrations table. This error usually happens due to the following:
teslamate2_1 |
teslamate2_1 | * The database does not exist
teslamate2_1 | * The "schema_migrations" table, which Ecto uses for managing
teslamate2_1 | migrations, was defined by another library
teslamate2_1 | * There is a deadlock while migrating (such as using concurrent
teslamate2_1 | indexes with a migration_lock)
teslamate2_1 |
teslamate2_1 | To fix the first issue, run "mix ecto.create".
teslamate2_1 |
teslamate2_1 | To address the second, you can run "mix ecto.drop" followed by
teslamate2_1 | "mix ecto.create". Alternatively you may configure Ecto to use
teslamate2_1 | another table and/or repository for managing migrations:
teslamate2_1 |
teslamate2_1 | config :teslamate, TeslaMate.Repo,
teslamate2_1 | migration_source: "some_other_table_for_schema_migrations",
teslamate2_1 | migration_repo: AnotherRepoForSchemaMigrations
teslamate2_1 |
teslamate2_1 | The full error report is shown below.
teslamate2_1 |
teslamate2_1 | ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2958ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
teslamate2_1 |
teslamate2_1 | 1. Tracking down slow queries and making sure they are running fast enough
teslamate2_1 | 2. Increasing the pool_size (albeit it increases resource consumption)
teslamate2_1 | 3. Allowing requests to wait longer by increasing :queue_target and :queue_interval
teslamate2_1 |
teslamate2_1 | See DBConnection.start_link/2 for more information
teslamate2_1 |
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:751: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate2_1 | (elixir 1.11.3) lib/enum.ex:1411: Enum."-map/2-lists^map/1-0-"/2
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:838: Ecto.Adapters.SQL.execute_ddl/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:669: Ecto.Migrator.verbose_schema_migration/3
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:498: Ecto.Migrator.lock_for_migrations/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:413: Ecto.Migrator.run/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:145: Ecto.Migrator.with_repo/3
teslamate2_1 | (teslamate 1.21.3) lib/teslamate/release.ex:9: anonymous fn/2 in TeslaMate.Release.migrate/0
teslamate2_1 | 2021-02-14 08:30:12.125 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:12.126 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:14.790 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:14.832 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:15.044 [error] Could not create schema migrations table. This error usually happens due to the following:
teslamate2_1 |
teslamate2_1 | * The database does not exist
teslamate2_1 | * The "schema_migrations" table, which Ecto uses for managing
teslamate2_1 | migrations, was defined by another library
teslamate2_1 | * There is a deadlock while migrating (such as using concurrent
teslamate2_1 | indexes with a migration_lock)
teslamate2_1 |
teslamate2_1 | To fix the first issue, run "mix ecto.create".
teslamate2_1 |
teslamate2_1 | To address the second, you can run "mix ecto.drop" followed by
teslamate2_1 | "mix ecto.create". Alternatively you may configure Ecto to use
teslamate2_1 | another table and/or repository for managing migrations:
teslamate2_1 |
teslamate2_1 | config :teslamate, TeslaMate.Repo,
teslamate2_1 | migration_source: "some_other_table_for_schema_migrations",
teslamate2_1 | migration_repo: AnotherRepoForSchemaMigrations
teslamate2_1 |
teslamate2_1 | The full error report is shown below.
teslamate2_1 |
teslamate2_1 | ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2953ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
teslamate2_1 |
teslamate2_1 | 1. Tracking down slow queries and making sure they are running fast enough
teslamate2_1 | 2. Increasing the pool_size (albeit it increases resource consumption)
teslamate2_1 | 3. Allowing requests to wait longer by increasing :queue_target and :queue_interval
teslamate2_1 |
teslamate2_1 | See DBConnection.start_link/2 for more information
teslamate2_1 |
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:751: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate2_1 | (elixir 1.11.3) lib/enum.ex:1411: Enum."-map/2-lists^map/1-0-"/2
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:838: Ecto.Adapters.SQL.execute_ddl/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:669: Ecto.Migrator.verbose_schema_migration/3
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:498: Ecto.Migrator.lock_for_migrations/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:413: Ecto.Migrator.run/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:145: Ecto.Migrator.with_repo/3
teslamate2_1 | (teslamate 1.21.3) lib/teslamate/release.ex:9: anonymous fn/2 in TeslaMate.Release.migrate/0
pi_teslamate2_1 exited with code 1
teslamate2_1 | 2021-02-14 08:30:19.347 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:19.347 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:20.626 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:21.389 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:22.233 [error] Could not create schema migrations table. This error usually happens due to the following:
teslamate2_1 |
teslamate2_1 | * The database does not exist
teslamate2_1 | * The "schema_migrations" table, which Ecto uses for managing
teslamate2_1 | migrations, was defined by another library
teslamate2_1 | * There is a deadlock while migrating (such as using concurrent
teslamate2_1 | indexes with a migration_lock)
teslamate2_1 |
teslamate2_1 | To fix the first issue, run "mix ecto.create".
teslamate2_1 |
teslamate2_1 | To address the second, you can run "mix ecto.drop" followed by
teslamate2_1 | "mix ecto.create". Alternatively you may configure Ecto to use
teslamate2_1 | another table and/or repository for managing migrations:
teslamate2_1 |
teslamate2_1 | config :teslamate, TeslaMate.Repo,
teslamate2_1 | migration_source: "some_other_table_for_schema_migrations",
teslamate2_1 | migration_repo: AnotherRepoForSchemaMigrations
teslamate2_1 |
teslamate2_1 | The full error report is shown below.
teslamate2_1 |
teslamate2_1 | ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2911ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
teslamate2_1 |
teslamate2_1 | 1. Tracking down slow queries and making sure they are running fast enough
teslamate2_1 | 2. Increasing the pool_size (albeit it increases resource consumption)
teslamate2_1 | 3. Allowing requests to wait longer by increasing :queue_target and :queue_interval
teslamate2_1 |
teslamate2_1 | See DBConnection.start_link/2 for more information
teslamate2_1 |
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:751: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate2_1 | (elixir 1.11.3) lib/enum.ex:1411: Enum."-map/2-lists^map/1-0-"/2
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:838: Ecto.Adapters.SQL.execute_ddl/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:669: Ecto.Migrator.verbose_schema_migration/3
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:498: Ecto.Migrator.lock_for_migrations/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:413: Ecto.Migrator.run/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:145: Ecto.Migrator.with_repo/3
teslamate2_1 | (teslamate 1.21.3) lib/teslamate/release.ex:9: anonymous fn/2 in TeslaMate.Release.migrate/0
pi_teslamate2_1 exited with code 0
teslamate2_1 | 2021-02-14 08:30:26.197 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:26.198 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:28.445 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:28.866 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate2" does not exist
teslamate2_1 | 2021-02-14 08:30:29.140 [error] Could not create schema migrations table. This error usually happens due to the following:
teslamate2_1 |
teslamate2_1 | * The database does not exist
teslamate2_1 | * The "schema_migrations" table, which Ecto uses for managing
teslamate2_1 | migrations, was defined by another library
teslamate2_1 | * There is a deadlock while migrating (such as using concurrent
teslamate2_1 | indexes with a migration_lock)
teslamate2_1 |
teslamate2_1 | To fix the first issue, run "mix ecto.create".
teslamate2_1 |
teslamate2_1 | To address the second, you can run "mix ecto.drop" followed by
teslamate2_1 | "mix ecto.create". Alternatively you may configure Ecto to use
teslamate2_1 | another table and/or repository for managing migrations:
teslamate2_1 |
teslamate2_1 | config :teslamate, TeslaMate.Repo,
teslamate2_1 | migration_source: "some_other_table_for_schema_migrations",
teslamate2_1 | migration_repo: AnotherRepoForSchemaMigrations
teslamate2_1 |
teslamate2_1 | The full error report is shown below.
teslamate2_1 |
teslamate2_1 | ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2959ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
teslamate2_1 |
teslamate2_1 | 1. Tracking down slow queries and making sure they are running fast enough
teslamate2_1 | 2. Increasing the pool_size (albeit it increases resource consumption)
teslamate2_1 | 3. Allowing requests to wait longer by increasing :queue_target and :queue_interval
teslamate2_1 |
teslamate2_1 | See DBConnection.start_link/2 for more information
teslamate2_1 |
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:751: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate2_1 | (elixir 1.11.3) lib/enum.ex:1411: Enum."-map/2-lists^map/1-0-"/2
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:838: Ecto.Adapters.SQL.execute_ddl/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:669: Ecto.Migrator.verbose_schema_migration/3
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:498: Ecto.Migrator.lock_for_migrations/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:413: Ecto.Migrator.run/4
teslamate2_1 | (ecto_sql 3.5.4) lib/ecto/migrator.ex:145: Ecto.Migrator.with_repo/3
teslamate2_1 | (teslamate 1.21.3) lib/teslamate/release.ex:9: anonymous fn/2 in TeslaMate.Release.migrate/0
pi_teslamate2_1 exited with code 1