Skip to content
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.

Sign up for GitHub

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

Jump to bottom

NUT fails to start after upgrade to Home Assistant OS 10.4 #2668

Closed
OriginalResponsibleUser opened this issue Aug 3, 2023 · 17 comments
Closed

NUT fails to start after upgrade to Home Assistant OS 10.4 #2668

OriginalResponsibleUser opened this issue Aug 3, 2023 · 17 comments
Labels
board/generic-x86-64 Generic x86-64 Boards (like Intel NUC) bug

Comments

@OriginalResponsibleUser
Copy link

OriginalResponsibleUser commented Aug 3, 2023 •
edited
Loading

Describe the issue you are experiencing

After upgrading to Home Assistant OS 10.4, the NUT addon no longer starts, seemingly due to a permission issue not allowing the UPS to be detected.
This worked fine in OS 10.3 and earlier.

I opened this issue originally in the NUT-Addons page, but was told to take it here due to being on OS 10.4
hassio-addons/addon-nut#317

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

Home Assistant OS 10.4

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

  1. Running OS 10.3, get the NUT add-on configured properly.
  2. Upgrade to OS 10.4
  3. NUT no longer starts

Anything in the Supervisor logs that might be useful for us?

23-08-03 12:50:04 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:50:04 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:50:12 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:50:12 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:50:12 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:50:19 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:50:19 INFO (SyncWorker_7) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:50:20 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:50:27 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:50:27 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:50:27 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:50:35 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:50:35 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:50:35 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:50:42 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:50:42 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:50:43 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:50:50 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:50:50 INFO (SyncWorker_7) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:50:51 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:50:58 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:50:58 INFO (SyncWorker_6) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:50:58 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:51:06 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:51:06 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:51:06 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:51:13 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:51:13 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:51:14 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:51:29 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Network UPS Tools is failed, restarting...
23-08-03 12:51:29 INFO (SyncWorker_6) [supervisor.docker.manager] Cleaning addon_a0d7b954_nut application
23-08-03 12:51:30 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/amd64 with version 0.12.0
23-08-03 12:51:45 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-42133' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1042> exception=AddonsJobError('Rate limit exceeded, more then 10 calls in 0:30:00')>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 1056, in watchdog_container
    await self._restart_after_problem(self, event.state)
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 144, in wrapper
    raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more then 10 calls in 0:30:00
23-08-03 12:52:13 ERROR (SyncWorker_0) [supervisor.docker.manager] Container addon_a0d7b954_nut is not running

Anything in the Host logs that might be useful for us?

Aug 03 16:51:13 homeassistant systemd[1]: mnt-data-docker-overlay2-3073205dc6573b44643928ed8d49c1903e19e17e5fc85d5e071bd271e148edc6-merged.mount: Deactivated successfully.
Aug 03 16:51:13 homeassistant kernel: audit: type=1334 audit(1691081473.709:1906): prog-id=656 op=UNLOAD
Aug 03 16:51:13 homeassistant systemd[1]: mnt-data-docker-overlay2-15ec526f0980cf5724f2432252db5887b6050106b9671745c41f1dddfd9bd5d5\x2dinit-merged.mount: Deactivated successfully.
Aug 03 16:51:13 homeassistant kernel: hassio: port 11(veth8047d67) entered blocking state
Aug 03 16:51:13 homeassistant kernel: hassio: port 11(veth8047d67) entered disabled state
Aug 03 16:51:13 homeassistant kernel: device veth8047d67 entered promiscuous mode
Aug 03 16:51:13 homeassistant kernel: audit: type=1700 audit(1691081473.886:1907): dev=veth8047d67 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
Aug 03 16:51:13 homeassistant kernel: audit: type=1300 audit(1691081473.886:1907): arch=c000003e syscall=44 success=yes exit=40 a0=c a1=c0018aec00 a2=28 a3=0 items=0 ppid=1 pid=485 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
Aug 03 16:51:13 homeassistant kernel: audit: type=1327 audit(1691081473.886:1907): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
Aug 03 16:51:13 homeassistant kernel: hassio: port 11(veth8047d67) entered blocking state
Aug 03 16:51:13 homeassistant kernel: hassio: port 11(veth8047d67) entered forwarding state
Aug 03 16:51:13 homeassistant NetworkManager[407]: <info>  [1691081473.8902] manager: (veth9bdc849): new Veth device (/org/freedesktop/NetworkManager/Devices/168)
Aug 03 16:51:13 homeassistant NetworkManager[407]: <info>  [1691081473.8913] manager: (veth8047d67): new Veth device (/org/freedesktop/NetworkManager/Devices/169)
Aug 03 16:51:13 homeassistant systemd[1]: Started libcontainer container f3a6e050e216437bf19ac784c6df46c1ca76e4c2ba58bdd61db4c8f2bf732cb1.
Aug 03 16:51:13 homeassistant kernel: audit: type=1334 audit(1691081473.994:1908): prog-id=657 op=LOAD
Aug 03 16:51:13 homeassistant kernel: audit: type=1334 audit(1691081473.995:1909): prog-id=658 op=LOAD
Aug 03 16:51:14 homeassistant kernel: eth0: renamed from veth9bdc849
Aug 03 16:51:14 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8047d67: link becomes ready
Aug 03 16:51:14 homeassistant NetworkManager[407]: <info>  [1691081474.1484] device (veth8047d67): carrier: link connected
Aug 03 16:51:15 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-372e0642063efd8f13ae2dc63943c814904a67c808fcbc608803ec6cbf49e244-runc.PHebyv.mount: Deactivated successfully.
Aug 03 16:51:16 homeassistant kernel: Bluetooth: hci0: command 0x1001 tx timeout
Aug 03 16:51:25 homeassistant kernel: Bluetooth: hci0: RTL: HCI_OP_READ_LOCAL_VERSION failed (-110)
Aug 03 16:51:29 homeassistant systemd[1]: docker-f3a6e050e216437bf19ac784c6df46c1ca76e4c2ba58bdd61db4c8f2bf732cb1.scope: Deactivated successfully.
Aug 03 16:51:29 homeassistant systemd[1]: docker-f3a6e050e216437bf19ac784c6df46c1ca76e4c2ba58bdd61db4c8f2bf732cb1.scope: Consumed 2.483s CPU time.
Aug 03 16:51:29 homeassistant kernel: kauditd_printk_skb: 34 callbacks suppressed
Aug 03 16:51:29 homeassistant kernel: audit: type=1334 audit(1691081489.604:1922): prog-id=657 op=UNLOAD
Aug 03 16:51:29 homeassistant dockerd[485]: time="2023-08-03T16:51:29.616122118Z" level=info msg="ignoring event" container=f3a6e050e216437bf19ac784c6df46c1ca76e4c2ba58bdd61db4c8f2bf732cb1 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Aug 03 16:51:29 homeassistant kernel: hassio: port 11(veth8047d67) entered disabled state
Aug 03 16:51:29 homeassistant kernel: veth9bdc849: renamed from eth0
Aug 03 16:51:29 homeassistant NetworkManager[407]: <info>  [1691081489.6639] manager: (veth9bdc849): new Veth device (/org/freedesktop/NetworkManager/Devices/170)
Aug 03 16:51:29 homeassistant kernel: hassio: port 11(veth8047d67) entered disabled state
Aug 03 16:51:29 homeassistant kernel: device veth8047d67 left promiscuous mode
Aug 03 16:51:29 homeassistant kernel: hassio: port 11(veth8047d67) entered disabled state
Aug 03 16:51:29 homeassistant kernel: audit: type=1700 audit(1691081489.671:1923): dev=veth8047d67 prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
Aug 03 16:51:29 homeassistant kernel: audit: type=1300 audit(1691081489.671:1923): arch=c000003e syscall=44 success=yes exit=32 a0=c a1=c00136d4e0 a2=20 a3=0 items=0 ppid=1 pid=485 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
Aug 03 16:51:29 homeassistant kernel: audit: type=1327 audit(1691081489.671:1923): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
Aug 03 16:51:29 homeassistant systemd[1]: run-docker-netns-e68afe951ffc.mount: Deactivated successfully.
Aug 03 16:51:29 homeassistant systemd[1]: var-lib-docker-overlay2-15ec526f0980cf5724f2432252db5887b6050106b9671745c41f1dddfd9bd5d5-merged.mount: Deactivated successfully.
Aug 03 16:51:29 homeassistant systemd[1]: mnt-data-docker-overlay2-15ec526f0980cf5724f2432252db5887b6050106b9671745c41f1dddfd9bd5d5-merged.mount: Deactivated successfully.
Aug 03 16:51:29 homeassistant kernel: audit: type=1334 audit(1691081489.737:1924): prog-id=660 op=UNLOAD
Aug 03 16:51:30 homeassistant kernel: hassio: port 11(veth3da0f3c) entered blocking state
Aug 03 16:51:30 homeassistant kernel: hassio: port 11(veth3da0f3c) entered disabled state
Aug 03 16:51:30 homeassistant kernel: device veth3da0f3c entered promiscuous mode
Aug 03 16:51:30 homeassistant kernel: audit: type=1700 audit(1691081490.003:1925): dev=veth3da0f3c prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
Aug 03 16:51:30 homeassistant kernel: audit: type=1300 audit(1691081490.003:1925): arch=c000003e syscall=44 success=yes exit=40 a0=c a1=c0014446c0 a2=28 a3=0 items=0 ppid=1 pid=485 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
Aug 03 16:51:30 homeassistant kernel: audit: type=1327 audit(1691081490.003:1925): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
Aug 03 16:51:30 homeassistant kernel: hassio: port 11(veth3da0f3c) entered blocking state
Aug 03 16:51:30 homeassistant kernel: hassio: port 11(veth3da0f3c) entered forwarding state
Aug 03 16:51:30 homeassistant NetworkManager[407]: <info>  [1691081490.0061] manager: (veth769dd1a): new Veth device (/org/freedesktop/NetworkManager/Devices/171)
Aug 03 16:51:30 homeassistant NetworkManager[407]: <info>  [1691081490.0072] manager: (veth3da0f3c): new Veth device (/org/freedesktop/NetworkManager/Devices/172)
Aug 03 16:51:30 homeassistant systemd[1]: Started libcontainer container 249d616efbc3270c11ee4db59271e01b420062e6b45d17b0dc032152fbb911f0.
Aug 03 16:51:30 homeassistant kernel: audit: type=1334 audit(1691081490.127:1926): prog-id=661 op=LOAD
Aug 03 16:51:30 homeassistant kernel: audit: type=1334 audit(1691081490.127:1927): prog-id=662 op=LOAD
Aug 03 16:51:30 homeassistant systemd[1]: Stopped target Bluetooth Support.
Aug 03 16:51:30 homeassistant kernel: eth0: renamed from veth769dd1a
Aug 03 16:51:30 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3da0f3c: link becomes ready
Aug 03 16:51:30 homeassistant NetworkManager[407]: <info>  [1691081490.2809] device (veth3da0f3c): carrier: link connected
Aug 03 16:51:30 homeassistant kernel: usb 3-9.2: reset full-speed USB device number 5 using xhci_hcd
Aug 03 16:51:30 homeassistant systemd[1]: Reached target Bluetooth Support.
Aug 03 16:51:32 homeassistant kernel: Bluetooth: hci0: command 0x1001 tx timeout
Aug 03 16:51:40 homeassistant kernel: Bluetooth: hci0: RTL: HCI_OP_READ_LOCAL_VERSION failed (-110)
Aug 03 16:51:45 homeassistant systemd[1]: docker-249d616efbc3270c11ee4db59271e01b420062e6b45d17b0dc032152fbb911f0.scope: Deactivated successfully.
Aug 03 16:51:45 homeassistant systemd[1]: docker-249d616efbc3270c11ee4db59271e01b420062e6b45d17b0dc032152fbb911f0.scope: Consumed 2.581s CPU time.
Aug 03 16:51:45 homeassistant kernel: kauditd_printk_skb: 34 callbacks suppressed
Aug 03 16:51:45 homeassistant kernel: audit: type=1334 audit(1691081505.029:1940): prog-id=661 op=UNLOAD
Aug 03 16:51:45 homeassistant dockerd[485]: time="2023-08-03T16:51:45.041131314Z" level=info msg="ignoring event" container=249d616efbc3270c11ee4db59271e01b420062e6b45d17b0dc032152fbb911f0 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Aug 03 16:51:45 homeassistant kernel: hassio: port 11(veth3da0f3c) entered disabled state
Aug 03 16:51:45 homeassistant kernel: veth769dd1a: renamed from eth0
Aug 03 16:51:45 homeassistant NetworkManager[407]: <info>  [1691081505.0831] manager: (veth769dd1a): new Veth device (/org/freedesktop/NetworkManager/Devices/173)
Aug 03 16:51:45 homeassistant kernel: hassio: port 11(veth3da0f3c) entered disabled state
Aug 03 16:51:45 homeassistant kernel: device veth3da0f3c left promiscuous mode
Aug 03 16:51:45 homeassistant kernel: hassio: port 11(veth3da0f3c) entered disabled state
Aug 03 16:51:45 homeassistant kernel: audit: type=1700 audit(1691081505.095:1941): dev=veth3da0f3c prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
Aug 03 16:51:45 homeassistant kernel: audit: type=1300 audit(1691081505.095:1941): arch=c000003e syscall=44 success=yes exit=32 a0=c a1=c000cc37c0 a2=20 a3=0 items=0 ppid=1 pid=485 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
Aug 03 16:51:45 homeassistant kernel: audit: type=1327 audit(1691081505.095:1941): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
Aug 03 16:51:45 homeassistant systemd[1]: run-docker-netns-75cf52d87002.mount: Deactivated successfully.
Aug 03 16:51:45 homeassistant systemd[1]: var-lib-docker-overlay2-c58302ad5f7a01172ceedf9649b68a856d96f4f449b462bb8def7050b69e2049-merged.mount: Deactivated successfully.
Aug 03 16:51:45 homeassistant systemd[1]: mnt-data-docker-overlay2-c58302ad5f7a01172ceedf9649b68a856d96f4f449b462bb8def7050b69e2049-merged.mount: Deactivated successfully.
Aug 03 16:51:45 homeassistant kernel: audit: type=1334 audit(1691081505.166:1942): prog-id=664 op=UNLOAD
Aug 03 16:52:51 homeassistant kernel: audit: type=1334 audit(1691081571.000:1943): prog-id=665 op=LOAD
Aug 03 16:52:51 homeassistant systemd-timesyncd[477]: Network configuration changed, trying to establish connection.
Aug 03 16:52:51 homeassistant systemd-timesyncd[477]: Contacted time server [2606:4700:f1::1]:123 (time.cloudflare.com).
Aug 03 16:52:51 homeassistant systemd[1]: Started Journal Gateway Service.
Aug 03 16:52:51 homeassistant systemd-journal-gatewayd[1447015]: microhttpd: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.
Aug 03 16:53:01 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-aa1c85e88c6741d02f45283202bc070624c922c0aa3a3692d9a55d9d19ec9579-runc.90Iff8.mount: Deactivated successfully.
Aug 03 16:53:01 homeassistant kernel: Bluetooth: hci0: command 0x1001 tx timeout
Aug 03 16:53:09 homeassistant kernel: Bluetooth: hci0: RTL: HCI_OP_READ_LOCAL_VERSION failed (-110)
Aug 03 16:53:14 homeassistant systemd[1]: Stopped target Bluetooth Support.
Aug 03 16:53:14 homeassistant kernel: usb 3-9.2: reset full-speed USB device number 5 using xhci_hcd
Aug 03 16:53:14 homeassistant systemd[1]: Reached target Bluetooth Support.
Aug 03 16:53:16 homeassistant kernel: Bluetooth: hci0: command 0x1001 tx timeout
Aug 03 16:53:22 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-87b557524eff83f2f4483bd0fb6f53e1a8b833d1d2bd599c74fa791df0db4464-runc.I6NYMD.mount: Deactivated successfully.
Aug 03 16:53:25 homeassistant kernel: Bluetooth: hci0: RTL: HCI_OP_READ_LOCAL_VERSION failed (-110)
Aug 03 16:54:45 homeassistant kernel: Bluetooth: hci0: command 0x1001 tx timeout
Aug 03 16:54:53 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-87b557524eff83f2f4483bd0fb6f53e1a8b833d1d2bd599c74fa791df0db4464-runc.1FgUVu.mount: Deactivated successfully.
Aug 03 16:54:54 homeassistant kernel: Bluetooth: hci0: RTL: HCI_OP_READ_LOCAL_VERSION failed (-110)
Aug 03 16:54:59 homeassistant systemd[1]: Stopped target Bluetooth Support.
Aug 03 16:54:59 homeassistant kernel: usb 3-9.2: reset full-speed USB device number 5 using xhci_hcd
Aug 03 16:54:59 homeassistant systemd[1]: Reached target Bluetooth Support.
Aug 03 16:55:01 homeassistant kernel: Bluetooth: hci0: command 0x1001 tx timeout
Aug 03 16:55:09 homeassistant kernel: Bluetooth: hci0: RTL: HCI_OP_READ_LOCAL_VERSION failed (-110)

System information

System Information

version core-2023.8.0
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.11.4
os_name Linux
os_version 6.1.39
arch x86_64
timezone America/New_York
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 5000
Installed Version 1.32.1
Stage running
Available Repositories 1267
Downloaded Repositories 8
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 10.4
update_channel beta
supervisor_version supervisor-2023.08.0
agent_version 1.5.1
docker_version 23.0.6
disk_total 116.7 GB
disk_used 14.3 GB
healthy true
supported true
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons Z-Wave JS (0.1.85), Mosquitto broker (6.2.1), Ring-MQTT with Video Streaming (5.5.1), File editor (5.6.0), Advanced SSH & Web Terminal (15.0.6), Matter Server (4.9.0), Silicon Labs Flasher (0.1.1), Silicon Labs Multiprotocol (2.3.0), Network UPS Tools (0.12.0), Studio Code Server (5.10.0), Z-Wave JS UI (1.15.3), Let's Encrypt (4.12.9), OpenThread Border Router (2.3.0)
Dashboards
dashboards 1
resources 5
views 1
mode storage
Recorder
oldest_recorder_run July 27, 2023 at 12:14 AM
current_recorder_run August 2, 2023 at 8:04 PM
estimated_db_size 64.04 MiB
database_engine sqlite
database_version 3.41.2

Additional information

NUT Addon Configuration file

users:
  - username: ****
    password: *********
    instcmds:
      - all
    actions: []
devices:
  - name: BackUPS1500
    driver: usbhid-ups
    port: auto
    config:
      - vendorid = 051d*
      - productid = 0002*
      - serial = abcd*
  - name: BackUPS550
    driver: usbhid-ups
    port: auto
    config:
      - vendorid = 051d*
      - productid = 0002*
      - serial = abcd*
mode: netserver
shutdown_host: false
log_level: debug

NUT Addon Startup Logs

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 0.12.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.4  (amd64 / generic-x86-64)
 Home Assistant Core: 2023.8.0
 Home Assistant Supervisor: 2023.08.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[12:50:13] INFO: Configuring timezone (America/New_York)...
Log level is set to DEBUG
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nut.sh
[12:50:13] INFO: Setting mode to netserver...
[12:50:13] INFO: Generating /etc/nut/upsd.users...
[12:50:14] INFO: Configuring user: hass
[12:50:14] DEBUG: Password SHA1: 6BBD6EA473D3064CEAAB6385EDFE0E943E7D6065
[12:50:14] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/6BBD6
[12:50:14] DEBUG: API HTTP Response code: 200
[12:50:14] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[12:50:14] INFO: Configuring Device named BackUPS1500...
[12:50:14] INFO: Configuring Device named BackUPS550...
[12:50:14] INFO: Starting the UPS drivers...
   0.000000	[D1] Starting UPS: BackUPS1500
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Using subdriver: APC HID 0.98
   0.251379	[D1] Starting UPS: BackUPS550
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching HID UPS found
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
   0.476758	Driver failed to start (exit status=1)
Network UPS Tools - UPS driver controller 2.8.0
cont-init: info: /etc/cont-init.d/nut.sh exited 1
cont-init: info: running /etc/cont-init.d/nutclient.sh
cont-init: info: /etc/cont-init.d/nutclient.sh exited 0
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-timezone: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-timezone successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
@Jan022

This comment was marked as off-topic.

Sign in to view
@agners agners added the board/generic-x86-64 Generic x86-64 Boards (like Intel NUC) label Aug 4, 2023
@agners
Copy link
Member

agners commented Aug 4, 2023

Hm, my best guess is that this is related to #2623 🤔

Can you double check with 10.3 to confirm that this is indeed 10.4 related? You can downgrade the OS safely using ha os update --version 10.3.

@OriginalResponsibleUser
Copy link
Author

This can be closed. I did a bit more troubleshooting and the issue was not related to HAOS nor the NUT Add-on/integration.

@edwardtfn
Copy link

Could you please share what was the issue? I'm facing the exactly same error message when trying to setup this for the first time.

@Xitee1
Copy link

Xitee1 commented Aug 18, 2023

I'm also having the same problem. Trying to connect my first UPS.

@uros76
Copy link

uros76 commented Sep 10, 2023

This can be closed. I did a bit more troubleshooting and the issue was not related to HAOS nor the NUT Add-on/integration.

What was it? I have exactly same problem same as few above...

@Xitee1
Copy link

Xitee1 commented Sep 10, 2023

In my case I've got it working by rebooting my HA host system and UPS.

@francescopeloi
Copy link

francescopeloi commented Oct 6, 2023 •
edited
Loading

what was the issue at the end? @OriginalResponsibleUser

Rebooting didn't help.

@pilot51
Copy link

pilot51 commented Oct 19, 2023

I'm using the Docker container in Debian 12 rather than HA OS, but I just ran into this same issue after rebooting for a kernel update and my solution may be helpful. I'm here because this was the first result when I Googled the "insufficient permissions on everything" error.

Compare the output of nut-scanner -U with the configuration in /etc/nut/ups.conf and modify as necessary.
In my case, bus had changed from 001 to 003.
The nut-driver service picked up the updated config right away, though apparently I had to reload the HA configuration for it to see the UPS again (or I didn't wait long enough).

@BigWebstas
Copy link

Same issue here might be related to the recent HASSOS update

Network UPS Tools
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------

 Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 0.13.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.4  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.1.2
 Home Assistant Supervisor: 2023.12.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[14:45:30] INFO: Configuring timezone (America/Denver)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nut.sh
[14:45:33] INFO: Setting mode to netserver...
[14:45:33] INFO: Generating /etc/nut/upsd.users...
[14:45:34] INFO: Configuring user: webstas
[14:45:34] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[14:45:36] INFO: Configuring Device named myups...
[14:45:37] INFO: Starting the UPS drivers...
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching HID UPS found
Network UPS Tools - UPS driver controller 2.8.0
Driver failed to start (exit status=1)

@XSplinter
Copy link

Yes I confirm that's the solution.... shutdown the host.

It's not reboot HA, you do this: Go to settings, system, power button on the top right, advance option, shutdown server.
Once you turn it on everything is working again

@zavorra
Copy link

zavorra commented Feb 19, 2024

Same problem here. Shutdown didn't help, other here reported that shutdown the raspberry is not (always) the solution

please re-open this

@john8329
Copy link

john8329 commented Mar 18, 2024 •
edited
Loading

Same, I'm still researching the issue, but neither reboot nor shutdown helped. I can't even see why that should help. Also see hassio-addons/addon-nut#322

Edit: using the nutdrv_qx instead of the hid driver fixed it for me.

@sarroutbi
Copy link

Same, I'm still researching the issue, but neither reboot nor shutdown helped. I can't even see why that should help. Also see hassio-addons/addon-nut#322

Edit: using the nutdrv_qx instead of the hid driver fixed it for me.

Hello @john8329 . Could you please elaborate how to change it to use nutdrv_qx?

Thanks

@john8329
Copy link

Same, I'm still researching the issue, but neither reboot nor shutdown helped. I can't even see why that should help. Also see hassio-addons/addon-nut#322
Edit: using the nutdrv_qx instead of the hid driver fixed it for me.

Hello @john8329 . Could you please elaborate how to change it to use nutdrv_qx?

Thanks

Sure, I even found the right driver that works permanently for my UPS (before it was disconnecting after a while). You have to set it up like
this under settings > add-ons > NUT > Configuration:
Screenshot 2024-05-10 at 15 10 40

The driver name and configuration can be created depending on the device, you can find more here.

Cheers

@sarroutbi
Copy link

Same, I'm still researching the issue, but neither reboot nor shutdown helped. I can't even see why that should help. Also see hassio-addons/addon-nut#322
Edit: using the nutdrv_qx instead of the hid driver fixed it for me.

Hello @john8329 . Could you please elaborate how to change it to use nutdrv_qx?
Thanks

Sure, I even found the right driver that works permanently for my UPS (before it was disconnecting after a while). You have to set it up like this under settings > add-ons > NUT > Configuration: Screenshot 2024-05-10 at 15 10 40

The driver name and configuration can be created depending on the device, you can find more here.

Cheers

Thank you so much. I will git it a try.

@finix77
Copy link

finix77 commented Sep 21, 2024

Same problem here:
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching HID UPS found
Network UPS Tools - UPS driver controller 2.8.0
Driver failed to start (exit status=1)

Home Assistant OS 13.1
Supervisor 2024.09.1

I use the following configuration for APC smart UPS 1500i usb connected:

name: apcsmart
driver: usbhid-ups
port: auto
config:
vendorid = 051d*
productid = 0002*
serial = AS0614322014
Last year this configuration was working. I don’t know exactly when it stopped to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
board/generic-x86-64 Generic x86-64 Boards (like Intel NUC) bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests