I use OpenHAB3 now 3 weeks working fine. Yesterday I see problem that nothing is changed through OpenHAB. When I look at the config there is no things anymore. All items are still there but without the things nothing can be changed.
In the logs I can see the error messages:
Example:
2021-01-19 08:58:34.017 [ERROR] [internal.handler.ScriptActionHandler] - Script execution of rule with UID ‘Rule-System-Start-Komplett’ failed: val telegramAction = getActions(“telegram”,“telegram:telegramBot:5eb3137cf6”) telegramAction. ___ sendTelegram(“OpenHAB neu gestartet!”)
The method sendTelegram(String) is undefined for the type ThingActions; line 1, column 93, length 12
Could you find anything in openhab.log/event.log around the time you guess the configuration disappeared ?
On which Platform are you running OH ?
Where are your configuration files (things/items/…) stored (created via GUI or stored in files locally/NAS/…) ?
A little bit more information about your setup and logfiles are required if you expect help here.
It was just an assumption, and deactivate ZRAM is just a workaround.
You should check the forum if there are already reported similar issues with the same openhabian build.
The ZRAM and SD-card thing on the PI was a reason for me to use a different (more stable) hardware.
But this is just a personal preference.
Minix Neo J50C-4 Mini
Intel Pentium Silver J5005, 4GB, eMMC
Running CentOS8, installed all the required SW “manually”.
I have no need for an all-in-one solution like openhabian, again, just a personal preference.
@maintainers There are several reports in the Facebool group with the same problem: out of nothing things disappear, nothing in the logs. Any idea how to debug that? Is this a core issue or is this an openhabian issue?
For a start, I think it would be good to provide a dump of the json db to see whether it’s corrupted somehow: /var/lib/openhab/jsondb
There are also backups under /var/lib/openhab/jsondb/backup, restoring them could may be at least a workaround until the bug is found and fixed.
Also, I would give a try stopping openHAB and deleting the cache with openhab-cli clean-cache and starting it again. This helps sometimes when weird things have happened.
Ok, in this case deleting cache won’t work, then you definitely need to restore the backup while openHAB is turned off.
Regarding debugging: It could be checked whether multiple instances of openHAB are running which are trying to write to the same file (just an idea…). Thread dumps may also help finding the cause (anyhow, those would have to be taken directly after the issue occured, before openHAB has been restarted).
Disclaimer: I’m not a core maintainer, so I’m just thowing out some ideas. Personally, I use file based configuration so I don’t have this issue.
I suffered from it at the weekend, thankfully I’ve been taking regular backups so was able to restore only losing a few hours work (I’m now taking multiple backups when I’m making changes).
I myself have been seeing the jsondb file be reset to 0 bytes at times in the past.
I never found out but this is unrelated to openHABian and ZRAM. If it was ZRAM related it could only show up on power outage and reboots: if there was a failure in saving files that changed during operations with ZRAM enabled, they would get reset to their last checkpoint save’s version (file version at system/ZRAM startup). Assuming you properly shutdown/reboot your machine once in a while that should not be 0 bytes then but show at least the last checkpointed version (unless that has been 0 bytes ever).
It was me providing this bug-report and wondered if I’m the only one facing this problem. But yes, indeed, can confirm that with a recent nightbuild, the problem is gone. In fact previously the CPU-load on one core was very high. Since this issue was fixed, my Raspi4b can relax now