07-24-2025, 11:12 AM
That number of files should be no problem but no matter how many files the best way to troubleshoot this type of issue is to follow the steps below.
1. Reboot
2. Clear the MPD log
3. Regenrate the Music database
Menu > Configure > Library
a. REGENERATE music database
b. Stay on the page until the busy spinner clears
4. Examine the MPD log in real time for a few minutes
Each line should say "updating" or "adding"
5. After the busy spinner clears (step 3b)
Examine the moode log and verify the statistics for the "regen_library" job
It should look like below ending with Job regen_library done
On the server side, signs of trouble in Library database regen include the following:
1. Permission errors in the MPD log. This indicates the file or album directory could not be accessed.
2. "Job regen_library done" never appears in the moode log. This indicates MPD database rescan (or update) never completed because MPD hung or crashed.
3. If MPD crashed there would be an additional message in the moode log from the "watchdog" daemon. It would say something like "MPD restarted".
On the client side look for Browser errors that indicate one of the WebUI Java scripts has crashed
1. Return from the Library Config screen to the main Playback or Library screen
2. Open the Browser Javascript console
3. Look for errors indicating a script has crashed.
The error would say something like "undefined function" or "undefined variable" and it would list the line number and the file name where the error occurred.
1. Reboot
2. Clear the MPD log
Code:
sudo truncate /var/log/mpd/log --size 0
3. Regenrate the Music database
Menu > Configure > Library
a. REGENERATE music database
b. Stay on the page until the busy spinner clears
4. Examine the MPD log in real time for a few minutes
Each line should say "updating" or "adding"
Code:
# View log in real time
tail -f /var/log/mpd/log
Ctrl-c to exit
# View entire log
moodeutl --mpdlog
--or--
cat /var/log/mpd/log
5. After the busy spinner clears (step 3b)
Examine the moode log and verify the statistics for the "regen_library" job
Code:
moodeutl -l
It should look like below ending with Job regen_library done
Code:
20250724 064327 worker: Job regen_library
20250724 064327 worker: Clear Library tag cache
20250724 064327 mpdindex: Start
20250724 064327 mpdindex: Cmd (rescan)
20250724 064327 worker: Clear thumbnail cache
20250724 064327 thumb-gen: Start
20250724 064327 thumb-gen: Scan opt: Default+
20250724 064327 thumb-gen: Priority: Embedded cover
20250724 064327 thumb-gen: Res,Qual: 600px,60
20250724 064327 thumb-gen: Px ratio: 1
20250724 064327 thumb-gen: Th width: 600
20250724 064327 thumb-gen: Thm qual: 60
20250724 064327 thumb-gen: Scanning: NAS, NVME, OSDISK, SATA, SDCARD
20250724 064420 thumb-gen: Done: 410 folders scanned, 410 thumbs created, 0 already in cache.
20250724 064647 mpdindex: Done: indexed 320 artists, 409 albums, 4555 songs
20250724 064647 worker: Job regen_library done
On the server side, signs of trouble in Library database regen include the following:
1. Permission errors in the MPD log. This indicates the file or album directory could not be accessed.
2. "Job regen_library done" never appears in the moode log. This indicates MPD database rescan (or update) never completed because MPD hung or crashed.
3. If MPD crashed there would be an additional message in the moode log from the "watchdog" daemon. It would say something like "MPD restarted".
On the client side look for Browser errors that indicate one of the WebUI Java scripts has crashed
1. Return from the Library Config screen to the main Playback or Library screen
2. Open the Browser Javascript console
3. Look for errors indicating a script has crashed.
The error would say something like "undefined function" or "undefined variable" and it would list the line number and the file name where the error occurred.