I’m getting an error running the ‘Check Home Assistant configuration’ add-on
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing...
bind failed: Address in use
error binding udev control socket
[20:41:58] INFO: Update udev information
@klogg, did you figure this out? I am having the same issue. I am on HAOS 5.13, which is the latest version, running in a VM on Proxmox. Currently running HA 2021.3.4.
edited to add - I rebooted my host and tried again…got the same error, but after a few minutes the addon did download the new version and complete the check. So never mind!
I am having the same issue. I start the add-on and it appears to be running and then about 5 minutes later the add-on stops. I copied the log file for the add-on after starting it and then copied it again after it stops. Here is what is in the log file. I am totally new to Home Assistant so I don’t understand any of what is happening except it says the process is being killed.
Log after startup of “Check Home Assistant configuration” add-on.
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] udev.sh: executing…
bind failed: Address in use
error binding udev control socket
[12:59:09] INFO: Update udev information
Log after “Check Home Assistant configuration” add-on stops.
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] udev.sh: executing…
bind failed: Address in use
error binding udev control socket
[12:59:09] INFO: Update udev information
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:01:09] INFO: Setup udev devices
[13:01:10] INFO: Don’t worry, this temporary installation is not overwriting your current one.
[13:01:10] INFO: Installing Home Assistant: latest…
[13:01:10] INFO: Please be patient, this might take a few minutes…
[13:02:28] INFO: Installed Home Assistant 2021.4.6
[13:02:28] INFO: Making a copy of your configuration for checking…
[13:02:28] INFO: Checking your configuration against this version…
[13:05:45] INFO: Configuration check finished - no error found!
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
This is working exactly the way it is supposed to. The line that has the smiley-face says
Configuration check finished - no error found!
That means it finished fine and you should have no issues updating. If there were errors, it would give you some clue where to start looking for the problem. Once the addon is finished running, it stops, hence the last lines in the log file.
I am glad to hear that is normal but the confusing part was how it worked before. I installed the add-on about 2 weeks ago and it has been running without stopping until the last couple days. I noticed it stopped and would start it back up but it would then stop again. I figured something was wrong since it ran for almost 2 weeks without stopping. Thanks again!!
Not quite sure what you mean by running without stopping. You only need to start the addon and run it when you want to do a check. It runs the check and then it is finished. I have mine set to not start on boot, and I only start it when I want to run a config check.
I was just trying to say that when I went to the add-on and looked at the info tab, it was always running because the START button was not there. It always had the STOP and RESTART buttons. I assume that meant it was running since the START was not a choice. Suddenly the other day is when I noticed the START button was the option and the STOP and RESTART were not there anymore. I guess it’s working fine now.
Thanks
