Someone else reported something similar and it was resolved by touching the org.ops4j.pax.logging.cfg file…