After updateing, teslamate doesn't work as supposed

[d1stru3t0r]

Report issues at https://termux.dev/issues
~ $ su
xport PATH=/data/adb/docker/bin:$PATH <
OST=unix:///data/adb/docker/run/docker.sock <
ocker compose ps <
no configuration file provided: not found
ocker ps <
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b40e6c62b95d teslamate/grafana:latest "/run.sh" 46 hours ago Up 14 hours 0.0.0.0:3000->3000/tcp, [::]:3000->3000/tcp teslamate-grafana-1
209d7c22e997 eclipse-mosquitto:2 "/docker-entrypoint.…" 46 hours ago Up 14 hours 1883/tcp teslamate-mosquitto-1
29e08f2dc658 teslamate/teslamate:latest "tini -- /bin/dash /…" 46 hours ago Up 14 hours 0.0.0.0:4000->4000/tcp, [::]:4000->4000/tcp teslamate-teslamate-1
196cbb4adba5 postgres:18-trixie "docker-entrypoint.s…" 46 hours ago Up 14 hours 5432/tcp teslamate-database-1
:/data/data/com.termux/files/home #

First, 3000 was kinda working but nothing inside 4000 worked, they all had no data, even if i had the database. Then, after hours of debugging, i got the database up again, but now 3000 doesn't show live status, it shows an old one.

I've read about doing backup, delete everything and restart from the beginning, but now i feel that I'd screw even that up. So how to fix this, or what would the best way to backup, (i can delete all) and actually start over again, but with my old database? I wouldn't lose 2 months of nice analytics

[JakobLichterfeld]

Thanks for reporting.

Please open an issue if you feel like you using a supported installation method, you checked your logs and are stillcertain an issue is present.

[d1stru3t0r]

But I got absolutely no response or help about how to fix it or what's the best way to backup / clean restore?

[JakobLichterfeld]

We can't read a crystal ball. As requested here #5259 (comment) and in this discussion above, we need a description what is not correct, which installation method you used, what the logs say etc. That's why the issue template guides you. From what you posted I can see you are not using a supported method as termux is an emulator on android for example which is not suitable for TeslaMate.

Only way to backup: https://docs.teslamate.org/docs/maintenance/backup

[brianmay]

I wouldn't do the backup/restore unless there is a good reason for doing so (e.g. you need to update your database or your database is broken or something). It isn't a magical solution that will fix all problems.

We need to see your logs though in order to provide any assistance.

If it is true that your are using Termux/Android, it is very possible that Teslamate is working perfectly, but Termux/Android is not exposing the ports correctly. Not sure how Termux works - I haven't used it, but I think it is very possible it creates a VM of some sort.

[d1stru3t0r]

I truly understand, and I know how frustrating it is when simple users can't follow basic guidelines (I'm a dev myself), but I wasted so much time on this that I don't even know what's up.

What kind of logs you need? Tell me what to check and I will send it with pleasure!

The thing is, it was working fine on 4.0.1, but while I upgraded to 4.1, it failed, redid, then 4.1.1 appeared, got another error, and then just debug after debug, till... now nothing. Database works, but till the update point.

[brianmay]

The logs from the teslamate docker container.

The failure from 4.1 was probably expected. That is why we released 4.1.1, to fix that.

Also you said you got an error after upgrading to 4.1.1. What did the error say?

[d1stru3t0r]

Oh, first itt was storage error, that was my fault. Afterwards, no idea. As of now, no obvious errors, just port, 400 error(s), will check tomorrow

[d1stru3t0r]

docker-compose (1).yml
Hello, so quick update, after so much troubleshooting, I remembered I did a custom docker compose long that ago, when it worked, then when I synced the 4.1, I used the stock docker-compose, which didn't gave network connection to my dockerd contained, or whatever was the fault. Maybe this will help others too.