ha-unraid: Error in HA log: "Command failed: open failed" occurs during network operations

Describe the bug In HA logs I see strange error without details:

Logger: custom_components.unraid.unraid
Zdroj: custom_components/unraid/unraid.py:87
integrace: UNRAID (dokumentace, problémy)
První výskyt: 23:13:38 (26 výskyty)
Naposledy logováno: 23:24:41

Command failed: open failed

When I look into debug log, there are no more details in that error, but probably can help whole block debug logs for finding which command failed, please see debug log below.

That error appears during network operations… for sure I have three network interfaces, eth0 (normal 1 Gig at MB), eth1 and eth3 (two 10 Gigs at PCI-E card), those eth1 and eth3 are bonded together to bond1 (as aggregated link - 802.3ad).

After interface existence check in code is part commented as “Get traffic stats” (line 261 in file network_operations.py) there are two commands one for rx bytes and one for tx bytes, that for tx bytes looks different, so I tried commands in Unraid Console

root@OK-USSTR:~# cat /sys/class/net/eth0/statistics/rx_bytes /sys/class/net/eth0/statistics/tx_bytes
405928273798
545492351685
root@OK-USSTR:~# cat /sys/class/net/eth1/statistics/rx_bytes /sys/class/net/eth1/statistics/tx_bytes
135457907838
159654895112
root@OK-USSTR:~# cat /sys/class/net/eth3/statistics/rx_bytes /sys/class/net/eth3/statistics/tx_bytes
170724649096
11255665434
root@OK-USSTR:~# cat /sys/class/net/bond1/statistics/rx_bytes /sys/class/net/bond1/statistics/tx_bytes
306183579445
170936637188

But for all four interfaces I’ve got response.

Expected behavior

Screenshots

Debug Log

2025-01-07 23:18:09.046 DEBUG (MainThread) [custom_components.unraid.api.vm_operations] Checking VM service status
2025-01-07 23:18:09.048 DEBUG (MainThread) [custom_components.unraid.api.docker_operations] Fetching Docker container information
2025-01-07 23:18:09.050 DEBUG (MainThread) [custom_components.unraid.api.userscript_operations] Fetching user scripts
2025-01-07 23:18:09.122 DEBUG (MainThread) [custom_components.unraid.api.vm_operations] Libvirt validated through process and socket checks
2025-01-07 23:18:09.191 DEBUG (MainThread) [custom_components.unraid.api.docker_operations] Docker validated through process and socket checks
2025-01-07 23:18:09.712 DEBUG (MainThread) [custom_components.unraid.helpers] No disk information found in system stats
2025-01-07 23:18:09.733 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Processing interface: eth0 (normalized: eth0)
2025-01-07 23:18:09.736 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Processing interface: eth1 (normalized: eth1)
2025-01-07 23:18:09.739 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Processing interface: eth3 (normalized: eth3)
2025-01-07 23:18:09.741 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Processing interface: bond1 (normalized: bond1)
2025-01-07 23:18:09.771 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Interface existence check: eth0 (exists=True)
2025-01-07 23:18:09.774 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Interface existence check: eth1 (exists=True)
2025-01-07 23:18:09.778 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Interface existence check: eth3 (exists=True)
2025-01-07 23:18:09.781 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Interface existence check: bond1 (exists=True)
2025-01-07 23:18:09.869 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-01-07 23:18:09.870 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-01-07 23:18:09.913 DEBUG (MainThread) [custom_components.unraid.api.network_operations] First measurement - storing bytes=405791019678 at 2025-01-07T22:18:09.913255+00:00
2025-01-07 23:18:09.913 DEBUG (MainThread) [custom_components.unraid.api.network_operations] First measurement - storing bytes=544497349430 at 2025-01-07T22:18:09.913513+00:00
2025-01-07 23:18:09.913 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Update too frequent (0.000s < 1.000s) - keeping previous rate: 0.00 bits/s
2025-01-07 23:18:09.913 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Update too frequent (0.000s < 1.000s) - keeping previous rate: 0.00 bits/s
2025-01-07 23:18:09.913 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Update too frequent (0.001s < 1.000s) - keeping previous rate: 0.00 bits/s
2025-01-07 23:18:09.913 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Update too frequent (0.000s < 1.000s) - keeping previous rate: 0.00 bits/s
2025-01-07 23:18:09.914 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Update too frequent (0.001s < 1.000s) - keeping previous rate: 0.00 bits/s
2025-01-07 23:18:09.914 DEBUG (MainThread) [custom_components.unraid.api.network_operations] Update too frequent (0.001s < 1.000s) - keeping previous rate: 0.00 bits/s
2025-01-07 23:18:09.997 DEBUG (MainThread) [custom_components.unraid.coordinator] Found parity check cron: # Generated parity check schedule: 0 0 * * 0 /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null

Unraid (please complete the following information):

  • Version 6.2.14

Home Assistant (please complete the following information):

  • Version 2025.1.1

Home Assistant installation type (please complete the following information):

  • [ ] Docker / Container
  • [ ] Virtual Machine
  • [x] Raspberry Pi
  • [ ] Baremetal

Additional context

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 17 (13 by maintainers)

Commits related to this issue

Most upvoted comments

@domalab I can confirm, issue with missing pool disk is fixed, thanks for that.

@domalab ok thank you for that link, I’ll check it, probably I’ll create another instance of HA in docker for that purpose 😊

Issue Resolution Status

The reported issues have been fixed in the latest source code available on GitHub. These fixes are not yet released to HACS and require manual installation.

Manual Installation Instructions

  1. Download the latest code from the GitHub repository
  2. Replace the unraid folder in your Home Assistant custom_components directory
  3. Restart Home Assistant
  4. Verify that the original errors no longer appear in logs

Expected Log Messages (Normal Behavior)

After installation, you may see these messages which are normal and expected:

Critically high memory usage: 1092.9 MB - forcing cache cleanup

These are protective features, not errors. The integration includes intelligent cache management that:

  • Monitors memory usage in real-time
  • Automatically cleans up cache when usage exceeds safe thresholds
  • Maintains system stability and prevents Home Assistant performance issues

These messages indicate the system is working correctly to manage resources.

Fan Detection Warnings

You may also see warnings about fan detection:

No fans detected in sensors data

This is a known limitation due to diverse Unraid hardware configurations. Fan detection challenges include:

  • Different motherboard chipsets and sensor implementations
  • Varying BIOS sensor exposure methods
  • Custom cooling solutions and non-standard fan controllers

Verification

After manual installation, confirm:

  • Original error messages disappear from logs
  • Integration functions normally with expected performance improvements
  • Memory and fan warnings are informational only

Critically high memory usage: 1092.9 MB - forcing cache cleanup

Thanks for checking.

Regarding the last warning of cache cleanup. I implemented a caching system to speed up the integration so it uses a small cache and clears itself.