Wouter Born

Does it work better with these changes https://github.com/wborn/openhab-distro/commit/d022c6ed0445e5223fe9f561d9bfaf1a5e66f661?

We could also simulate the weather in Berlin until we find another good replacement. I.e. similar to what is done for the room temperatures: https://github.com/openhab/openhab-distro/blob/7188264c4130a0b516a7c0dd7292a80f7982d37b/features/distro-resources/src/main/resources/rules/demo.rules#L91-L99

Based on the timestamps it looks like the log4j2.xml file is always modified on startup. So maybe it is sometimes written/read at the same time causing this issue?

Karaf always updates this logger on startup: https://github.com/openhab/openhab-distro/blob/79cc7ca7f78c7a902827afda2cdb4754f8204953/distributions/openhab/src/main/resources/userdata/etc/log4j2.xml#L124-L126 which probably causes the file to be modified.

Seems to make sense to me and it was already discussed before, see https://github.com/openhab/openhab-linuxpkg/pull/81#issuecomment-332152160.

> The fourth point sounds very interesting, but doesn't really fit into the scheme. It seems to be an option, if you are able to set it in some lines...

After a very very brief look I don't think Pax will pickup such logging configurations so it will probably not be visible/editable from the console. You'll be directly configuring Log4j2...

> You can add a log4j v2 XML-based configuration file by adding this line to the above file org.ops4j.pax.logging.log4j2.config.file=${karaf.etc}/log4j2.xml There is an issue about log:get and log:set commands not properly...

I've made local build with OH 2.2.0 and Karaf 4.2.0.M1 and tested the implementation of using a log4j2.xml: * Using a XML configuration works pretty well, KARAF-5354 is also solved...

There's an [older revision of that wiki](https://github.com/openhab/openhab-distro/wiki/Breaking-Changes-in-openHAB-3/139901f0ef7ee8b5b7dd480204ddf5069f030f50) that still shows them. Maybe @kaikreuzer forgot to add these changes back after regenerating the release notes?