System: RPi B+ (trying to reuse an old Pi I had laying around)
Software: Volumio 2.692
I have a new install of volumio and a very large music library (35K+ songs) on my NAS. The initial scan over ethernet works fine, but when I switched to WiFi only I was finding that mpd was never starting up. When running an strace of mpd, I found that it was trying stat every file in my library on startup. From journalctl output I see that mpd is eventually getting killed, for example this is from earlier this afternoon:
Jan 04 12:30:27 masterbath systemd[1]: mpd.service stop-final-sigterm timed out. Killing.
Jan 04 12:30:27 masterbath systemd[1]: mpd.service: main process exited, code=killed, status=9/KILL
Jan 04 12:30:27 masterbath systemd[1]: Failed to start Music Player Daemon.
Jan 04 12:30:27 masterbath systemd[1]: Unit mpd.service entered failed state.
Jan 04 12:30:27 masterbath systemd[1]: Starting Music Player Daemon...
It looks like it is taking so long to scan my collection for new files that systemd kills mpd since it is taking too long to send a notify. This then starts the scan again, which causes mpd to get killed again, in a never-ending loop. Since the scan never finishes, volumio never becomes usable.
I found a workaround in this thread: github.com/MusicPlayerDaemon/MPD/issues/259, but that really seems like a hack (setting the Type to simple instead of notify). However, this does get me up and running and makes the system usable. Has anyone else run into this, and are there any other suggestions for a fix? I think the obvious fix would be to have mpd do the scan in a separate thread, but that’s really outside the scope of volumio.
)