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.

Sign up for GitHub

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

Jump to bottom

Log spam in journald #292

Closed
cpaelzer opened this issue Jan 5, 2024 · 3 comments
Closed

Log spam in journald #292

cpaelzer opened this issue Jan 5, 2024 · 3 comments

Comments

@cpaelzer
Copy link

cpaelzer commented Jan 5, 2024

Hi,
Ubuntu got this reported as a bug in 2046470.
A check of the history showed me that this happened

  1. back in the initial import this was a debug message
  2. It got later converted to a log message and got INFO level (no more debug) but was unseen
  3. it was moved around when introducing sockets, still unseen
  4. recently not only foreground but also log_journal is auto-set

Combined that leads to Ubuntu, Debian and probably all other users of the recent version with change number 4 to get continuous journal entries like this every 10 seconds:

Jan 05 12:30:55 n-vm irqbalance[770]: 
                                      
                                      
                                      -----------------------------------------------------------------------------
Jan 05 12:31:05 n-vm irqbalance[770]: 
                                      
                                      
                                      -----------------------------------------------------------------------------
Jan 05 12:31:15 n-vm irqbalance[770]: 
                                      
                                      
                                      -----------------------------------------------------------------------------
Jan 05 12:31:25 n-vm irqbalance[770]: 
                                      
                                      
                                      -----------------------------------------------------------------------------
Jan 05 12:31:35 n-vm irqbalance[770]: 
                                      
                                      
                                      -----------------------------------------------------------------------------
Jan 05 12:31:45 n-vm irqbalance[770]: 
                                      
                                      
                                      -----------------------------------------------------------------------------

It grabs a lot of space and it does not say what it is about.
That made sense back then when added as a message for the developer, but today is just annoying in the log.

I'd suggest to make this only shown in log level debug and to reduce the space it grabs as well as making it a bit more descriptive.
cpaelzer added a commit to cpaelzer/irqbalance that referenced this issue Jan 5, 2024
@cpaelzer
Stop log spam due to debug message from scan
a27df6e 
Currently systems encounter log spam every 10 seconds due to a
message meant for debugging now being forwarded to journald.
Users get three empty lines followed by 78 "-" without any further
info what this is about.

Due to its original debug-only purpose the message also grabs
a lot of screen-estate. So while touching it anyway let us also make
it a bit less agressive (no three lead line breaks, less width),
now it is like:
  ----- Enter: scan -----

Fixes: Irqbalance#292

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
@cpaelzer cpaelzer mentioned this issue Jan 5, 2024
Closed
@paride
Copy link
Contributor

paride commented Jan 9, 2024 •
edited

Hi @cpaelzer, isn't this the same of of #288 / #281, hopefully fixed by f3282f4 ?

@cpaelzer
Copy link
Author

cpaelzer commented Jan 9, 2024

You are right, thanks for going through closed issues. It wasn't in the context of the bad line so I missed it. I'll give this a try and if good close this and the PR.

@cpaelzer
Copy link
Author

Confirmed, better fixing twice than not at all :-)
But still closing this duplicate report - thanks

@mascheiber mascheiber mentioned this issue Feb 29, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Stop log spam due to debug message from scan cpaelzer/irqbalance
2 participants
@paride @cpaelzer