Closed itn3rd77 closed 1 year ago
I would claim that this is not at all specific to openHAB, but most likely exists in plain Karaf as well. Would be great if you could verify this assumption - if it is correct, a bug should be opened for Karaf.
I must admit that I have no clue what to do - 0,000 knowledge with Karaf ...
Could you retest this with a recent 2.4.0-SNAPSHOT build (# 1362 or newer) @itn3rd77? Karaf has been upgraded from 4.1.5 to 4.2.1 so many bugs were fixed. See also the Karaf Release Notes.
Hi,
I want to bring the following exceptions to your attention which I would consider a bug or maybe better a misbehavior.
Ok here is what I have done and observed. I wanted to change the logging for the audit.log, events.log and openhab.log from
SizeBasedTriggeringPolicy
toTimeBasedTriggeringPolicy
. I have stopped openHAB and replaced the fileuserdata/etc/org.ops4j.pax.logging.cfg
with my modified file (see attached file: org.ops4j.pax.logging.cfg.new.txt). After replacing the original file with the modified file I startet openHAB and did get a bunch of exceptions (see attached file: openhab.log):After restarting openHAB once again openHAB comes up fine without any exception. I suspect the old config saved at
userdata/config/org/ops4j/pax/logging.config
(see attached file: config_org_ops4j_pax_logging.config.txt) to be responsible for the exceptions and something get mixed up. But that's just a guess. After restarting openHAB the fileuserdata/config/org/ops4j/pax/logging.config
is updated with the new values fromuserdata/etc/org.ops4j.pax.logging.cfg
I haven't tested if this is true for other files as well besides logging.
Attachments