Infinite loop on clean install

Hi,

My previous openHAB installation on RP3B+ broke and I was not able to recover it.

So I started a new clean install, got through all the regular hassles with RP3B+ and OpenHABianPi like wifi not connecting and many other issues, untill finally I was able to get through the whole installation process without any problems, everything seems to be in place except for 1 “little” detail.

With monitor behind the RaspberryPi I can see an infinite loop of:

[   OK   ] Started openHAB 2 - empowering the smart home.
[   OK   ] Stopped openHAB 2 - empowering the smart home.
[   OK   ] Started openHAB 2 - empowering the smart home.
[   OK   ] Stopped openHAB 2 - empowering the smart home.
[   OK   ] Started openHAB 2 - empowering the smart home.
[   OK   ] Stopped openHAB 2 - empowering the smart home.
[   OK   ] Started openHAB 2 - empowering the smart home.
[   OK   ] Stopped openHAB 2 - empowering the smart home.
[   OK   ] Started openHAB 2 - empowering the smart home.

And so on … ( I guess you get the idea)

I have no idea what could be causing this but accessing openhab via web is not possible.

Hope someone can help.

Best regards,

Alari

Thought I’d also include this BEAUTIFUL picture :slight_smile:

1 Like

The last few lines in /boot/first-boot.log are:

2019-03-20_22:29:24_EET [openHABian] Adding an openHAB dashboard tile for 'frontail'... OK
2019-03-20_22:29:24_EET [openHABian] Execution of 'openhabian-setup.sh unattended' completed.
2019-03-20_22:29:24_EET [openHABian] Waiting for openHAB to become ready...

There is /opt/openHABian-install-successful file but no afterfirstboot.lock file anywhere but also no in progress or failed files, and every time raspberry restarts it goes through all the first-boot script things…

Tried almost everything by now and have a huge headache

Re installed with clean image 4 times, manually created afterfirstboot.lock file, now reran FireMotD instals and configs all the different ways, installed new java, updated openhab2-addons, removed openhab2-addons and openhab2, reinstalled them both to see if anything changes… nothing…

systemctl status openhab2.service gets me

Process: 15521 ExecStop=/usr/share/openhab2/runtime/bin/karaf stop (code=exited, status=127)
Process: 15452 ExecStart=/usr/share/openhab2/runtime/bin/karaf $OPENHAB_STARTMODE (code=exited, status=127)
Main PID: 15452 (code=exited, status=127)

journalctl -u openhab2.service -b gets me:
Mar 20 23:22:23 openHABianPi systemd[1]: Started openHAB 2 - empowering the smart home.
Mar 20 23:22:24 openHABianPi karaf[444]: /usr/share/openhab2/runtime/bin/karaf: 233: [: Illegal number:
Mar 20 23:22:24 openHABianPi karaf[444]: /usr/share/openhab2/runtime/bin/karaf: 233: [: Illegal number:
Mar 20 23:22:24 openHABianPi karaf[444]: /usr/share/openhab2/runtime/bin/karaf: 285: [: Illegal number:
Mar 20 23:22:24 openHABianPi systemd[1]: openhab2.service: Main process exited, code=exited, status=127/n/a
Mar 20 23:22:24 openHABianPi karaf[542]: /usr/share/openhab2/runtime/bin/karaf: 233: [: Illegal number:
Mar 20 23:22:24 openHABianPi karaf[542]: /usr/share/openhab2/runtime/bin/karaf: 233: [: Illegal number:
Mar 20 23:22:24 openHABianPi karaf[542]: /usr/share/openhab2/runtime/bin/karaf: 285: [: Illegal number:
Mar 20 23:22:24 openHABianPi systemd[1]: openhab2.service: Control process exited, code=exited status=127
Mar 20 23:22:24 openHABianPi systemd[1]: openhab2.service: Unit entered failed state.
Mar 20 23:22:24 openHABianPi systemd[1]: openhab2.service: Failed with result ‘exit-code’.

What do the commands:

openhab-cli info
java -version

Produce?

Hi @Alluuu, I installed a fresh installation and came across the same error.

After debugging, I’ve come to the conclusion that this is an issue caused by setting the capabilities of java. To fix your issue:

sudo ln -s /opt/jdk/zulu8.36.0.152-ca-jdk1.8.0_202-linux_aarch32hf/lib/aarch32/jli/libjli.so /usr/lib/

Where zulu8.36.0.152-ca-jdk1.8.0_202-linux_aarch32hf is the assumed version that the script installed, it may vary slightly.

Thank you so much @Benjy !

I did this and seems most of the errors have disappeared, still no openhab @openhabianpi:8080 connection refused, but I’ll get over that I’m pretty sure.

Since I’ve done so much stuff here now that I my raspberry could be quite bloated and not the best setup, I’ll do one more fresh clean instal where your symlink is in first-boot.sh and see if I get nice install results with this or not.

Cheers!

Please don’t mix the different services:

I sent a fix through, so this shouldn’t happen anymore. Please let me know if you have any other issues.

@Benjy works perfectly, love you!

I did however install everything with cable attached and only afterwards set up wifi. wifi works and everything works just when starting up I get dhcpcd service failed error and status is also:

 dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/dhcpcd.service.d
           └─wait.conf
   Active: failed (Result: exit-code) since Thu 2019-03-21 16:54:34 EET; 36min ago
  Process: 343 ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -w (code=exited, status=6)

Mar 21 16:54:34 openHABianPi systemd[1]: Starting dhcpcd on all interfaces...
Mar 21 16:54:34 openHABianPi dhcpcd[343]: Not running dhcpcd because /etc/network/interfaces
Mar 21 16:54:34 openHABianPi dhcpcd[343]: defines some interfaces that will use a
Mar 21 16:54:34 openHABianPi dhcpcd[343]: DHCP client or static address
Mar 21 16:54:34 openHABianPi systemd[1]: dhcpcd.service: Control process exited, code=exited status=6
Mar 21 16:54:34 openHABianPi systemd[1]: Failed to start dhcpcd on all interfaces.
Mar 21 16:54:34 openHABianPi systemd[1]: dhcpcd.service: Unit entered failed state.
Mar 21 16:54:34 openHABianPi systemd[1]: dhcpcd.service: Failed with result 'exit-code'.
Warning: dhcpcd.service changed on disk. Run 'systemctl daemon-reload' to reload units.

Doesn’t seem to be causing nay problems thus far…