Often times the script that starts a service running in the background will save the ID of the running process (i.e. the PID) to a well known file in a well known place. That way, when the startup system is asked to restart or stop that background service, it knows which process to send the signal to. If the permissions on the pid file get messed up or the number stored in the pid file get’s out of sync there can be problems.
I would have expected a simple reboot to fix the problem. I fear simply commenting out the line in the start script may cause problems down the road.
Nothing really. openhabian-config calls apt to do the update/upgrade.
You can turn on debug mode. Details are in the openHABian docs.
We’ve been down this path multiple times. It is anything but a simple thing, which is why we remain with openhabian-config.
Proper documentation for what? For openHABian I believe the “stable” set of docs as Introduction | openHAB keeps up with the latest release of openHABian. So what you see there will be up to date, unless you use some other branch of openHABian in which case, see the latest readme on GitHub that corresponds with the branch you are using.
There’s an excellent tutorial posted on contributing to the docs at [Wiki] How to contribute to the openHAB Documentation.
The key is to understand where the docs come from. Since OH has multiple repos, parts of the documentation come from different repos as well and gets compiled into one unified documentation page from those multiple sources.