This repository has been archived by the owner on Jul 1, 2024. It is now read-only.
Help with error #23
Unanswered
zephyrus9MA
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Installed Teslamate, Mosquito broker, PostgreSQL. Corresponding config files:
database_user: t-mate_user
database_pass: PASS
database_name: t-mate
database_host: 29b65938-postgres
database_ssl: false
database_port: 5432
disable_mqtt: false
grafana_import_dashboards: false
grafana_folder_name: TeslaMate
grafana_host: a0d7b954-grafana
grafana_port: 3000
grafana_user: admin
grafana_pass: t-mate
import_dir: /share/teslamate
mqtt_host: core-mosquitto
mqtt_user: mozzie
mqtt_pass: PASS-M
mqtt_tls: true
mqtt_tls_accept_invalid_certs: false
mqtt_namespace: ''
timezone: usa
certfile: fullchain.pem
customize:
active: false
folder: mosquitto
keyfile: privkey.pem
logins: []
require_certificate: false
disable_mqtt: false
mqtt_host: core-mosquitto
mqtt_user: mozzie
mqtt_pass: PASS-M
mqtt_tls: false
mqtt_tls_accept_invalid_certs: true
user: t-mate_user
password: PASS
database: t-mate
Log shows
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2022-02-23 00:58:39.061 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "t-mate_user"
2022-02-23 00:58:39.061 [error] Postgrex.Protocol (#PID<0.165.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "t-mate_user"
2022-02-23 00:58:41.632 [error] Postgrex.Protocol (#PID<0.166.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "t-mate_user"
2022-02-23 00:58:41.975 [error] Could not create schema migrations table. This error usually happens due to the following:
migrations, was defined by another library
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:
..........................
...........................
What is ecto? How do I fix this?
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions