(03-07-2022, 01:18 AM)japumpy Wrote: Well it's 1.5 years later. ;-) Same RPi that I've been using for other things. Just recently built an amplifier and bought myself a new SMSL D0200 DAC. So I thought I'd give the latest MoOde a try! I programmed two different cards of differing sizes and booted. Once configured, the system starts to build it's library and then, for no apparent reason, it stops dead. I then notice that the NAS has disappeared from the library list. The same result happens upon rebuild even though the NAS isn't showing on the 'browse by folders' list.
- RPi 3b
- PSU 5Amps
- Wired network
- NAS configuration is with IP address and not domain
- moode-r761-iso
- Number of tracks ~73,000
...
[Danger - bloviation lies ahead]
Preface: I'm assuming that moOde runs normally when you don't have any external Music Source defined in the Library. (AFAICT you never said.) If you can't boot a fresh image (no 64-bit kernel, please), configure for your DAC, and play the Stereo Test track and various radio stations, then there's a problem with your hardware and/or SD card.
Earlier on you mentioned a Synology NAS. I have a virtual DS3615XS instance running DSM 6.1 in my test environment. I have had no trouble mounting it in moOde using either SMB or NFS shares. With recent releases of moOde it is no longer necessary for me to fiddle with the SMB protocol version in the mount flags irrespective of the protocol setting on the NAS.
-----
Down to business:
Let's pull out some details from this post and your later post of the moOde log.
First, a general observation:
Quote:Number of tracks ~73,000
This is a huge collection for the software and low-powered hardware we're working with. I don't know that one can say with certainty there's an upper bound to what MPD can handle but generally once one gets into the multple tens of thousands of tracks everything gets sluggish even when it does work and several users have reported having various difficulties with collections exceeding 25000 to 50000 tracks.
-----
Next, the symptom
Quote:Once configured, the system starts to build it's library and then, for no apparent reason, it stops dead
suggests that there is at least one track with corrupted metadata causing MPD to stop scanning. MPD is not very forthcoming with details but you can get a hint from the log file
/var/log/mpd/log
When "Update library" is clicked, the MPD log begins accumulating entries like
Code:
Mar 07 07:45 : update: added NAS/OMV-Music/World/Ravi Shankar/In London/03 Ravi Shankar - Raga Ramkali.flac
The last such entry will be the last track successfully scanned by MPD, naturally.
In the case of an abnormal scan, this will be the last track scanned by MPD before it tries to scann the track which caused the halt. If the scan stops in the middle of a particular directory (aka folder) then it should be pretty obvious what the next track is. If, however, the scanning has moved to the beginning of another directory, then some detective work is required to determine what that directory is. As you can imagine, this detective work could be very tedious with 73,000 tracks to sift through.
Once identified, the offending track(s) can then be examined with other tools (starting with
mediainfo from the moOde player's command line).
There is a troubleshooting tip on the ArchLinux Wiki for dealing with this issue using a third-party tool such as EasyTAG or kid3. See
MPD_hangs_on_first_startup . Again, this will be tedious with so many tracks. I've never looked at more than about 5000 tracks at once using EasyTAG (and it was, you guessed it, tedious).
Note: The presence of certain hidden files and directories (eg, with names beginning with a period, dot, or fullstop, depending on your background) can cause problems with the MPD scan but I'm not seeing typical symptoms.
---
Next
Quote:I then notice that the NAS has disappeared from the library list
Please keep in mind that the Library folder view is not the view of a file manager; it is MPD's view of the database it builds when it scans tracks. This disappearance means MPD has removed information about tracks on the NAS from that database. I expect the SMB share is still mounted in the Linux filesystem (which can be checked using the
mount command from the moOde player's command line).
---
Next, there are curious entries found in the moOde log
Code:
20220306 190251 watchdog: Info: Reducing PHP fpm worker pool
20220306 200813 watchdog: Info: Reducing PHP fpm worker pool
20220306 211336 watchdog: Info: Reducing PHP fpm worker pool
20220306 222900 watchdog: Info: Reducing PHP fpm worker pool
20220307 112643 watchdog: Info: Reducing PHP fpm worker pool
20220307 123142 watchdog: Info: Reducing PHP fpm worker pool
I have no idea what's going on here but maybe @
Tim Curtis can comment.
Code:
20220307 145803 moode.php: MPD connect failed: cmd=(playlist)
20220307 145805 watchdog: Error: MPD restarted (check syslog for errors)
Entries like these imply MPD is dying during or after the library scan, which shouldn't be happening. Have you checked
/var/log/syslog for errors? If nothing suggestive is found then you might set MPD logging to verbose (in MPD settings), try scanning again, and recheck the
/var/log/mpd/log file. Note that this file can grow very large when logging verbosely.
---
Finally, as a test of your basic moOde / NAS connectivity, you could try creating a small Music Source entry from a subdirectory of the NAS's share.
For example, the hostname of one of my NAS boxes is
OMV-HC1. It publishes the music directory on the NAS as a share named
Music. In moOde I normally create the Music source from the hostname/share pair
OMV-HC1/Music with the MPD name
OMV-Music. (That's what you see above in my example taken from the MPD log). This share contains about 6000 tracks.
However, instead of using the main share I can create a small Music Source using any subdirectory of it. For example, I can create the music source named, say,
OMV-NewAge from
OMV-HC1/Music/NewAge, which contains only 600 tracks. This is a much more convenient number of tracks to test with. BTW, this works with any level subdirectory within the main share.
If you're lucky and the chosen subdirectory contains only "good" tracks, then this source can be used to test that moOde and your NAS can work together. If you are unlucky enough to choose a subdirectory which still causes the MPD scan to fail, then at least you will have an easier time troubleshooting the problem given the smaller number of tracks to examine.
Actually, this divide-and-conquer strategy can be used to identify all offending subdirectories but, again, can be very tedious for big collections.
Good hunting.
Regards,
Kent
PS - I'm not aware of any FOSS tool which comprehensively validates a music library in all its aspects before subjecting MPD to it. I've thought several times about cobbling a script out of the various different tools I do know but it always felt like I would be building a Frankenstein monster. Anyone have a suggestion?