2024.8.3 hangs with iperf3

[532910]

The problem

ha hangs completely

What version of Home Assistant Core has the issue?

2024.8.3

What was the last working version of Home Assistant Core?

2024.8.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

iperf3

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[mib1185]

Hi @532910 there is not much to analyse, please provide more details about your issue, how to reproduce, what is your configuration, anything in the log file. Help us to help you, thx :+1:

[532910]

nothing in the log steps to reproduce: 2024.8.3 + iperf3

[mib1185]

sorry but this is still to less information, show us your iperf3 configuration and explain when the hang occur (at HA start time or later or after doing something)

[532910]

it occurs after some time of working

iperf3:
  hosts:
    - host: <my server vpn IPv4>
    - host: <my server wan IPv4>
    - host: <my server wan IPv6>
  scan_interval:
    minutes: 10

I have 2 differerent HA (arm64 superwised / amd64 qemu haos) with different set of integrations and with the same iperf3 config. Once I updated both to 2024.8.3 both started to hang. I downgraded one of them and disabled iperf3 on another and both stopped hanging.

[home-assistant[bot]]

Hey there @rohankapoorcom, mind taking a look at this issue as it has been labeled with an integration (iperf3) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of iperf3 can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign iperf3 Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

iperf3 documentation iperf3 source _{^{(message by IssueLinks)}}

[532910]

Any update? It looks like iperf3 should be removed, as it breaks HA.

[mib1185]

What exactly means "started to hang"? Is HA just slow or not usable anymore? What is the cpu and memory utilization in this moment? Further please restart HA in safe mode and check if the issue still occur.

Alos please, try to setup with only one iperf server and check again. Further enabling debug logging might be helpful - do so add the following to your configuration.yaml:

logger:
  default: info
  logs:
    homeassistant.components.iperf3: debug
    iperf3: debug

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

btw. there was not any code change in the iperf3 integration since 6 months, so an update from 2024.8.2 to 2024.8.3 should not break anything here.

[532910]

Ha you tried to reproduce this issue?

"Started to hang" means that it works worse and worse until it stops completely, and becomes completely unusable. CPU and RAM is OK. I didn't find anything strange, even in the debug logs.

[mib1185]

Ha you tried to reproduce this issue?

Nope, because I've no iperf server available.

Did you try my other suggestions - restart in safe mode and setup only one iperf server? As mentioned above, there was no code change and in the iperf integration for 6 months - were there any other changes in your environment, besides the ha update from 2024.8.2 to 2024.8.3?

[532910]

It's pretty simple to install it: apt install iperf3.

Did you try my other suggestions - restart in safe mode and setup only one iperf server?

I'd not like to experiment on my HAs. Both are used by other people.

As mentioned above, there was no code change and in the iperf integration for 6 months - were there any other changes in your environment, besides the ha update from 2024.8.2 to 2024.8.3?

As mentioned above, exactly one of two actions: "downgrade to 2024.8.2" or "disable iperf on 2024.8.3" makes HA work fine.

[mib1185]

It's pretty simple to install it: apt install iperf3.

This counts only for debian based linux systems :wink:

I'd not like to experiment on my HAs. Both are used by other people.

But without any checks on your HA instance, which has the issue, how should we analyse the issue for your instance?

As mentioned above, there was no code change and in the iperf integration for 6 months - were there any other changes in your environment, besides the ha update from 2024.8.2 to 2024.8.3?

As mentioned above, exactly one of two actions: "downgrade to 2024.8.2" or "disable iperf on 2024.8.3" makes HA work fine.

My question was more about, were there any other changes, which could be the cause for this issue? Because there were not any changes within the last 6 months in the iperf3 integration, it's most properly something else causing this issue - maybe a custom component or changes to your iperf servers? Maybe 3 iperf measurements simultaneously just exhaust the network interface of your HA instance? But without anything to analyse, it is all only guessing.

Please provide the homeassistant.log with enabled debug logging as mentioned in https://github.com/home-assistant/core/issues/125034#issuecomment-2341282505 , further -if you use any custom components- please also restart in safe mode and check again

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[532910]

stale is not a reason to close issues

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[532910]

stale is not a reason to close issues

[mib1185]

You might want to check https://github.com/home-assistant/core/issues/125034#issuecomment-2351511023

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[532910]

stale is not a reason to close issues

[mib1185]

You might have overlooked my previous comments?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.