Network Binding has to be re-added on a reboot or an systemctl restart openhab2.service

[ltgcc]

Network Binding has to be re-added on a reboot or an systemctl restart openhab2.service.

System info at the bottom.

Problem is consistently repeatable:

[12:58:27] root@openHABianPi:~# systemctl restart openhab2.service
[12:59:01] root@openHABianPi:~# systemctl status openhab2.service
● openhab2.service - openHAB 2 - empowering the smart home
Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-10-08 12:59:01 AKDT; 8s ago
Docs: Introduction | openHAB
https://community.openhab.org
Process: 9268 ExecStop=/usr/share/openhab2/runtime/bin/karaf stop (code=exited, status=0/SUCCESS)
Main PID: 9455 (java)
Tasks: 26 (limit: 4915)
CGroup: /system.slice/openhab2.service
└─9455 /usr/bin/java -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab2 -Dopenhab.runtime=/usr/share/openhab2/runtime -Dopenhab.userdata=/var/lib/openhab2 -Dopenh

Oct 08 12:59:01 openHABianPi systemd[1]: Started openHAB 2 - empowering the smart home.

openhab.log:

[13:00:11] root@openHABianPi:~# cat /var/log/openhab2/openhab.log | grep -i network | grep -vi Z-Wave | grep -vi zwave

2019-10-08 12:59:40.848 [DEBUG] [etControllerCapabilitiesMessageClass] - Controller is on other network = false
2019-10-08 12:59:47.542 [INFO ] [core.karaf.internal.FeatureInstaller] - Uninstalled ‘openhab-binding-network’
[13:00:36] root@openHABianPi:~#

Attempts to fix:

updated to current via openhabian-config
fixed permissions via openhabian-config “Fix Permissions”

Looking in the community for ‘network binding uninstalled’ and 'network binding uninstalled on restart gave several hits:

This seems to be the most relevant one:

Bindings added through PaperUI being auto-uninstalled?

Same here Fresh OpenHabian image on a Pi3, all seemed well with z-wave and harmony working nicely. Left it running overnight, came back to find no bindings and no things in the UI at all.

but appears to be unresolved.

This also has information, but seems to indicate that there are incompatibilities between paperui and various config files, some of which appear to be openhabian specific. Perhaps openhabian is not well understood by newbs such as myself?
There were other hits that seemed to be openhabian related.

OH2 on restart is forgetting all binding and loading the demo binding

here my addons.cfg: # The installation package of this openHAB instance # Note: This is only regarded at the VERY FIRST START of openHAB # Note: If you want to specify your add-ons yourself through entries below, set the package to "minimal" # as otherwise your definition might be in conflict with what the installation package defines. # # Optional. If not set, the dashboard (https://<yourserver>:8080/) will ask you to choose a package. # # Valid options: # - minimal : Installation only with…

Not sure what to do now. Suggestions?

Thanks,

Relevant info below:

[12:44:43] root@openHABianPi:~# uname -an
Linux openHABianPi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux

[12:45:21] root@openHABianPi:~# openhab-cli info

Version: 2.4.0 (Build)

User: openhab (Active Process 23626)
User Groups: openhab tty dialout audio bluetooth gpio

Directories: Folder Name | Path | User:Group
----------- | ---- | ----------
OPENHAB_HOME | /usr/share/openhab2 | openhab:openhab
OPENHAB_RUNTIME | /usr/share/openhab2/runtime | openhab:openhab
OPENHAB_USERDATA | /var/lib/openhab2 | openhab:openhab
OPENHAB_CONF | /etc/openhab2 | openhab:openhab
OPENHAB_LOGDIR | /var/log/openhab2 | openhab:openhab
OPENHAB_BACKUPS | /var/lib/openhab2/backups | openhab:openhab

URLs: http://192.168.22.15:8080
https://192.168.22.15:8443

[12:45:34] root@openHABianPi:~# java -version
openjdk version “1.8.0_222”
OpenJDK Runtime Environment (Zulu8.40.0.178-CA-linux_aarch32hf) (build 1.8.0_222-b178)
OpenJDK Client VM (Zulu8.40.0.178-CA-linux_aarch32hf) (build 25.222-b178, mixed mode, Evaluation)

[13:00:36] root@openHABianPi:~# cat /etc/openhab2/services/network.cfg
binding.network:allowSystemPings=true
binding.network:allowDHCPlisten=true
binding.network:arpPingToolPath=arping
binding.network:cacheDeviceStateTimeInMS=2000

[13:02:31] root@openHABianPi:~# find /etc/openhab2 -iname “network”
/etc/openhab2/services/network.cfg
[13:03:11] root@openHABianPi:~#

[13:03:11] root@openHABianPi:~# find /usr/share/openhab2 -iname “network”
[13:04:31] root@openHABianPi:~#

[rlkoshak (Rich Koshak)]

The first link has a post with a link to an issue that should be resolved. But in case it isn’t, did you read the discussion in that issue and stop openHAB and delete userdata/etc/org.openhab.addons.cfg?

@ltgcc

This also has information, but seems to indicate that there are incompatibilities between paperui and various config files, some of which appear to be openhabian specific.

No, they are not openhabian specific. They exist in all openHAB installations regardless of what operating system you install it on. You have two ways you can configure openHAB. One is through the UIs and the other is using text based configs. You don’t mention which approach you are using but you cannot mix and match them (e.g. install some bindings using PaperUI and other bindings using addons.cfg). If you’ve installed a bunch of bindings using addons.cfg and then try to install the Network binding through PaperUI, the one installed through PaperUI will get uninstalled as addons.cfg will always take precedence.

The network.cfg file is not relevant to this issue.

[ltgcc]

Thank you for the reply. As it turns out because more and more weirdnesses were accumulating I decided to simply do a fresh install. And that cleared this up, as well as most of the other weirdnesses. It also, by sheer timing, gave me a ‘buster’ based system, all to the good.

Of course, now there are new weirdnesses (but so far only one). I will post those separately.

Thank you again.