Unhealthy / Not Working after Upgrade to 2.2.0
christianreiss opened this issue · 2 comments
christianreiss commented
Problem/Motivation
After upgrading the container, ZWave refuses to start (docker unhealthy).
Expected behavior
Well, container healthy and ZWave online.
Actual behavior
Container unhealthy, ZWave offline.
Steps to reproduce
Upgrade Add-On from 2.1.2 to 2.2.0.
Error Log
[16:31:00] INFO: Starting the Z-Wave JS UI...
2023-10-18 16:31:00.946 INFO APP: Version: 9.2.0
2023-10-18 16:31:00.948 INFO APP: Application path:/opt
______ __ __ _ _____ _ _ _____
|___ / \ \ / / | |/ ____| | | | |_ _|
/ /____\ \ /\ / /_ ___ _____ | | (___ | | | | | |
/ /______\ \/ \/ / _' \ \ / / _ \ _ | |\___ \ | | | | | |
/ /__ \ /\ / (_| |\ V / __/ | |__| |____) | | |__| |_| |_
/_____| \/ \/ \__,_| \_/ \___| \____/|_____/ \____/|_____|
2023-10-18 16:31:00.971 WARN STORE: scenes.json not found
Error: listen EAFNOSUPPORT: address family not supported :::44920
at Server.setupListenHandle [as _listen2] (node:net:1800:21)
at listenInCluster (node:net:1865:12)
at doListen (node:net:2014:7)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
[16:31:01] INFO: Service Z-Wave JS UI exited with code 1 (by signal 0)
github-actions commented
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
christianreiss commented
Its fixed!