myMPD "updated database" 7 times in 2 minutes / suppress notification?

[iconoclasthero]

I'm beginning to suspect this is normal behavior:

13:48:11 NOTICE   mympdapi  "default": Update database id: 0
13:48:29 NOTICE   mympdapi  "default": Update database id: 3480
13:48:29 NOTICE   mympdapi  "default": Update database id: 0
13:48:50 NOTICE   mympdapi  "default": Update database id: 3481
13:48:50 NOTICE   mympdapi  "default": Update database id: 0
13:49:29 NOTICE   mympdapi  "default": Update database id: 3482
13:49:29 NOTICE   mympdapi  "default": Update database id: 0
13:49:48 NOTICE   mympdapi  "default": Update database id: 3483
13:49:48 NOTICE   mympdapi  "default": Update database id: 0
13:50:02 NOTICE   mympdapi  "default": Update database id: 3484
13:50:02 NOTICE   mympdapi  "default": Update database id: 0
13:51:14 NOTICE   mympdapi  "default": Update database id: 3485
13:51:14 NOTICE   mympdapi  "default": Update database id: 0
13:52:30 NOTICE   mympdapi  "default": Update database id: 3486
13:52:30 NOTICE   mympdapi  "default": Update database id: 0
13:54:29 NOTICE   mympdapi  "default": Update database id: 3487
13:54:29 NOTICE   mympdapi  "default": Update database id: 0

Can this be suppressed in the log so that it's not all over /var/log/syslog and can the corresponding notices on the webclient be silenced?

[jcorporation]

This events are emitted from MPD.

You can toggle notification options in the settings.

[iconoclasthero]

Thank you, I will look into that.

I do not consider this an answer as mpd isn't writing this to the syslog and mpd does not have a web server to display those notifications. Modifying the properties of the server to change unwanted output from the client is not acceptable as it will change the way other clients or the service perform.

[iconoclasthero]

I looked through my /etc/mpd.conf, searching for first notification and then not and I don't see this setting. Would you please let me know what—exactly—am I looking for in the mpd.conf? Maybe it is something I can just turn off, but mpd isn't scanning my library every 20 seconds and those notifications in myMPD correspond to events like changing the song as well as DB changes so I'm really not sure I even believe this is something that's coming from mpd at this point, i.e., w/o further evidence.

Thanks!

[iconoclasthero]

In looking at the mpMPD settings again, I found how to remove the web notifications which was half of what I was looking for.

I'm still interested in suppressing the syslog notifications or moving the notifications to a separate log aside from /var/log/syslog. I'm not the only person out there who doesn't like the practice of using syslog vs. a dedicated log for a service. Is there a setting somewhere to log to /var/log/mympd/mympd instead of syslog?

mpd has a config file at /etc/mpd.conf and a log file at /var/log/mpd/mpd.log. it makes sense to me to look there for the settings and log for anything that is designed to work alongside mpd. I'm also not even close to being unique when it comes to not wanting services to default writing all notifications to /var/syslog.

[jcorporation]

myMPD is relaying MPD events to the web clients. There is nothing to configure in MPD. Start MPD in verbose mode to see more details or try the mpc idle cli to see what MPD events are emitted.

[iconoclasthero]

How do I move logging from /var/log/syslog to /var/log/mympd/mympd.log or /var/log/mpd/mympd.log?
Neither mpd—which logs to a discrete log file at /var/log/mpd/mpd.log by default—nor myMPD are core system service that should be outputting to the syslog.

https://jcorporation.github.io/myMPD/configuration/logging

Thanks!

PS - I personally would appreciate if there were a search bar so I didn't have to https://www.google.com/search?q=logging+site%3Ahttps%3A%2F%2Fjcorporation.github.io%2FmyMPD%2F

[iconoclasthero]

How do I stop this with the transient systemd user? I chowned this once but this isn't a permanent solution... ``` 2024-03-31T00:10:51.883880-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.webp" 2024-03-31T00:10:51.884221-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.884284-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.jpg" 2024-03-31T00:10:51.884334-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.884379-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.jpeg" 2024-03-31T00:10:51.884423-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.884465-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.png" 2024-03-31T00:10:51.884531-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.884575-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.svg" 2024-03-31T00:10:51.884617-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.884658-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.avif" 2024-03-31T00:10:51.884699-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.884780-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.WEBP" 2024-03-31T00:10:51.884826-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.884867-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.JPG" 2024-03-31T00:10:51.884909-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.884966-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.JPEG" 2024-03-31T00:10:51.885010-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.885051-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.PNG" 2024-03-31T00:10:51.885092-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.885131-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.SVG" 2024-03-31T00:10:51.885172-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.885212-04:00 gigabyte mympd[19482]: ERROR webserver Error opening file ro "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.AVIF" 2024-03-31T00:10:51.885270-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied 2024-03-31T00:10:51.885315-04:00 gigabyte mympd[19482]: ERROR webserver Can not open file "/var/cache/mympd/covercache/365c184d131d9f893c65f9d8f38be7738cd2bbc7-0.jpg.MNb3EO" for write 2024-03-31T00:10:51.885359-04:00 gigabyte mympd[19482]: ERROR webserver Permission denied ```

…

On Mon, Apr 1, 2024 at 8:58 AM Jürgen Mang ***@***.***> wrote: myMPD is relaying MPD events to the web clients. There is nothing to configure in MPD. Start MPD in verbose mode to see more details or try the mpc idle cli to see what MPD events are emitted. — Reply to this email directly, view it on GitHub <#1250 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEC3GR5R4OEPRG3KWLO6S3Y3FKY7AVCNFSM6AAAAABFQS6RCGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNZSGYYDC> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jcorporation]

Permissions are managed by systemd. Deleting the directory and the symlink should create it with correct permissions after restart.

myMPD has no option to write logs to a file. It can log to syslog or to stdout.

You should investigate why this events occur and not trying to disable the logs/notifications for it.

[iconoclasthero]

Permissions are managed by systemd. Deleting the directory and the symlink should create it with correct permissions after restart.

I don't understand e.g., the use of the transient user or the need for it; as none of my other services are of a similar structure to myMPD. As such, my expectations for how to use such a service are apparently rather far apart from the controls of myMPD. For now, it may just be easier for me to turn that off (as I saw something to that effect in the config file or documentation) until I get a handle on what that's doing.

myMPD has no option to write logs to a file. It can log to syslog or to stdout.

Prompted me to learn how to fix this and complete a couple systemd services I'm running so they have unique log files as well: https://bsamuels.net/2014/08/30/redirecting-rsyslog-output.html

NB: I'm nowhere unique in this, e.g., the first two lines: "You know what sounds good right now? Blowing a few hours trying to figure out how to redirect a program’s rsyslog output to a different log file." and later: "All that "$service" noise takes up a lot of space in the syslog file, and it shares that space with pretty much every other program that uses the rsyslog daemon. If I want to see non-"$service" traffic, I’d have to use grep or something on the syslog file and I’m just too lazy for that kind of jazz." (Substitute for "$service" as appropriate.)

You should investigate why this events occur and not trying to disable the logs/notifications for it.

I agree which is why the log should have things that are worth investigating. I've already lowered the log level once and I'm still seeing a ton of noise...*

That said, these aren't things to investigate as you've said above: This is something that myMPD is outputting as a result of something from mpd AND despite mpd not actually outputting it, somehow the solution to this relies /etc/mpd.conf but I haven't spent the time to track down that wild goose.

At the end of the day, we just have very different ideas about how much of a system an application like myMPD should be allowed to control. I don't think it should have facilities to log notices to syslog and I don't think it should expect 80 and 443 as default open ports upon install and I'm beating my head against this trying to get it to fit into the way I run my system. (And I'm at an obvious and tremendous disadvantage since you know far, far more about this than I and everything about the application you developed.)

r MYMPD_API_COVERCACHE_CROP
2024-04-01T12:16:13.404205-04:00 gigabyte mympd[337393]: NOTICE   mpdworker Deleted 0 files from covercache
2024-04-01T12:16:13.404344-04:00 gigabyte mympd[337393]: NOTICE   mpdworker Stopping mpd_worker thread
2024-04-01T12:17:33.699952-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 10
2024-04-01T12:17:33.704361-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 0
2024-04-01T12:22:18.723992-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 11
2024-04-01T12:22:18.727975-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 0
2024-04-01T12:24:07.724008-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 12
2024-04-01T12:24:07.728470-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 0
2024-04-01T12:24:18.722203-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 13
2024-04-01T12:24:18.726451-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 0
2024-04-01T12:25:55.665509-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 14
2024-04-01T12:25:55.670426-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 0
2024-04-01T12:27:55.649502-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 15
2024-04-01T12:27:55.653838-04:00 gigabyte mympd[337393]: NOTICE   mympdapi  "default": Update database id: 0

You said that this is because of mpd, However gmpc, mpc, etc., don't spit this information out at me so I've literally never needed to worry about it for over a decade and am why am I spending time looking at it now as a result of installing myMPD?

I mean seriously, what is this trying to tell me that I've been missing out on for the last 15 years and why do I need to investigate it?

*wait, I just checked /var/lib/mympd/config/loglevel and it's still 5 despite changing that with mympd-config and applying and putting in my sudo password. I can't get mympd-config to do anything regardless of what user it's run as, etc., but who knows if it's my fault for upsetting the delicate balance that is /var/lib/private/mympd/config/sslport so I don't know if it's even worth filing a bug at this point.