Can not get teslamate working

[kerbero81]

Hello, I am trying to set up teslamate for my vehicle. This is the first time I use docker so I am pretty lost... I followed a tutorial, that made me set the following environment:

• VM on Oracle Cloud, wich is working fine.
• Zerotier to set a VPN connection, wich is working fine as well, because I can make ping between both machines.

For the instalation of teslamate

• At first I followed the instructions on https://docs.teslamate.org/docs/installation/docker, wich I could not make work, nor grafana nor teslamate answered on their, my_ip:port.
• Then I followed the advanced installation, wich worked only for grafana, but teslamate keept not working.
  I have googled a lot but I have not been able to find a solution. The only thing that I can say is that, on teslamate logs, I can see an endles list of:

waiting for postgres at database:5432
waiting for postgres at database:5432
waiting for postgres at database:5432 ...

The log file does not have anything else, and keeps being updated every two seconds or so. So I think it is clear that something here is not working fine.

I have entered on the postgress database directly, and it seems its working:
psql -h 172.20X.X -p 5432 -U XXXX

teslamate=# SELECT version();
version

PostgreSQL 14.7 (Debian 14.7-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
(1 row)

Does anybody have an idea how to make it work?

[DrMichael]

Well, teslamate cannot connect to the database at 5432. You need to check that.

[kerbero81]

Hi! Thanks for your answer, as I said, I am absolutely new on docker, so, please, could you tell me how to check it?

Thank you!

[DrMichael]

For a start the docker-compose.yml would be helpful.

[kerbero81]

Hello!
Right now I have copied and pasted the docker-compose.yml from https://docs.teslamate.org/docs/guides/traefik with the .env as advised there. The only points I have in doubt are the FQDN wich I do not have any so I think I could delete them as I have read that they are optional.
Other points I do that I am not sure I am doing rigth are the commands to update the system when I introduce changes on the .yml file: I use sudo docker-compose pull and then: sudo docker-compose up -d --remove-orphans

[DrMichael]

What gives docker-compose ps and docker ps?

[DrMichael]

Hard to read, but all services up...

What with docker-compose logs teslamate and docker-compose logs database?

[kerbero81]

Yes, sorry its better to read it on the ssh display.

sudo docker logs teslamate_teslamate_1, as I said is:

waiting for postgres at database:5432
waiting for postgres at database:5432
waiting for postgres at database:5432
waiting for postgres at database:5432
waiting for postgres at database:5432
waiting for postgres at database:5432

That keep adding one new line every second

For sudo docker logs teslamate_database_1:

PostgreSQL Database directory appears to contain a database; Skipping initialization

2023-04-09 13:29:36.606 UTC [1] LOG: starting PostgreSQL 14.7 (Debian 14.7-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-04-09 13:29:36.606 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-04-09 13:29:36.606 UTC [1] LOG: listening on IPv6 address "::", port 5432
2023-04-09 13:29:36.615 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-04-09 13:29:36.622 UTC [26] LOG: database system was shut down at 2023-04-09 13:29:27 UTC
2023-04-09 13:29:36.643 UTC [1] LOG: database system is ready to accept connections

As I said on my first post, I can access grafana via my-ip:3000 and, once introduced user/pwd, I can see Teslamate data source and, if I try, "Save and test" and get: Database Connection OK

[DrMichael]

Sorry out of ideas. No idea, why grafana can connect to the database and teslamate cannot...

[sedetweiler]

I am having the exact same issue. Grafana can connect but teslamate cannot. It is all running, but postgress is waiting

[kerbero81]

Sorry to read that. I ended up creating a new VM and setting up the new environment from scratch. I do not know what happened but, clearly, had something to do with the environment. I can tell you, logs from the containers are useless for this problem.

[tills13]

Just ran into this myself after changing my network. The way I solved it was to destroy the teslamate docker network

docker network rm teslamate_default

and then restart the app

docker compose up --force-recreate