Openhab 3.4 GUI not working

Hi all,
I am running OH 3.4 on PI3 using openhabian.

The problem is that every few weeks the GUI interface stops responding.

When it happens, OH3 works fine, receive commands and sends commands, send email and notifications, SSH works fine, Karaf is accessible, but the IP:8080 do not connect.
Also HTTP API do not work (HomeHabit & HabPanel do not connect) and sitemaps do not work (even if in the logs the cloud connector is connected)

2023-09-16 17:36:59.263 [INFO ] [io.openhabcloud.internal.CloudClient] - Disconnected from the openHAB Cloud service (UUID = ee...ea, base URL = http://localhost:8080)
2023-09-16 17:37:00.445 [INFO ] [io.openhabcloud.internal.CloudClient] - Connected to the openHAB Cloud service (UUID = ee...ea, base URL = http://localhost:8080)

Apparently everything is fine, but GUI, sitemaps do not work.

logfiles do not show anything related to this behaviour.

Any idea?
How can I restart the HTTP services of OH3 without restarting OH itself?

Maybe it’s possible through Karaf (something like bundle:restart org...jetty) but I don’t think that this is the way you should try.
There is a reason for the malfunction, you have to find that.
When jetty stops working, what’s the output of

free -h

(it’s to get information about free and used memory of the hardware, -h is for human-friendly output)

Now it’s not accessible.
Here is the output:

openhabian@openhabian:~ $ free -h
              total        used        free      shared  buff/cache   available
Mem:          972Mi       773Mi       111Mi       0.0Ki        87Mi       144Mi
Swap:         1.8Gi       344Mi       1.5Gi
openhabian@openhabian:~ $

I agree. I should find the cause. But what is the command to restart the GUI?

So RAM should not be the cause of the hickup.

Not sure about… As I’m not at home right now, I’ll have to take a look later…

As it happens periodically, what could I check or log?

First try (as my Server won’t go down, you’ll have to test…)
Login to the Karaf Console:

openhab-cli console

the default user is openhab (that’s NOT the linux user) and the password is habopen.
If using openHABian to install openHAB, it might even setup the karaf console to be remotely available, so you could use it directly with ssh or PuTTY (openhab-ip and port 8101, credentials as above)

Using username "openhab".
Authenticating with public key "imported-openssh-key" from agent

                           _   _     _     ____
   ___   ___   ___   ___  | | | |   / \   | __ )
  / _ \ / _ \ / _ \ / _ \ | |_| |  / _ \  |  _ \
 | (_) | (_) |  __/| | | ||  _  | / ___ \ | |_) )
  \___/|  __/ \___/|_| |_||_| |_|/_/   \_\|____/
       |_|       4.0.3 - Release Build

Use '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
To exit, use '<ctrl-d>' or 'logout'.


As you can see, I added a public key to login, that’s better in terms of security :slight_smile:
Now, from the Karaf Console, there are many commands - you can get a complete list by typing

openhab> help

To logout from the Console, use

openhab> logout

To restart a specific bundle (here the jetty server) type

openhab> bundle:restart org.eclipse.jetty.server

you can also get a list of bundles by typing

openhab> bundle:list

and even filter the output:

openhab> bundle:list | grep Jetty

but this won’t help as the correct path isn’t listed, so you only get an idea of all bundles which could be involved.

I have no idea :frowning: a crashed Jetty Webservice should emerge in openhab.log, it’s a severe failure…

thanks, will try next time it happens.
Now I had to reboot to solve the issue