Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openHAB 4.0.4: Changing loglevel via Binding Settings empties org.ops4j.pax.logging.cfg #1618

Open
wzbfyb opened this issue Dec 18, 2023 · 3 comments
Labels
awaiting feedback bug An unexpected problem or unintended behavior stale As soon as a PR is marked stale, it can be removed 6 months later.

Comments

@wzbfyb
Copy link

wzbfyb commented Dec 18, 2023

Hi,

I noticed that whenever I change a log-level via binding settings (GUI), org.ops4j.pax.logging.cfg suddenly is empty and logging stops. Populating the file again will resume logging. This does not happen if I set loglevel via console.

Expected Behavior

If I change the loglevel for a binding via GUI, I expect logging to still work :)

Current Behavior

Changing Loglevel via GUI, results in an empty org.ops4j.pax.logging.cfg which in turn causes logging to stop.
grafik

Possible Solution

only change settings via console, or fix UI

Steps to Reproduce (for Bugs)

  1. Go To Settings, Bindigs
  2. go to settings of a Binding (tried with zigbee and tradfri)
  3. change loglevel there, Save

Your Environment

  • Version used: openHAB 4.0.4
  • Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...): Docker
  • Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...): Debian on Intel
@mherwege mherwege added the bug An unexpected problem or unintended behavior label Dec 18, 2023
@wborn
Copy link
Member

wborn commented Dec 23, 2023

Changing Loglevel via GUI, results in an empty org.ops4j.pax.logging.cfg which in turn causes logging to stop.

  1. Go To Settings, Bindigs
  2. go to settings of a Binding (tried with zigbee and tradfri)
  3. change loglevel there, Save

I cannot reproduce the issue using these steps.

@mherwege
Copy link
Contributor

I was not able to reproduce either.

Copy link

stale bot commented Feb 22, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale As soon as a PR is marked stale, it can be removed 6 months later. label Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting feedback bug An unexpected problem or unintended behavior stale As soon as a PR is marked stale, it can be removed 6 months later.
Projects
None yet
Development

No branches or pull requests

3 participants