[SOLVED] Library update issue

[radu-]

I'm running Moode (I'm on 8.2.5 now) on a RPi Zero W for some time now (3+ years) and didn't have any major issues.

Yesterday I added some new music to my collection and started a Library update, but it didn't get the changes. Today I tried again with the same result. I tried to check the mpd log, as in the past I could see what was going on, but the log is empty. How else can I check what's happening? I can see the "updating icon" on the Web UI, and `mpc status` shows that the library update is ongoing, but there's no change.

On my other installation, on a RPi 3, the library updated without issues, but /var/log/mpd/log is empty there too.

[Tim Curtis]

There is a maintenance task that runs every 6 hours and one of its processes is to clear all the system logs including the MPD log.

You can try monitoring the MPD log with tail -f /var/log/mpd/log and then from Folder view update just one of the folders and then see what shows up in the log.

[radu-]

OK, but by default, when running the full library update is that done specifically without saving the log? Because during that update I was trying to run

Code:

tail -f /var/log/mpd/log

and that was empty.

Also, refreshing a single folder will not scan the cover art and won't create the thumbnail(s), right?

[Tim Curtis]

OK, but by default, when running the full library update is that done specifically without saving the log? Because during that update I was trying to run

Code:

tail -f /var/log/mpd/log

and that was empty.

Also, refreshing a single folder will not scan the cover art and won't create the thumbnail(s), right?

MPD log is controlled by MPD and not moOde. If MPD updates something in its database it records it in the log.

Updating a single folder goes through same routine as full lib update and thus thumbnail scan is run. You should see this and the log entries for mpd update in the moode log.

moodeutl -l

[TheOldPresbyope]

@radu- 

MPD has a habit of stopping its update process for reasons of its own without telling the user what and where. Problems range from such things as improper directory permissions to corrupt metadata in one or more files.

One trick you can use to narrow down your search is to

• in one window, start tail -f /var/log/mpd/log from the command line
  
• in another window, using the WebUI: m > Configure > Library: REGENERATE the Music Database
  
• at some point, /var/log/mpd/log will stop updating. The last line represents the last file which MPD could reach and consider a valid music file before it bailed out
  
• examine your music directory to see where MPD should have scanned next.
  

Yes, I'm assuming MPD can still scan the library you already had and, yes, this is an annoying troubleshooting process, but that's the way MPD is.

Regards,
Kent

[radu-]

Thanks for the details. Seems like there was an issue with the RPi (Zero) on my side. After trying most stuff I could think of, I rebooted it. And, lo and behold, I can see the mpd log while scanning!