-
Notifications
You must be signed in to change notification settings - Fork 33
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
microceph spams logs with debug messages #239
Comments
Folks, we need to resolve the issue, but not only to document it. The real issue is that there is no way to configure microcephd's log level yet. And this is big problem for instances running on IoT devices with eMMC storage. Syslog is spammed with "microceph.daemon" messages which are not needed normal operation. Asn as result eMMC storage wears out too fast, This line of code enforces debug level by default . However, snap does not support configuration hook, so there is no way to change microcephd parameters via snap commands. |
Did this fix arrived to snap reef/stable: 18.2.0+snap450240f5dd 2024-04-09 (979) ?
My environment:
P.S. |
Thanks for reporting this @tregubovav-dev will take a look at this. |
just to get this right - You used |
I will provide additional details in couple hours. |
Steps to reproducePlease run script below:
review log outputs and see that microcephd continues generate level=debug messages to the system log independently of log level set by sudo microceph log set level $LEVEL command. My environment information:I have 7 Raspberry Pi 4 SBC that host microceph and LXD clusters. $ lsb_release -a $ sudo microceph --version $ sudo snap info microceph $ sudo lxd --version $ sudo snap info lxd $ sudo lshw -short |
My concern is to this test:
It does verify that log level configuration is changed, but it does not validate that the log configuration change is applied to the log producer. Script provided in my previous comment can be adjusted for validation logs after log level changes. |
Hello, just found about this bug report and I guess the root cause for the daemon's log debug messages lies in https://github.com/canonical/microceph/blob/main/microceph/cmd/microcephd/main.go#L107. If you don't proactively set As |
I installed microceph recently and found it to be quite noisy in the logs due to debug mode be enabled by default. |
In order to reduce log noise by default Fixes canonical#239 Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
I'm deploying LXD+microceph clusters on top of Raspberry PI instances.
I found that microceph spams syslog with debug messages in addition to tons of debug messages in /var/snap/microceph/common/logs as described in issue #163.
How to make microceph's daemons log level configurable?
The text was updated successfully, but these errors were encountered: