[PROBLEM] can't update library

[Tim Curtis]

Examine the MPD log for errors or to determine the last track that it successfully indexed.

Code:

cat /var/log/mpd/log

mine is empty

There is a maintenance task that purges the logs every every 3 hours which could account for an empty MPD log.

Try regen again and check the log in real time using the command below to confirm that MPD is able to index files. If the log is still empty then something else its going on thats not obvious to me.

Code:

# Print the log as its being written
tail -f /var/log/mpd/log

# Print the log
cat /var/log/mpd/log

[uteroid]

Examine the MPD log for errors or to determine the last track that it successfully indexed.

Code:

cat /var/log/mpd/log

mine is empty

There is a maintenance task that purges the logs every every 3 hours which could account for an empty MPD log.

Try regen again and check the log in real time using the command below to confirm that MPD is able to index files. If the log is still empty then something else its going on thats not obvious to me.

Code:

# Print the log as its being written
tail -f /var/log/mpd/log

# Print the log
cat /var/log/mpd/log

my output for moodeutil -l  looks like below, I never get the last two lines, you posted in the previous posts, for mpdindex and worker: Job update_library done

Code:

20250503 060006 worker: Job update_library
20250503 060006 mpdindex: Start
20250503 060006 mpdindex: Cmd (update)
20250503 060006 thumb-gen: Start
20250503 060006 thumb-gen: Scan opt: Default
20250503 060006 thumb-gen: Priority: Embedded cover
20250503 060006 thumb-gen: Res,Qual: Auto
20250503 060006 thumb-gen: Px ratio: 2
20250503 060006 thumb-gen: Th width: 200
20250503 060006 thumb-gen: Thm qual: 75
20250503 060006 thumb-gen: Scanning: NAS, NVME, SATA, SDCARD
20250503 060014 thumb-gen: Done: 598 folders scanned, 0 thumbs created, 598 already in cache.

[zbilic]

Hello,
I managed to "fix" the generation of the MPD database when the source is a remote SAMBA filesystem.

The problem was in the advanced mount settings (although I did not change them before or after the update).
Unfortunately, it is not immediately visible because the mounted file system is readable, and the utility "/var/www/util/list-songfiles.sh" generates a list.
Therefore, I deleted "Remote NAS Source" from "WebUI" and mounted the remote filesystem via console with the server "vers=x.y" option.
After that, the generation of MPD databases from the "WebUI" is successful, but the progress spinner never stops.
In the next step, I deleted the "cache=none" option, and the progress spinner disappeared after generating the database again.
Without a defined cache option, the default value "cache=strict" is used

Code:

cache=
    Cache mode. See the section below on CACHE COHERENCY for details. Allowed values are:
    • none: do not cache file data at all
    • strict: follow the CIFS/SMB2 protocol strictly
    • loose: allow loose caching semantics
    The default in kernels prior to 3.7 was "loose". As of kernel 3.7 the default is "strict".
    
"cache=strict means that the client will attempt to follow the CIFS/SMB2 protocol strictly.
That is, the cache is only trusted when the client holds an oplock.
When the client does not hold an oplock, then the client bypasses the cache and accesses the server directly to satisfy a read or write request.
By doing this, the client avoids problems with byte range locks.
Additionally, byte range locks are cached on the client when it holds an oplock and are "pushed" to the server when that oplock is recalled. "

If there is no proposal already, I would suggest the "rollback" feature in "Software update" for the backlog functionality.

I am aware that there is Backup/Restore functionality for configuration, but not for binary packages ie. restore the entire system to the state before the update.

Kind regards,

Zlatko

[Tim Curtis]

Thanks for the testing. The "cache=none" option has been there forever but I can certainly update the help.

Most mount options are auto-negotiated when the mount is attempted but in some cases auto-negotiation cannot determine the correct values and the mount may fail. In this case certain options must be explicitly added or changed. Some of these are listed below.
SMB: vers=x.y, sec=ntlm or sec=ntlmssp, cache=strict
NFS: vers=x.y, type=nfs2, nfs3 or nfs4

I think rolling back an updated system to its pre-update state would be difficult to implement and most likely very unreliable in the field for example what if the rollback failed, then what.

The easiest and most trouble free is to boot a fresh image and restore from a backup.

[uteroid]

Thanks for the testing. The "cache=none" option has been there forever but I can certainly update the help.

Most mount options are auto-negotiated when the mount is attempted but in some cases auto-negotiation cannot determine the correct values and the mount may fail. In this case certain options must be explicitly added or changed. Some of these are listed below.
SMB: vers=x.y, sec=ntlm or sec=ntlmssp, cache=strict
NFS: vers=x.y, type=nfs2, nfs3 or nfs4

I think rolling back an updated system to its pre-update state would be difficult to implement and most likely very unreliable in the field for example what if the rollback failed, then what.

The easiest and most trouble free is to boot a fresh image and restore from a backup.

So I started fresh, installed a clean image, added my share and regenerated, it only added 3 songs, Billy Joel if you're curious : and nothing else.  Tried updating again and only those 3 songs remain, the circle keeps spinning... I'm not doing anything different than what I've done in the past... only usually I would restore from back up, this time I just added everything fresh.

[Tim Curtis]

Have you examined the MPD log?

Code:

# Print the log as its being written
tail -f /var/log/mpd/log

# Print the log
cat /var/log/mpd/log

[uteroid]

Have you examined the MPD log?

Code:

# Print the log as its being written
tail -f /var/log/mpd/log

# Print the log
cat /var/log/mpd/log

I see a buncha entries like below

Code:

Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2025-05-05T11:47:09 ffmpeg: Unsupported libavcodec SampleFormat value: name   depth (?)
2025-05-05T11:47:09 update: added NAS/HiRez/Billy Joel/Turnstiles/._08. Miami 2017 (Seen The Lights Go Out On Broadway).flac
2025-05-05T11:47:09 update: added NAS/HiRez/Billy Joel/Billy Joel - 1978 - 52nd Street (MFSL Hybrid SACD 2012)/Billy Joel - 52nd Street MFSL.flac
2025-05-05T11:47:10 ffmpeg/flac: Format flac detected only with low score of 1, misdetection possible!
2025-05-05T11:47:10 ffmpeg/flac: Could not find codec parameters for stream 0 (Audio: flac, 0 channels): unspecified sample format
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2025-05-05T11:47:10 ffmpeg: Unsupported libavcodec SampleFormat value: name   depth (?)
2025-05-05T11:47:10 update: added NAS/HiRez/Billy Joel/Billy Joel - 1978 - 52nd Street (MFSL Hybrid SACD 2012)/._Billy Joel - 52nd Street MFSL.flac

[Tim Curtis]

Theres not any useful information in the MPD log other than it apparently did not proceed past the Billy Joel folder.

You could try temporarily moving that folder to an offline USB stick and then see if MPD makes it any further.

[zbilic]

Have you examined the MPD log?

Code:

# Print the log as its being written
tail -f /var/log/mpd/log

# Print the log
cat /var/log/mpd/log

I see a buncha entries like below

Code:

Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2025-05-05T11:47:09 ffmpeg: Unsupported libavcodec SampleFormat value: name   depth (?)
2025-05-05T11:47:09 update: added NAS/HiRez/Billy Joel/Turnstiles/._08. Miami 2017 (Seen The Lights Go Out On Broadway).flac
2025-05-05T11:47:09 update: added NAS/HiRez/Billy Joel/Billy Joel - 1978 - 52nd Street (MFSL Hybrid SACD 2012)/Billy Joel - 52nd Street MFSL.flac
2025-05-05T11:47:10 ffmpeg/flac: Format flac detected only with low score of 1, misdetection possible!
2025-05-05T11:47:10 ffmpeg/flac: Could not find codec parameters for stream 0 (Audio: flac, 0 channels): unspecified sample format
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2025-05-05T11:47:10 ffmpeg: Unsupported libavcodec SampleFormat value: name   depth (?)
2025-05-05T11:47:10 update: added NAS/HiRez/Billy Joel/Billy Joel - 1978 - 52nd Street (MFSL Hybrid SACD 2012)/._Billy Joel - 52nd Street MFSL.flac

Hi,
maybe I overlooked it, but I didn't see what network protocol you are using on your NAS? SMB, NFS...?

In the case of SMB, can you check what version it is, and set the appropriate vers=x.y parameter for the Mount options (Advanced section) and optionaly "cache" mode.
You can use nmap scanning to help.

Code:

root@moode:~# nmap -p445 --script smb-protocols <RemoteIPAddress>
root@moode:~# nmap -p139 --script smb-protocols <RemoteIPAddress>

[uteroid]

Have you examined the MPD log?

Code:

# Print the log as its being written
tail -f /var/log/mpd/log

# Print the log
cat /var/log/mpd/log

I see a buncha entries like below

Code:

Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2025-05-05T11:47:09 ffmpeg: Unsupported libavcodec SampleFormat value: name   depth (?)
2025-05-05T11:47:09 update: added NAS/HiRez/Billy Joel/Turnstiles/._08. Miami 2017 (Seen The Lights Go Out On Broadway).flac
2025-05-05T11:47:09 update: added NAS/HiRez/Billy Joel/Billy Joel - 1978 - 52nd Street (MFSL Hybrid SACD 2012)/Billy Joel - 52nd Street MFSL.flac
2025-05-05T11:47:10 ffmpeg/flac: Format flac detected only with low score of 1, misdetection possible!
2025-05-05T11:47:10 ffmpeg/flac: Could not find codec parameters for stream 0 (Audio: flac, 0 channels): unspecified sample format
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2025-05-05T11:47:10 ffmpeg: Unsupported libavcodec SampleFormat value: name   depth (?)
2025-05-05T11:47:10 update: added NAS/HiRez/Billy Joel/Billy Joel - 1978 - 52nd Street (MFSL Hybrid SACD 2012)/._Billy Joel - 52nd Street MFSL.flac

Hi,
maybe I overlooked it, but I didn't see what network protocol you are using on your NAS? SMB, NFS...?

In the case of SMB, can you check what version it is, and set the appropriate vers=x.y parameter for the Mount options (Advanced section) and optionaly "cache" mode.
You can use nmap scanning to help.

Code:

root@moode:~# nmap -p445 --script smb-protocols <RemoteIPAddress>
root@moode:~# nmap -p139 --script smb-protocols <RemoteIPAddress>

This is what I got... It's an older NAS, Buffalo Linkstation

Code:

Starting Nmap 7.93 ( https://nmap.org ) at 2025-05-08 10:13 EDT
Nmap scan report for 192.168.0.201
Host is up (0.0064s latency).

PORT    STATE SERVICE
445/tcp open  microsoft-ds

Host script results:
| smb-protocols:
|   dialects:
|_    NT LM 0.12 (SMBv1) [dangerous, but default]

Starting Nmap 7.93 ( https://nmap.org ) at 2025-05-08 10:14 EDT
Nmap scan report for 192.168.0.201
Host is up (0.0064s latency).

PORT    STATE SERVICE
139/tcp open  netbios-ssn

Host script results:
| smb-protocols:
|   dialects:
|_    NT LM 0.12 (SMBv1) [dangerous, but default]