core: Udevd[528]: bind failed: Address in use
The problem
Since OS 5.10 in console following:
Udevd[528]: bind failed: Address in use
Udevd[528]: error binding udev control socket
ha core info: arch: amd64 audio_input: None audio_output: None boot: true image: homeassistant/qemux86-64-homeassistant ip_address: 172.30.32.1 last_version: 2021.2.2 machine: qemux86-64 port: 8123 ssl: false update_available: false version: 2021.2.2 version_latest: 2021.2.2 wait_boot: 600 watchdog: true
ha os info: board: ova boot: B update_available: false version: “5.11” version_latest: “5.11”
What is version of Home Assistant Core has the issue?
core-2021.2.2
What was the last working version of Home Assistant Core?
core-2021.2.2
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Example YAML snippet
# Put your YAML below this line
Anything in the logs that might be useful for us?
pls let me know logs you additonal need:
# Put your logs below this line
Have also the problem of a long shutdown, booting is verry fast but shutdown took 220 sec where the cpu load is at 1%. A start of complete VM took 45sec, a reboot of HA (startet in server menu) need 4 min and 10 sec.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (8 by maintainers)
There is no reason in your response. Only a message to ignore it.
No “me”. “we”… and thus there “must be something significantly changed”.
What is the reason for the udevd error?
That is expected, almost everybody has that message at this point, as stated before, that message can be ignored, does not affect any startup times. If you have an issue, you are blindly starring at the wrong error message.
See here… I cannot proof it but I am not alone…
https://community.home-assistant.io/t/udevd-529-bind-failed-address-in-use/278578
This particular error is not affecting start-up times or performance. If you have performance issues, this might be throwing you off.
It is noticabely affecting the startup, and performance of my instance. What is caising this and when and how will this be possibly resolved?
(👋 Hi, See how cautious I ask his question)