Arch Linux

alex404

Member

Registered: 2009-12-03

Posts: 51

MPD spamming journald with opened/closed messages

Hi there,

I've got a weird problem with MPD. Although it runs apparently flawlessly, I recently noticed that any command to mpd causes it to generate a sequence of messages to my journald. If I run

journalctl -xn I see

I see

Dec 03 13:14:21 finalboss mpd[455]: client: [153] closed
Dec 03 13:14:21 finalboss mpd[455]: client: [152] closed
Dec 03 13:14:21 finalboss mpd[455]: client: [154] opened from [::1]:48114
Dec 03 13:14:21 finalboss mpd[455]: client: [154] closed
Dec 03 13:14:21 finalboss mpd[455]: client: [155] opened from [::1]:48115
Dec 03 13:14:21 finalboss mpd[455]: client: [155] closed
Dec 03 13:14:21 finalboss mpd[455]: client: [156] opened from [::1]:48116
Dec 03 13:14:21 finalboss mpd[455]: client: [156] closed
Dec 03 13:14:21 finalboss mpd[455]: client: [157] opened from [::1]:48117

Three of these messages will typically be generated per command. This meant that when I was running my xmobar MPD monitor, it was generating journald spam like crazy. Again, there doesn't seem to be any problems performance wise, but it certainly makes it hard to use journalctl to diagnose other problems.

I'm running mpd using the user service, and pulseaudio.

Cheers,

- Sacha

Raynman

Member

Registered: 2011-10-22

Posts: 1,539

Re: MPD spamming journald with opened/closed messages

`man mpd.conf` describes three choices for log_level. This output seems to correspond to "secure" and I get the same thing without specifying a log_level in mpd.conf, even though the default should be the less verbose "default". Explicitly setting log_level to default seems to work.

alex404

Member

Registered: 2009-12-03

Posts: 51

Re: MPD spamming journald with opened/closed messages

Great, that fixed it indeed. However, are these opened/closed calls with incrementing port numbers not unusual, or is that pretty standard for a server/client program like mpd?