OH failed - but why?


I did a fresh OH installation in January. I’ve installed Telegram-Bot(most recend addition), Systeminfo, Mqtt Broker, Shelly, Fritz!Box and Homematic.
Everything was working fine until yesterday when I couldn’t open the garage using the HM-Remote.

Since it was already late I just had a quick look at the panel - everything seemed to be fine except the broker binding showed ‘offline’.

Today I checked the logs, but all I could see was that it stopped logging yesterday around 12pm. Last logentry was MQTT communication error. I thought that maybe the RPi ran out of memory (happend to me once before) but that wasn’t the case. I rebooted the system and everything is working fine again now, but I need to find out what happend and why.

Any suggestions on what to try and where to look?

  • Platform information:
    • RPi 4: 8GB ram + dev/nvme0n1: 223.57 GiB
    • Flashed with Openhabian
    • openHAB version: openHAB 3.4.1 - Release Build

Which logs have you checked ? Have you checked

  • the brokers log file
  • the system.log file
  • output of journalctl
  • output of dmesg

what does that mean, did you move your system to SSD or some such ?
That would not be a supported configuration.

The 8GB RPi won’t run out of mem (unless you do things beyond OH to cause that) but as you should have read in the openHABian instructions before installing, it isn’t recommended to use either.
For one because it’s overkill but also there’s effects that apply for >4G only you might suffer from
(4G is a significant limit similar to the 640KB in early PC days).


I checked /var/log/mosquitto/mosquitto.log and /var/log/openhab/openhab.log /var/log/openhab/events.log. In the mosquitto log there were a couple of lines stating that it was saving the in-memory database - seemed to be fine. OH eventlog stopped after the com error.
I just now had a look at journalctl, but the last entry before the reboot is from Feb 09. I did however noticed some issues with the zigbee2mqtt.service. Dmesg … well, not sure what to make from it. There are a couple of red marked lines. Might be startup related?

Yes. I’ve got an OH installation at my house running on SSD for 4yrs now. I’m not going back to SD cards as they failed me one too many times. The 8GB RPi was what I had lying around when I setup OH at my girlfriends place.
I was reading the documentation prior installation. Thank you all so much for the good work providing it!

Well, then in short now you’re paying the price for not listening to what’s written in there.

Please also respect this from now on.
That means: don’t ask for help on this any more. That’s a real no-go as you yourself have caused the issue.

nothing for the moment. It contains information since boot.
In case it happens again check its output before booting.

1 Like

I’ll do that. Thanks for your help!

Markus, I disclosed my setup directly in the first post. I don’t expect any support from you or others, but I am grateful for any help. I’m not the only user with an SSD, a setup that hasn’t caused me any problems for years, and if there are users here who are willing to provide me with support - why should I refrain from making use of it?
I have been using OH since 2016! Stable operation was only possible after I switched from SD to SSD. It is clear to me that a lot of work has been done here to ensure such stable operation on SD as well, but as the saying goes → never change a winning team.

Not really, it was somewhat hidden and I had to ask first to get it confirmed.
Costed my time and attention and that of many others to read your post.

You are free to use whatever you want, that isn’t the point.

But when it does not work because you ignored the docs (that are clearly saying it is not supported) in the first place, you are NOT free to ask for help as you KNOW yours is not a SUPPORTED setup,
and the docs are very explicit on even this. They are asking you NOT to ask for help on the forum.

You nonetheless did. And when you nonetheless did, you showed that you are not respecting community member’s (including myself) valueable time and efforts.

And THAT is the no-go !

In addition to the link on SSD support that I had already referred you to and for your and others’ reference, here’s the relevant excerpt of the docs that you claimed you had read.

What you must not do, though, is to mess with the system, OS packages and config and expect anyone to help you with that. Let’s clearly state this as well: when you deliberately decide to make manual changes to the OS software packages and configuration (i.e. outside of openhabian-config), you will be on your own. Your setup is untested, and no-one but you knows about your changes. openHABian maintainers are really committed to providing you with a fine user experience, but this takes enormous efforts in testing and is only possible with a fixed set of hardware. You dont get to see this as a user.

So if you choose to deviate from the standard openHABian installation and run into problems thereafter, dont be unfair: don’t waste maintainer’s or anyone’s time by asking for help or information on your issues on the forum. Thank you !

Just a thought - how about creating a separate category for unsupported setups? People running unsupported setups might be willing to help each other and those who are not interested can simply ignore that category.


It won’t solve the problem that people either don’t read or even intentionally ignore docs and forum rules.
Note I edited my post to reflect the even more explicit passage from the docs I meant to refer to.

True, but that happens today anyway.

If you give people a category, at least some of those questions will be raised there rather than in the general category. Of course there might still be an overall increase in the volume of questions concerning unsupported setups, but I believe that it will be a net gain for the community.

1 Like

I’m afraid it’s a waste of time to debate this subject further in this forum. The fronts are entrenched (similar debates with Markus can be found all over this forum), the community is divided, and there are several unofficial places where people exchange information about OH in a civilised and constructive way, without the restrictions imposed on those who put stable setups with industry-standard hardware above the laws that exist here.
Is this a good development? I doubt it very much, but what can you do? I like the software, especially because of the powerful rule processing that I use intensively, but maybe it’s time to investigate the alternatives?

I haven’t seen anything in this thread that indicates an unwillingness to listen. I can understand the maintainers’ frustration with having to deal with requests for help that go against “if you want help, you need to do it this way” and it is of course the project’s decision how to support the tools it gives away for free.

However, when pushing people away from the official channels, it results in additional fragmentation and I think we as a community would benefit from gathering us much knowledge as possible under one roof.

If you have openhab issues, of course you will get support, but in terms of openhabian you will face such discussions. just imagine the amount of devices and workload the openHABian maintainers would need to invest to approve all different kind of configurations.

  • RasPi2/3/4 that boots from SD card
  • RasPi2/3/4 that boots from USB thumbdrive
  • RasPI2/3/4 that boots from USB SSD
  • all with 32bit or 64bit linux base image

All in all openHABian is a very stable and reliable system, but this only can be assured with extensive testing and this can be only assured of you define some HW requirements for which you then will get (free, unpaid) support.

Please make a clear distinction.
“The forum” is various people that each speak for themselves and decide on their own if they want to respond to, work for, or support others.
If you now explicitly and technically ask the openHABian maintainer, me that is, the answer is no, this being the reason:

It’s not about how you get there, and flashing to SSD results in the same setup as moving it over.
There’s various aspects to this, but a major technical reason is that much of the code uses SD device specific functionality including hardcoded names and as such can fail with other storage media like SSD or HDD.
Remember openHABian has a lot more functionality than just to boot, also think of mirroring and backup.

I’ll only add the following.

  1. Each and every individual on this forum speaks only for themselves. There is no universal forum policy or rules that are strictly enforced. It’s all a bunch of individuals with their own pet peeves and topics they are enthusiastic about. The only rules that are enforced by the moderators are violations of the forum rules (no spam, be nice, be civil, etc). Everything else, unless otherwise stated, is to be taken as the opinion of that one user and not the stance of the openHAB Foundation, openHAB project nor the openHAB forum and it’s community of users. In short, @mstormi’s opinion on this topic has no more or less right to be expressed on this forum than @Wolfgang_S, @gerrit, @peterhoeg, @Magnus, @Sascha_Billian, or myself (If I forgot someone I apologize).

  2. Any deviation from the configuration outlined in the openHABian docs is no longer openHABian. That’s what we mean by unsupported. It’s not that it won’t work. It means that you’ve left the realm of what the openHAB project provides. If you need help with a problem, particularly a problem unrelated to the openHAB software itself, it’s likely going to be a waste of your time and our time asking for help here on this forum. You are more likely to find your answers on an Raspberry Pi OS forum, generic Linux forum, stackoverflow, or one of the many other resources for getting help with generic Linux or Raspberry Pi OS problems. To put it bluntly, if you know better how to set up your RPi than openHABian and decide to deviate from openHABian, you should know better about how to fix it when problems arise.