Also getting: FATAL: database "teslamate" does not exist

[christiantschoerner]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Same as #2129. When I try to install TeslaMate and type "sudo docker-compose up" I am flooded with errors.

Expected Behavior

No response

Steps To Reproduce

RPI4, Install Docker and Docker-Compose, load docker-compose.yml and pull the container up

Relevant log output

sudo docker-compose up
Pulling teslamate (teslamate/teslamate:latest)...
latest: Pulling from teslamate/teslamate
c0b5ba470cac: Pull complete
e7a6bf53a571: Pull complete
33c7cb17c32e: Pull complete
a9fccfb62c75: Pull complete
ea050ff0879a: Pull complete
8e6d161fcc99: Pull complete
Digest: sha256:541d9b6dd637fa40dcc68064839cd047e49d7abea69592f45816bb0ac4559a08
Status: Downloaded newer image for teslamate/teslamate:latest
Pulling database (postgres:13)...
13: Pulling from library/postgres
b6e5ca4da968: Pull complete
3ef876aa8c0a: Pull complete
d74a37ede70c: Pull complete
ae26ca21bba2: Pull complete
b022af5735d1: Pull complete
51b8341697d7: Pull complete
0f8cc2c0eedf: Pull complete
01d70f71d0a7: Pull complete
5941681c9d5d: Pull complete
8e61c34c782b: Pull complete
3562d3774c74: Pull complete
67969c9975bd: Pull complete
0d60a1fe25a9: Pull complete
Digest: sha256:5e1c13326d5444a8a178ae42c10ce912f6ce6426cf231a8ca2624b9d3ebe76aa
Status: Downloaded newer image for postgres:13
Pulling grafana (teslamate/grafana:latest)...
latest: Pulling from teslamate/grafana
48fad15491f9: Pull complete
9f56dfe459bc: Pull complete
b747d3c5effa: Pull complete
2fe86ffd4cc1: Pull complete
2008c2bc8773: Pull complete
35e40a873add: Pull complete
ec8c732485fb: Pull complete
e7067b57ed02: Pull complete
0acd5a319d3d: Pull complete
41b72d4519ad: Pull complete
423c8c07eb31: Pull complete
4179036a510e: Pull complete
dd2b2d92fd0e: Pull complete
ca6d7861b831: Pull complete
43e5c8bba6bd: Pull complete
4f982efd1c41: Pull complete
Digest: sha256:4b792dbaa10d5a52a040b0e2643369c7582d6952ced2a9b2f15466ef8ea408cb
Status: Downloaded newer image for teslamate/grafana:latest
Pulling mosquitto (eclipse-mosquitto:2)...
2: Pulling from library/eclipse-mosquitto
56afcfda5d78: Pull complete
7cc5dfa21678: Pull complete
193ff21ebef8: Pull complete
Digest: sha256:64b7c1729f7d1fff46b5e884fc389071686b2f7ed116c3fc7e17cbcb50fa147e
Status: Downloaded newer image for eclipse-mosquitto:2
Creating teslamate_database_1  ... done
Creating teslamate_teslamate_1 ... done
Creating teslamate_mosquitto_1 ... done
Creating teslamate_grafana_1   ... done
Attaching to teslamate_teslamate_1, teslamate_mosquitto_1, teslamate_grafana_1, teslamate_database_1
mosquitto_1  | 0: mosquitto version 2.0.14 starting
mosquitto_1  | 0: Config loaded from /mosquitto-no-auth.conf.
mosquitto_1  | 0: Opening ipv4 listen socket on port 1883.
mosquitto_1  | 0: Opening ipv6 listen socket on port 1883.
mosquitto_1  | 0: Warning: Address family not supported by protocol
mosquitto_1  | 0: mosquitto version 2.0.14 running
teslamate_1  | waiting for postgres at database:5432
database_1   |
database_1   | PostgreSQL Database directory appears to contain a database; Skipping initialization
database_1   |
teslamate_1  | waiting for postgres at database:5432
database_1   | 1970-01-01 00:00:00.000 UTC [1] LOG:  starting PostgreSQL 13.5 (Debian 13.5-1.pgdg110+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 32-bit
database_1   | 1970-01-01 00:00:00.000 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
database_1   | 1970-01-01 00:00:00.000 UTC [1] LOG:  could not create IPv6 socket for address "::": Address family not supported by protocol
database_1   | 1970-01-01 00:00:00.000 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 1970-01-01 00:00:00.000 UTC [25] LOG:  database system was shut down at 1970-04-26 05:44:08 UTC
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Starting Grafana" logger=server version=7.5.11 commit=6f8c1d9fe4 branch=HEAD compiled=2021-10-05T11:14:33+0000
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana-plugins"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.provisioning=/etc/grafana/provisioning"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.log.mode=console"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_DATA=/var/lib/grafana"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_LOGS=/var/log/grafana"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PLUGINS=/var/lib/grafana-plugins"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PROVISIONING=/etc/grafana/provisioning"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_ANALYTICS_REPORTING_ENABLED=FALSE"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_USER=admin"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_PASSWORD=*********"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_DISABLE_GRAVATAR=true"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ALLOW_EMBEDDING=true"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_USERS_ALLOW_SIGN_UP=false"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_ANONYMOUS_ENABLED=true"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_BASIC_ENABLED=false"
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana-plugins
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="App mode production" logger=settings
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Connecting to DB" logger=sqlstore dbtype=sqlite3
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Starting DB migrations" logger=migrator
database_1   | 1970-01-01 00:00:00.000 UTC [1] LOG:  database system is ready to accept connections
database_1   | 1970-01-01 00:00:00.000 UTC [29] LOG:  stats collector's time 1970-04-26 08:22:17.966104+00 is later than backend local time 1970-01-01 00:00:00+00
database_1   | 1970-01-01 00:00:00.000 UTC [29] LOG:  stats collector's time 1970-04-26 08:22:17.966104+00 is later than backend local time 1970-01-01 00:00:00+00
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="migrations completed" logger=migrator performed=0 skipped=279 duration=3.848085ms
grafana_1    | t=2021-11-18T10:59:39+0000 lvl=info msg="Starting plugin search" logger=plugins
grafana_1    | t=2021-11-18T10:59:40+0000 lvl=info msg="Registering plugin" logger=plugins id=input
grafana_1    | t=2021-11-18T10:59:41+0000 lvl=info msg="Registering plugin" logger=plugins id=grafana-map-panel
grafana_1    | t=2021-11-18T10:59:41+0000 lvl=info msg="Registering plugin" logger=plugins id=natel-discrete-panel
grafana_1    | t=2021-11-18T10:59:41+0000 lvl=info msg="Registering plugin" logger=plugins id=pr0ps-trackmap-panel
grafana_1    | t=2021-11-18T10:59:41+0000 lvl=info msg="Registering plugin" logger=plugins id=grafana-piechart-panel
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169141Z","queryType":"exponential_heatmap_bucket_data"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169255Z","queryType":"linear_heatmap_bucket_data"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169335Z","queryType":"random_walk"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169374Z","queryType":"predictable_pulse"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169440Z","queryType":"predictable_csv_wave"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169475Z","queryType":"random_walk_table"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169509Z","queryType":"slow_query"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169551Z","queryType":"no_data_points"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.169639Z","queryType":"datapoints_outside_range"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.170062Z","queryType":"manual_entry"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.170136Z","queryType":"csv_metric_values"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.170218Z","queryType":"streaming_client"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.170346Z","queryType":"live"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.170743Z","queryType":"grafana_api"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.170828Z","queryType":"arrow"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.171049Z","queryType":"annotations"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.171112Z","queryType":"table_static"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.171158Z","queryType":"random_walk_with_error"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.171212Z","queryType":"server_error_500"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.171244Z","queryType":"logs"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type handler","@timestamp":"2021-11-18T10:59:41.171302Z","queryType":"node_graph"}
grafana_1    | {"@level":"debug","@message":"datasource: registering query type fallback handler","@timestamp":"2021-11-18T10:59:41.171341Z"}
grafana_1    | t=2021-11-18T10:59:41+0000 lvl=info msg="HTTP Server Listen" logger=http.server address=0.0.0.0:3000 protocol=http subUrl= socket=
database_1   | 1970-01-01 00:00:00.000 UTC [34] FATAL:  database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [33] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:42.673 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:42.673 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [35] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:45.251 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [36] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:45.599 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:45.615 [error] Could not create schema migrations table. This error usually happens due to the following:
teslamate_1  |
teslamate_1  |   * The database does not exist
teslamate_1  |   * The "schema_migrations" table, which Ecto uses for managing
teslamate_1  |     migrations, was defined by another library
teslamate_1  |   * There is a deadlock while migrating (such as using concurrent
teslamate_1  |     indexes with a migration_lock)
teslamate_1  |
teslamate_1  | To fix the first issue, run "mix ecto.create".
teslamate_1  |
teslamate_1  | To address the second, you can run "mix ecto.drop" followed by
teslamate_1  | "mix ecto.create". Alternatively you may configure Ecto to use
teslamate_1  | another table and/or repository for managing migrations:
teslamate_1  |
teslamate_1  |     config :teslamate, TeslaMate.Repo,
teslamate_1  |       migration_source: "some_other_table_for_schema_migrations",
teslamate_1  |       migration_repo: AnotherRepoForSchemaMigrations
teslamate_1  |
teslamate_1  | The full error report is shown below.
teslamate_1  |
teslamate_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:
teslamate_1  |
teslamate_1  |   1. Ensuring your database is available and that you can connect to it
teslamate_1  |   2. Tracking down slow queries and making sure they are running fast enough
teslamate_1  |   3. Increasing the pool_size (although this increases resource consumption)
teslamate_1  |   4. Allowing requests to wait longer by increasing :queue_target and :queue_interval
teslamate_1  |
teslamate_1  | See DBConnection.start_link/2 for more information
teslamate_1  |
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/adapters/sql.ex:760: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate_1  |     (elixir 1.12.3) lib/enum.ex:1582: Enum."-map/2-lists^map/1-0-"/2
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/adapters/sql.ex:852: Ecto.Adapters.SQL.execute_ddl/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:678: Ecto.Migrator.verbose_schema_migration/3
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:504: Ecto.Migrator.lock_for_migrations/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:419: Ecto.Migrator.run/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:146: Ecto.Migrator.with_repo/3
teslamate_1  |     (teslamate 1.25.0) lib/teslamate/release.ex:9: anonymous fn/2 in TeslaMate.Release.migrate/0
database_1   | 1970-01-01 00:00:00.000 UTC [38] FATAL:  database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [39] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:49.565 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:49.565 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [40] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:51.913 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [41] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:52.152 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:52.506 [error] Could not create schema migrations table. This error usually happens due to the following:
teslamate_1  |
teslamate_1  |   * The database does not exist
teslamate_1  |   * The "schema_migrations" table, which Ecto uses for managing
teslamate_1  |     migrations, was defined by another library
teslamate_1  |   * There is a deadlock while migrating (such as using concurrent
teslamate_1  |     indexes with a migration_lock)
teslamate_1  |
teslamate_1  | To fix the first issue, run "mix ecto.create".
teslamate_1  |
teslamate_1  | To address the second, you can run "mix ecto.drop" followed by
teslamate_1  | "mix ecto.create". Alternatively you may configure Ecto to use
teslamate_1  | another table and/or repository for managing migrations:
teslamate_1  |
teslamate_1  |     config :teslamate, TeslaMate.Repo,
teslamate_1  |       migration_source: "some_other_table_for_schema_migrations",
teslamate_1  |       migration_repo: AnotherRepoForSchemaMigrations
teslamate_1  |
teslamate_1  | The full error report is shown below.
teslamate_1  |
teslamate_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:
teslamate_1  |
teslamate_1  |   1. Ensuring your database is available and that you can connect to it
teslamate_1  |   2. Tracking down slow queries and making sure they are running fast enough
teslamate_1  |   3. Increasing the pool_size (although this increases resource consumption)
teslamate_1  |   4. Allowing requests to wait longer by increasing :queue_target and :queue_interval
teslamate_1  |
teslamate_1  | See DBConnection.start_link/2 for more information
teslamate_1  |
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/adapters/sql.ex:760: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate_1  |     (elixir 1.12.3) lib/enum.ex:1582: Enum."-map/2-lists^map/1-0-"/2
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/adapters/sql.ex:852: Ecto.Adapters.SQL.execute_ddl/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:678: Ecto.Migrator.verbose_schema_migration/3
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:504: Ecto.Migrator.lock_for_migrations/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:419: Ecto.Migrator.run/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:146: Ecto.Migrator.with_repo/3
teslamate_1  |     (teslamate 1.25.0) lib/teslamate/release.ex:9: anonymous fn/2 in TeslaMate.Release.migrate/0
teslamate_teslamate_1 exited with code 0
database_1   | 1970-01-01 00:00:00.000 UTC [43] FATAL:  database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [44] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:56.358 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:56.358 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [45] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:57.417 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
database_1   | 1970-01-01 00:00:00.000 UTC [46] FATAL:  database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:57.725 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "teslamate" does not exist
teslamate_1  | 2021-11-18 10:59:59.307 [error] Could not create schema migrations table. This error usually happens due to the following:
teslamate_1  |
teslamate_1  |   * The database does not exist
teslamate_1  |   * The "schema_migrations" table, which Ecto uses for managing
teslamate_1  |     migrations, was defined by another library
teslamate_1  |   * There is a deadlock while migrating (such as using concurrent
teslamate_1  |     indexes with a migration_lock)
teslamate_1  |
teslamate_1  | To fix the first issue, run "mix ecto.create".
teslamate_1  |
teslamate_1  | To address the second, you can run "mix ecto.drop" followed by
teslamate_1  | "mix ecto.create". Alternatively you may configure Ecto to use
teslamate_1  | another table and/or repository for managing migrations:
teslamate_1  |
teslamate_1  |     config :teslamate, TeslaMate.Repo,
teslamate_1  |       migration_source: "some_other_table_for_schema_migrations",
teslamate_1  |       migration_repo: AnotherRepoForSchemaMigrations
teslamate_1  |
teslamate_1  | The full error report is shown below.
teslamate_1  |
teslamate_1  | ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2960ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
teslamate_1  |
teslamate_1  |   1. Ensuring your database is available and that you can connect to it
teslamate_1  |   2. Tracking down slow queries and making sure they are running fast enough
teslamate_1  |   3. Increasing the pool_size (although this increases resource consumption)
teslamate_1  |   4. Allowing requests to wait longer by increasing :queue_target and :queue_interval
teslamate_1  |
teslamate_1  | See DBConnection.start_link/2 for more information
teslamate_1  |
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/adapters/sql.ex:760: Ecto.Adapters.SQL.raise_sql_call_error/1
teslamate_1  |     (elixir 1.12.3) lib/enum.ex:1582: Enum."-map/2-lists^map/1-0-"/2
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/adapters/sql.ex:852: Ecto.Adapters.SQL.execute_ddl/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:678: Ecto.Migrator.verbose_schema_migration/3
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:504: Ecto.Migrator.lock_for_migrations/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:419: Ecto.Migrator.run/4
teslamate_1  |     (ecto_sql 3.7.1) lib/ecto/migrator.ex:146: Ecto.Migrator.with_repo/3
teslamate_1  |     (teslamate 1.25.0) lib/teslamate/release.ex:9: anonymous fn/2 in TeslaMate.Release.migrate/0
teslamate_teslamate_1 exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
Stopping teslamate_grafana_1   ... done
Stopping teslamate_database_1  ... done
Stopping teslamate_mosquitto_1 ... done
Stopping teslamate_teslamate_1 ... done

Screenshots

Additional data

Type of installation

Docker

Version

Latest

[Dresch360]

Hey guys - think I figured it out and hope this helps, as it worked for me. Not sure why we were all pushed to this issues black hole, but here it is:

In the docker-compose.yml file, add "- DATABASE_POOL_SIZE=10" under the list of teslamate environment variables.
services:
teslamate:
image: teslamate/teslamate:latest
restart: always
environment:

• DATABASE_POOL_SIZE=10

then run the following at the command prompt: docker-compose down -v && docker-compose up

[ThxUuu]

That is helpful,Thanks