It is exactly that content. I change now the org.ops4j.pax.logging.cfg to only one line and it is working.
1 Like
sihui
January 4, 2021, 4:27pm
233
Peter_Antoni:
and it is working.
Good, now you are on the openHAB3 track
2 Likes
StefanMUC
January 13, 2021, 8:26pm
234
HaKuNa:
In RC1 I have multiple entries “enabled CORS for REST API” in the openhab.log during startup/stop of openhab. I know, these are only INFO messages, but are they related to any binding/thing or do they appear also multiple times in a clean install ?
I’m on OH3 (release) and these messages appear not only 33 times as in your log, but in mine I have 64 entries of this. So yes this happens in a clean install too! It’s a bit anoying seing that - any news on this?
thewiep
January 23, 2021, 9:02am
235
This post has the solution to this problem, it fixed it for me:
OK. Now I found a solution by my own.
I did the following: (just if somebody gets someday the same issue)
Stopped openhab sevice
openhab-cli clean-cache
I edited /var/lib/openhab/automation_rules.json an removed everything except the {}. Everything I tried during the last days was there, as well al some old rules I made with OH 2.5 and its Next-Gen Rule Engine.
Restarted Openhab
Voila, it works, now I am able to create rules in OH3 as expected.
Seems that this is / was a migration issue in …
thewiep
January 23, 2021, 9:03am
236
this post also fixes this issue for me:
OK. Now I found a solution by my own.
I did the following: (just if somebody gets someday the same issue)
Stopped openhab sevice
openhab-cli clean-cache
I edited /var/lib/openhab/automation_rules.json an removed everything except the {}. Everything I tried during the last days was there, as well al some old rules I made with OH 2.5 and its Next-Gen Rule Engine.
Restarted Openhab
Voila, it works, now I am able to create rules in OH3 as expected.
Seems that this is / was a migration issue in …
