openHAB not starting after upgrade 3.0.2 -> 3.1.0

After upgrade from 3.0.2 to 3.1.0 my Openhab does not work

Sorry, but this info is useless,
What does not work? Show us the errors in the log.

1 Like

After Upgrade port 8080 is unreachable and port 9001 don´t show any log.

Could you logon to your system and show the output of

sudo journalctl -u openhab -b

the upgrade seems to require a couple restarts to get going
edit: sometimes requires a couple restarts

Not always, mine did not…

Obviously, it’s the first thing I did.

openHAB does not use port 9001. Some users of openHANian have installed Frontail that uses port 9001.

Your title says upgrading from OH2 to 3 but your post says 3.0.2 to 3.1.0 Which is it??

Are you using openHABian?

How to ask a good question / Help Us Help You - Tutorials & Examples - openHAB Community

I use openhabian and have migrated from 3.0.2 to 3.1.0. I have already corrected the error of the title

the 9001 port is the frontal, but the real problem is that nothing new appears in the logs

After upgrade and before reboot:

[06:27:41] openhabian@openHABianPi:/var/log/openhab$ sudo journalctl -u openhab -b
– Logs begin at Tue 2021-07-06 05:40:00 CEST, end at Tue 2021-07-06 06:27:43 CEST. –
Jul 06 05:40:09 openHABianPi systemd[1]: Started openHAB instance, reachable at http://openHABianPi:8080.
Jul 06 06:13:54 openHABianPi karaf[582]: Loading class com.mysql.jdbc.Driver'. This is deprecated. The new driver class is com.mysql.cj.jdbc.Driver’. The driver is automatically registered via the SPI and manual loading of the driver c
Jul 06 06:14:01 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:01 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:01 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:01 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:01 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:14:02 openHABianPi karaf[582]: Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
Jul 06 06:21:52 openHABianPi systemd[1]: Stopping openHAB instance, reachable at http://openHABianPi:8080
Jul 06 06:22:01 openHABianPi karaf[582]: org.osgi.framework.BundleException: Unable to acquire the state change lock for the module: osgi.identity; type=“osgi.bundle”; version:Version=“3.12.100.v20180210-1608”; osgi.identity="org.eclipse
Jul 06 06:22:01 openHABianPi karaf[582]: at org.eclipse.osgi.container.Module.lockStateChange(Module.java:337)
Jul 06 06:22:01 openHABianPi karaf[582]: at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.asyncStop(EquinoxBundle.java:156)
Jul 06 06:22:01 openHABianPi karaf[582]: at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle.stop(EquinoxBundle.java:262)
Jul 06 06:22:01 openHABianPi karaf[582]: at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle.stop(EquinoxBundle.java:267)
Jul 06 06:22:01 openHABianPi karaf[582]: at org.eclipse.osgi.launch.Equinox.stop(Equinox.java:123)
Jul 06 06:22:01 openHABianPi karaf[582]: at org.apache.karaf.main.Main$2.run(Main.java:354)
Jul 06 06:22:01 openHABianPi karaf[582]: Caused by: java.util.concurrent.TimeoutException: Timeout after waiting 5 seconds to acquire the lock.
Jul 06 06:22:01 openHABianPi karaf[582]: at org.eclipse.osgi.container.Module.lockStateChange(Module.java:334)
Jul 06 06:22:01 openHABianPi karaf[582]: … 5 more
Jul 06 06:23:04 openHABianPi systemd[1]: Stopped openHAB instance, reachable at http://openHABianPi:8080.
Jul 06 06:23:42 openHABianPi systemd[1]: Started openHAB instance, reachable at http://openHABianPi:8080.
Jul 06 06:23:47 openHABianPi systemd[1]: Stopping openHAB instance, reachable at http://openHABianPi:8080
Jul 06 06:23:48 openHABianPi karaf[3660]: /var/lib/openhab/tmp/port shutdown port file doesn’t exist. The container is not running.
Jul 06 06:23:48 openHABianPi systemd[1]: openhab.service: Control process exited, code=exited status=3
Jul 06 06:23:49 openHABianPi systemd[1]: Stopped openHAB instance, reachable at http://openHABianPi:8080.
Jul 06 06:23:49 openHABianPi systemd[1]: openhab.service: Unit entered failed state.
Jul 06 06:23:49 openHABianPi systemd[1]: openhab.service: Failed with result ‘exit-code’.
Jul 06 06:23:49 openHABianPi systemd[1]: Started openHAB instance, reachable at http://openHABianPi:8080.
lines 1-43/43 (END)

after reboot:
[06:36:45] openhabian@openHABianPi:~$ sudo journalctl -u openhab -b
[sudo] password for openhabian:
– Logs begin at Tue 2021-07-06 06:33:26 CEST, end at Tue 2021-07-06 06:36:51 CEST. –
Jul 06 06:33:35 openHABianPi systemd[1]: Started openHAB instance, reachable at http://openHABianPi:8080.

But port 8080 is unreachable and nothing appears at openhab.log and events.log.

As there is an entry

that could look like a file could not be written I would try two things:
a) use menu 14 in openhabian-config fix permissions
if that does not help run
b) follow the steps as described in Clear the Cache

What does
sudo netstat -tulpn | grep java
show ?

1 Like

Same issue for me. Running OH on Raspi4 with Openhabian image.

  • Can start OH 3.1
  • OH Process running on 100% on 1 core forever
  • No log output
  • no Web UIs

sudo openhab-cli clean-cache

did solve the problem. “Fix permissions” did not help.
I’m still struggling with the charts on HABPanel, they are not showing up, only a “broken link” icon