-
-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Machine ID generation issue #5022
Comments
It depends on your other devices. Does on of them use machine id? Config? |
Mhhm. Can you track this to a commit? 09eab09? |
The MR changed the way telemetry is initialised. With the new runtime enabling possibility the machine-id is required on startup. I see two possible solutions:
|
Ich würde den PR fürs erste zurück rollen und Neues Release machen? Das ist ja breaking für Viele... |
Ich würd lieber den Fix bauen. Das ist keine große Sache. |
Wir sollten genau eine InstanceId haben, nicht mehrere. Geht der Fix kurzfristig? Sonst würde ich den PR zurück rollen. |
Describe the bug
I don't think machine-id generation issues should prevent evcc startup when there is no enabled telemetry.
I know that this is related to this two:
denisbrodbeck/machineid#5
#3027
Steps to reproduce
Use code base with #5001 that introduced telemetry as opt-in switch during runtime.
Configuration details
not relevant
Log details
Version: 0.105.2 09eab09 2022-11-02_10:17:28
go build -v -tags=release -ldflags='-X github.com/evcc-io/evcc/server.Version=0.105.2 -X github.com/evcc-io/evcc/server.Commit=09eab094 -s -w'
[main ] INFO 2022/11/02 11:17:28 evcc 0.105.2 (09eab09)
[main ] INFO 2022/11/02 11:17:28 using config file: /etc/evcc.yaml
[main ] INFO 2022/11/02 11:17:28 listening at :7070
[main ] FATAL 2022/11/02 11:17:28 could not get machineid: open /etc/machine-id: no such file or directory; for manual configuration use plant: 7c6a33ec487c3c597dd2fa34ee80c6268780f570340a2f98890b9cc66f4a3819
[main ] FATAL 2022/11/02 11:17:28 will attempt restart in: 5m0s
What type of operating system are you running?
Docker container
Version
No response
The text was updated successfully, but these errors were encountered: