OH3: stops logging... system seems working... some items do not update

Max_G · November 15, 2022, 3:12am

openHABian 3.3.0 on rPi4

I have been migrating form OH2 to OH3 over the last couple of weeks…
Adding bindings, creating things and items in the UI; using rules in text files.
I copy the latter and, check what errors out and fix these, with three key issues/fixes to address:

mail/mqtt actions
now > ZonedTime
executeCommandLine

Maybe 4: replace the "last updated " items with a channel config.

All going well.

I have two terminals open on the OH3 machine:

karaf
any command line I need to run; e.g. find openhab2 (in some paths that need changing) or a tail on openhab.log

I noticed that one item did not update over night; checked the flow (channel, item) for correctness, felt to look at this later, and for the time being updated it in the karaf console.

Well, it still did not update the item in the sitemap despite karaf saying it did.

A few minutes later, logging stopped, as is frontail logging stopped.

I then ended karaf to run top to see, if the system is still working; which it was. But as I closed kraf, logging continued, actually catching up on what it missed since it stopped.

…

Just to stop again.

Now openhab.log listed the rules file I was working in, and started complaining about other rules. The language server then disconnected from vsCode.

Then I thought, doing all this work and adding tons of stuff (as in migrating from OH2), maybe a OH restart is in order, and issued sudo openhab-cli stop; which seems to shutdown OH, but also seems to restart it by itself.

All came up seemingly normal, but logging stopped after some 5 minutes. Items are updated.

openhab.log with rules files listed:

2022-11-14 22:10:52.196 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'zeva.rules'
2022-11-14 22:10:55.166 [ERROR] [internal.handler.ScriptActionHandler] - Script execution of rule with UID 'zeva-3' failed: Script interpreter couldn't be obtained in zeva
2022-11-14 22:11:02.998 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'shed.rules'
2022-11-14 22:19:33.697 [INFO ] [enhab.core.model.script.Modbus.01.04] - Modbus error logged to file: Invalid CRC at 8100
2022-11-14 22:19:58.001 [ERROR] [xt.ide.server.concurrent.ReadRequest] - Error during request: 
java.lang.RuntimeException: Cannot create a resource for 'java:/Objects/org.openhab.core.items.GenericItem'; a registered resource factory is needed
	at org.eclipse.xtext.resource.XtextResourceSet.getResource(XtextResourceSet.java:263) ~[?:?]
	at org.eclipse.xtext.ide.server.ProjectManager.getResource(ProjectManager.java:169) ~[?:?]
	at org.eclipse.xtext.ide.server.WorkspaceManager.doRead(WorkspaceManager.java:436) ~[?:?]
	at org.eclipse.xtext.ide.server.findReferences.WorkspaceResourceAccess.readOnly(WorkspaceResourceAccess.java:36) ~[?:?]
	at org.eclipse.xtext.ide.server.symbol.DocumentSymbolService.doRead(DocumentSymbolService.java:332) ~[?:?]
	at org.eclipse.xtext.ide.server.symbol.DocumentSymbolService.getDefinitions(DocumentSymbolService.java:112) ~[?:?]
	at org.eclipse.xtext.ide.server.symbol.DocumentSymbolService.getDefinitions(DocumentSymbolService.java:99) ~[?:?]
	at org.eclipse.xtext.ide.server.LanguageServerImpl.lambda$definition$25(LanguageServerImpl.java:607) ~[?:?]
	at org.eclipse.xtext.ide.server.WorkspaceManager.doRead(WorkspaceManager.java:438) ~[?:?]
	at org.eclipse.xtext.ide.server.LanguageServerImpl.definition(LanguageServerImpl.java:606) ~[?:?]
	at org.eclipse.xtext.ide.server.LanguageServerImpl.definition(LanguageServerImpl.java:594) ~[?:?]
	at org.eclipse.xtext.ide.server.LanguageServerImpl.lambda$definition$24(LanguageServerImpl.java:585) ~[?:?]
	at org.eclipse.xtext.ide.server.concurrent.ReadRequest.lambda$doRun$0(ReadRequest.java:66) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:829) [?:?]
2022-11-14 22:19:58.189 [ERROR] [xt.ide.server.concurrent.ReadRequest] - Error during request: 
java.lang.RuntimeException: Cannot create a resource for 'java:/Objects/org.openhab.core.library.types.DecimalType'; a registered resource factory is needed
	at org.eclipse.xtext.resource.XtextResourceSet.getResource(XtextResourceSet.java:263) ~[?:?]
	at org.eclipse.xtext.ide.server.ProjectManager.getResource(ProjectManager.java:169) ~[?:?]
	at org.eclipse.xtext.ide.server.WorkspaceManager.doRead(WorkspaceManager.java:436) ~[?:?]
	at org.eclipse.xtext.ide.server.findReferences.WorkspaceResourceAccess.readOnly(WorkspaceResourceAccess.java:36) ~[?:?]
	at org.eclipse.xtext.ide.server.symbol.DocumentSymbolService.doRead(DocumentSymbolService.java:332) ~[?:?]
	at org.eclipse.xtext.ide.server.symbol.DocumentSymbolService.getDefinitions(DocumentSymbolService.java:112) ~[?:?]
	at org.eclipse.xtext.ide.server.symbol.DocumentSymbolService.getDefinitions(DocumentSymbolService.java:99) ~[?:?]
	at org.eclipse.xtext.ide.server.LanguageServerImpl.lambda$definition$25(LanguageServerImpl.java:607) ~[?:?]
	at org.eclipse.xtext.ide.server.WorkspaceManager.doRead(WorkspaceManager.java:438) ~[?:?]
	at org.eclipse.xtext.ide.server.LanguageServerImpl.definition(LanguageServerImpl.java:606) ~[?:?]
	at org.eclipse.xtext.ide.server.LanguageServerImpl.definition(LanguageServerImpl.java:594) ~[?:?]
	at org.eclipse.xtext.ide.server.LanguageServerImpl.lambda$definition$24(LanguageServerImpl.java:585) ~[?:?]
	at org.eclipse.xtext.ide.server.concurrent.ReadRequest.lambda$doRun$0(ReadRequest.java:66) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:829) [?:?]
2022-11-14 22:21:14.328 [INFO ] [enhab.core.model.script.Modbus.01.04] - Modbus error logged to file: Invalid CRC at 8100
2022-11-14 22:27:06.539 [INFO ] [enhab.core.model.script.Modbus.01.04] - Modbus error logged to file: Invalid CRC at 8100
2022-11-14 22:30:48.161 [INFO ] [enhab.core.model.script.Modbus.01.04] - Modbus error logged to file: DHCP OK
2022-11-14 22:33:41.316 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rf433rx.rules'
2022-11-14 22:49:05.012 [INFO ] [enhab.core.model.script.Modbus.01.04] - Modbus error logged to file: Invalid CRC at 8100
2022-11-14 22:57:38.286 [INFO ] [enhab.core.model.script.Modbus.01.04] - Modbus error logged to file: Invalid CRC at 8100
2022-11-14 23:59:00.072 [INFO ] [enhab.core.model.script.Modbus.05.01] - Minutes w/o grid...: 120
2022-11-15 00:01:09.260 [INFO ] [nhab.core.model.script.spp_bms.01.00] - Midnight cron resets...
2022-11-15 00:50:35.051 [INFO ] [nhab.core.model.script.RF433TX.01.01] - UNO_RF433TX has rebooted
2022-11-15 00:50:35.111 [INFO ] [nhab.core.model.script.RF433TX.01.02] - TX433 error logged to file
2022-11-15 00:50:35.116 [INFO ] [nhab.core.model.script.RF433TX.01.01] - UNO_RF433TX has rebooted
2022-11-15 00:50:35.147 [INFO ] [nhab.core.model.script.RF433TX.01.02] - TX433 error logged to file
2022-11-15 01:20:12.978 [INFO ] [.myenergi.internal.MyEnergiApiClient] - Re-initializing Api connection after exception caught
java.util.concurrent.ExecutionException: java.io.EOFException: HttpConnectionOverHTTP@1a9ae67::DecryptedEndPoint@47c285{l=/192.168.1.68:33090,r=s18.myenergi.net/52.30.172.43:443,OPEN,fill=-,flush=-,to=30362/0}
	at org.eclipse.jetty.client.util.FutureResponseListener.getResult(FutureResponseListener.java:118) ~[?:?]
	at org.eclipse.jetty.client.util.FutureResponseListener.get(FutureResponseListener.java:101) ~[?:?]
	at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:730) ~[?:?]
	at org.openhab.binding.myenergi.internal.MyEnergiApiClient.executeApiCallHttpClient(MyEnergiApiClient.java:367) ~[?:?]
	at org.openhab.binding.myenergi.internal.MyEnergiApiClient.executeApiCall(MyEnergiApiClient.java:338) ~[?:?]
	at org.openhab.binding.myenergi.internal.MyEnergiApiClient.updateZappiSummary(MyEnergiApiClient.java:171) ~[?:?]
	at org.openhab.binding.myenergi.internal.handler.MyEnergiZappiHandler.refreshMeasurements(MyEnergiZappiHandler.java:119) ~[?:?]
	at org.openhab.binding.myenergi.internal.handler.MyEnergiBaseDeviceHandler.lambda$1(MyEnergiBaseDeviceHandler.java:92) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.io.EOFException: HttpConnectionOverHTTP@1a9ae67::DecryptedEndPoint@47c285{l=/192.168.1.68:33090,r=s18.myenergi.net/52.30.172.43:443,OPEN,fill=-,flush=-,to=30362/0}
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.earlyEOF(HttpReceiverOverHTTP.java:385) ~[?:?]
	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1620) ~[?:?]
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.shutdown(HttpReceiverOverHTTP.java:269) ~[?:?]
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:185) ~[?:?]
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:80) ~[?:?]
	at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:131) ~[?:?]
	at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:172) ~[?:?]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) ~[?:?]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) ~[?:?]
	at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:555) ~[?:?]
	at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:410) ~[?:?]
	at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:164) ~[?:?]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) ~[?:?]
	at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) ~[?:?]
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409) ~[?:?]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) ~[?:?]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) ~[?:?]
	... 1 more
2022-11-15 01:20:16.035 [INFO ] [.myenergi.internal.MyEnergiApiClient] - Re-initializing Api connection after code: 0, reason: 
2022-11-15 01:20:19.051 [INFO ] [.myenergi.internal.MyEnergiApiClient] - Re-initializing Api connection after code: 0, reason: 
2022-11-15 01:20:22.068 [WARN ] [al.handler.MyEnergiBaseDeviceHandler] - Exception from API - myenergi:zappi:api:16181119
org.openhab.binding.myenergi.internal.exception.ApiException: Http error after several attemps: 0 - 
	at org.openhab.binding.myenergi.internal.MyEnergiApiClient.executeApiCallHttpClient(MyEnergiApiClient.java:400) ~[?:?]
	at org.openhab.binding.myenergi.internal.MyEnergiApiClient.executeApiCall(MyEnergiApiClient.java:338) ~[?:?]
	at org.openhab.binding.myenergi.internal.MyEnergiApiClient.updateZappiSummary(MyEnergiApiClient.java:171) ~[?:?]
	at org.openhab.binding.myenergi.internal.handler.MyEnergiZappiHandler.refreshMeasurements(MyEnergiZappiHandler.java:119) ~[?:?]
	at org.openhab.binding.myenergi.internal.handler.MyEnergiBaseDeviceHandler.lambda$1(MyEnergiBaseDeviceHandler.java:92) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:829) [?:?]
2022-11-15 02:11:15.867 [INFO ] [nhab.core.model.script.spp_bms.07.01] - ProfitLoss rule triggered...
2022-11-15 02:11:15.877 [INFO ] [nhab.core.model.script.spp_bms.07.02] - ProfitLossTotal yesterday.0.: -154.86
2022-11-15 02:11:15.882 [INFO ] [nhab.core.model.script.spp_bms.07.03] - ProfitLossTotal yesterday.1.: -154.86
2022-11-15 02:11:15.885 [INFO ] [nhab.core.model.script.spp_bms.07.04] - ProfitLoss updated (night)..: 0.09
2022-11-15 02:11:15.887 [INFO ] [nhab.core.model.script.spp_bms.07.05] - ProfitLoss corrections......: 0.00
2022-11-15 02:11:15.889 [INFO ] [nhab.core.model.script.spp_bms.07.06] - ProfitLossTotal new today...: -154.77
2022-11-15 02:11:15.891 [ERROR] [internal.handler.ScriptActionHandler] - Script execution of rule with UID 'sppro_bms-5' failed: Could not cast UNDEF to org.openhab.core.library.types.DecimalType; line 214, column 42, length 31 in sppro_bms
2022-11-15 04:15:00.071 [INFO ] [openhab.core.model.script.Shed.10.01] - Cron: is boost required?
2022-11-15 04:15:00.075 [INFO ] [openhab.core.model.script.Shed.10.02] - ... Shed_HWS_Boost_Allowed = NULL
2022-11-15 04:17:52.711 [INFO ] [enhab.core.model.script.Modbus.01.04] - Modbus error logged to file: Response Timed Out at 8100
2022-11-15 06:05:00.589 [INFO ] [enhab.core.model.script.Modbus.01.04] - Modbus error logged to file: Response Timed Out at 8000
2022-11-15 06:42:38.633 [ERROR] [xt.ide.server.concurrent.ReadRequest] - Error during request: 
java.lang.IndexOutOfBoundsException: Position [
  line = 193
  character = 79
] text was : /*
    20221015-1927 removed HWS rules; moved to shed.rules
    20181225-1420 copied rule file from v1 to v2

    all rules within that one .rules file can use these var or val
    val - short for "value", gets initialised with a value and the Rules DSL
          will prevent reassigning another value to that name
    var - short for "variable" , can remain uninitialised (will be null),
          can be assigned new values, and can be reassigned to another value
*/
val String logPrefix = "spp_bms."

// ----- 170614 MaxG: Timer for -> late arvo charge reduction
var Timer timerLateArvoChargeDecrement = null


// ------------------------------------------------------------------------
// ----- Rules related to SP PRO, BMS, etc.
// ------------------------------------------------------------------------

rule "SPPRO-BMS system started"
    when
        System started
    then
        logInfo(logPrefix + "00.00", "System start or rule file reload for {}", logPrefix)
end

[Info  - 10:11:10 am] Connection to server got closed. Server will restart.
[Error - 10:11:10 am] Connection to server is erroring. Shutting down server.
[Error - 10:11:10 am] Connection to server is erroring. Shutting down server.

I am pretty much clueless on where and what to look for.

This is a stock standard openHABian.
No binding was added in the last three days.
Added items and modified these in UI.

I am not running out of space:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        15G  5.8G  8.1G  42% /
devtmpfs        1.9G     0  1.9G   0% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           778M  1.6M  777M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sda1       253M   50M  203M  20% /boot
/dev/zram1      721M  213M  456M  32% /opt/zram/zram1
overlay1        721M  213M  456M  32% /var/lib/openhab/persistence
/dev/zram2      323M   15M  284M   5% /opt/zram/zram2
overlay2        323M   15M  284M   5% /var/lib/influxdb
/dev/zram3      974M  636M  271M  71% /opt/zram/zram3
overlay3        974M  636M  271M  71% /var/log
tmpfs           389M     0  389M   0% /run/user/1000

Any hints appreciated.

rlkoshak · November 15, 2022, 3:39pm

Is events.log still going or are both log files stopped?

openhab.log is showing lots of strange errors.

Do you know what’s wrong with the rule zeva-3?

Do you typically see a CRC error from Modbus? That shows that the message received from modbus isn’t as expected. CRC is typically a few bytes at the end of the message that contains the sum of all the ones in the message itself. If the CRC fails, it means one or three bits in the message got flipped.

I’ve never seen the “registered resource factory is needed” error before. But that points at something really wrong is going on in the core. The stack trace is pointing to Xtext so it’s coming from parsing a .items file, but I don’t think the problem is with the parsing but with actually creating the Item itself.

The error from MyEnergyApi indicates that the binding reached out to the service and got an empty response or the connection was unexpected disconnected. That error occurs a couple times and then the binding throws and error saying it’s giving up.

There’s a run of the mill exception from the rule sppro_bms-5.

Then we have an error I’m guessing comes from the Language Server Protocol (LSP) which is what allows VSCode to do the syntax checking of Rules DSL as you type.

So you’ve got bits being flipped on your modbus messages, an inexplicable inability to create new Items sometimes, and an error from the LSP before logging just stops.

I don’t have any experience with modbus but when I start seeing CRC checks failing in other contexts it points to a wire that needs to be reset or there is a hardware failure.

The rest is a mystery but if there is a hardware problem somewhere random inexplicable behavior is not unexpected.

Since modbus is the first to complain, what happens if you unplug it and/or disable the Things/Binding?

Max_G · November 16, 2022, 10:56am

Thanks for even looking at this.

Firstly I was never a fan of SDs or pen drives.
I am currently investigating the hardware.
I have a openhab-cli backup, which I assume I can restore if need be.
If the storage device is the problem (or not) I will rebuild with openHABian but on an SSD (like all my rPis).

To answer your questions:

both logs stopped; its not a frontail issue, as logs are not written for frontail to display.
zeva-3 worked as did the others… but all of sudden it was complaining about a bunch of rules.
the modbus CRCs are not happening at the OH side, but are picked up by the controller who then reports that error via a MQTT msg,
I could trigger the resource factory issue when holding the shift key in vsCode for a bit longer than usual. This is an issue I had in OH2 as well. Weird at best.
I disabled, as in removed the myenergi binding earlier to rule out it being the cause.
bms-5 should not be an issues; at least it wasn’t days before.
LSP was flaky all along; I had to restart vsCode to get the value checking/hover-over back.

… I think this is a hardware issue, but am still looking in to it (haven’t much time yet).

(But will ultimately report back here of any findings/actions.)

rossko57 · November 16, 2022, 11:19am

I think you will find other threads about this becoming a resource hog in some circumstances (such as when doing lots of edits in a conversion).

mstormi · November 17, 2022, 7:04am

Before you do, read the openHABian docs again and note that running openHABian on SSD is not supported. Check out SD mirroring instead.

Max_G · November 18, 2022, 8:40am

Thank you; yes, I have done so before I built it the first time, and before I built it again a day ago.

I understand the support conundrum; it has to be ideally a single set-up.

I also have to consider general experience with SD cards; and their failings, which have caused endless grief for most using them.

A day later…

I installed openHABian on the ‘old’ rPi4, but using an SSD; I could not see the device on the network.
I tried to install it on a new rPi4 with SSD; same result.
Tried again, and came beck the next morning and could reach the rPi over ssh.

I set-up OH3, and restored the backup form the previous set-up.
I got heaps of error messages, mainly related to grafana/influx, which I had before, but not any more.
I could not resolve the issues; not even after I installed the influx/grafana combo from the menu.

I also installed openHABian on the ‘old’’ rPi4 but on an SD card; however, after three hours it was still not visible on the network.
I am in the process of re-imaging the SD card and use it on the new rPi4.

If that fails I will do a normal apt install, as I seem to have no success with the openHABian image.

[update]
Alright, interestingly enough, the image on the SD card and old rPi4 seem to function.

Probably shot myself in the foot by trying to connect to openhabian@openhabian; while I could only connect to openhabian@ip-address. However, this time the rPi4 was found with nmap looking for a rPi4 on the network, while that wasn’t the case with the other installations.

Do I have a monitor I could connect to? Yes. but no cable that fits the small HDMI port of the rPi4. Hence, I was flying blind, but never needed a monitor on a rPi, as my images worked and SSH was enabled via file before sticking any storage device into the rPi.

I went through the initial set-up (password, timezone, location).

But, before I restore the backup, a question:

should I install grafana/influx before restoring the backup?
(Seems logical when using the same passwords.)

rlkoshak · November 18, 2022, 2:11pm

To be fair, that’s why ZRAM is a default part of openHABian now. Most of the writes that OH makes are made in RAM to avoid SD card wear out. This greatly mitigates the problems with SD card wear out and it even slightly addresses problems caused by power loss since the machine is writing to the SD card less frequently so it’s less likely that it happens to be writing when power is lost (and risking a catastrophic corruption as a result).

There is actually a documented problem with openHABian if you plug in a monitor and keyboard during that first boot and initialization covered in the docs. So that’s to be expected that you wouldn’t have a monitor attached.

I’m not sure it matters that much either way.

mstormi · November 18, 2022, 5:45pm

Monitor w/o keyboard should do. But you don’t need it.
If you thoroughly read the docs, it’ll tell you to use the IP address to access the log during installation.

Max_G · November 18, 2022, 11:48pm

Well, when I installed a new image and restored my backup, it created errors galore; all related to cannot store data, etc. And I found no way to disable these. I then installed installed influx/grafana via the openhabian-config menu option… the errors continued.

Despite the automated and streamlined openHABian process, it still takes a lot of time to get a new system going… hence, my question.

I have taken an rsync backup of this virgin install, and am creating a SD mirror as we speak; and then install influx/grafana; then restore my backup. Logically this should work, but I do not know the inner workings of OH3 to say for sure.

rlkoshak · November 19, 2022, 12:00am

Uninstall or disable the InfluxDB add-on until you are ready for it, or create/modify the influxdb.persist file to not save anything. But whether you install it first and then configure OH to use it, or install it last and ignore the errors or configure OH to not even try to save stuff doesn’t really matter.

Your credentials are likely not the same to access InfluxDB, particularly if you didn’t use openHABian to install it on your old system. Also, I believe openHABian installs InfluxDB v2 whereas OH 2 only supported InfluxDB v1 so the config might be different there as well.

Max_G · November 19, 2022, 12:23am

Thanks…

I used the openHABian install on the previous install and this install.

On previous:
I installed openHABian resulting in 3.3.0
I then installed influx/grafana but never used it or setup persistence with it. (Siting there doing nothing).
I backed up openhab via openhab-cli. (a few hours before logging stopped; (this post)

On new:
I installed openHABian resulting in 3.3.0
Did basic UI (start-up) config (username, password, location) and left it there.
Did a rsync backup to a NAS
Just finished the SD card mirror
Now setting up Amanda…

Yes, I did change the credentials on the first rebuild/restore; did another rebuild/restore with old credentials, and still got errors… but these were installs straight to SSD.

This latest ‘new’ has an SD card, and is set-up entirely by the book, as in openHABian documentation… except, it says do not install influx.grafana.

ATM I would install it to get my OH3 back w/o errors (as it seemingly barks at me for not having influx/grafana).

Why influx/grafana?

well, I like its look (I am using teslamate for my Tesla M3LR).
Ignorance, as I felt grafana graphs look better than OH’s, w/o ever having investigated what OH graphs look like. I have only seen the ‘analyse’ in the item screen of the UI (and you posted a multi-graph in response to my 'graphing post, which didn’t grab my fancy).

I am not yet familiar with OH3, despite having spent 50 hours migrating from OH2; that is groups, items, bindings, things in the UI, and rules as text.
“Familiar”, as in do not understand graphing yet, or the yaml business for the fancy widgets.

Or (actually and), I still have an old early OH2 mindset, w/o using the new stuff OH2 introduced post OH1.

Simply seeing some of the new things on the forum instilled the trust that I can migrate to OH3, and adopt new functionality after the basic migration has been completed.

Max_G · November 19, 2022, 2:50am

Thank you all for your support…

I have installed the influx/grafana combo

Then stopped openhab: sudo systemctl stop openhab.service

The restored my backup: sudo openhab-cli restore 20221115-2155_BUP_full.zip

Then started openhab: sudo systemctl start openhab.service

All came up perfectly; no errors…

The only obstacle was an ever loading UI, because I didn’t realise I had to login again