I have Hass.io running on an ESXI vm (used to be on an RPi, but I moved it) and have the Duck DNS plug-in installed and configured. Everything works great - dynamic dns, ssl, all good.
However, I happened to click on the plug-in’s control page today (I was checking if any plug-ins needed updating) and noticed it wasn’t running, despite being set to “auto-start” and the system having been recently rebooted for unrelated reasons.
So I clicked start. It spun, and came back to the same screen, not running. Scrolling down to the log, I found this:
# INFO: Using main config file /data/workdir/config
ERROR: Lock file '/data/workdir/lock' present, aborting.
I’m honestly even sure anything is wrong, since everything seems to be working, but figured I’d check. Is this plug-in supposed to be constantly running like most others? Is this normal behavior? Should I delete the lock file and try starting again?
The only one of those questions I can answer is yes, the add-on should be running at all times if you want the DNS updater feature to work. On my system, It’s been running since the box was last rebooted and I can see in the logs that it is checking for an IP change to update the DNS entry every 5 minutes.
Infact, it shows that in the log for the plugin:
Fri Nov 30 10:32:13 EST 2018: OK
XXX.XXX.XXX.XXX
NOCHANGE
Fri Nov 30 10:37:13 EST 2018: OK
XXX.XXX.XXX.XXX
NOCHANGE
Fri Nov 30 10:42:13 EST 2018: OK
XXX.XXX.XXX.XXX
NOCHANGE
As for the error you are seeing regarding the lock file, I’m not sure and haven’t experienced that myself. Someone else can hopefully chime in with more information there.
You could always try uninstalling the add-on, restarting, then re-installing.
If you still have issues you could try doing the above process again, but manually deleting the certs in your SSL folder before re-installing the add-on, and see if they get re-created.