[PROBLEM] 8.2.2 always show "Library update in progress"

[eroica]

It passed over one week after my moodeaudio had been updated to 8.2.2.
I feel 8.2.2 is very good and I enjoy music with moodeaudio everyday.
But, I met a strange thing when I trided to update library in USB disk.
Whenever I try to update folder, moodeaudio shows me "Library update in progress".
In case of selecting 'update library' from menu, I always meet the same situation. 
When I tried to update library after restarting modeaudio, but no changes. 
I can't update my music library because of this problem.

Refer to the attached pictures and moode log.

   
   

Code:

pi@MyConcertHall:~ $ moodeutl -l
20221103 234206 worker: --
20221103 234206 worker: -- Start moOde 8 series
20221103 234206 worker: --
20221103 234206 worker: Successfully daemonized
20221103 234226 worker: File check (OK)
20221103 234227 worker: Session vacuumed
20221103 234227 worker: Session loaded
20221103 234227 worker: Debug logging (OFF)
20221103 234227 worker: --
20221103 234227 worker: -- Audio debug
20221103 234227 worker: --
20221103 234227 worker: ALSA cards: (0:b1 | 1:Headphones | 2:empty | 3:empty
20221103 234227 worker: MPD config: (2:VMV USB AUDIO | mixer:(PCM) | card:2)
20221103 234227 worker: WARNING: No device found at MPD configured card 2
20221103 234227 worker: --
20221103 234227 worker: -- System
20221103 234227 worker: --
20221103 234230 worker: Host      (MyConcertHall)
20221103 234230 worker: moOde     (8.2.2 2022-10-23)
20221103 234230 worker: RaspiOS   (11.5)
20221103 234230 worker: Kernel    (5.15.61-v8+ #1579)
20221103 234230 worker: Platform  (Pi-3B 1.2 1GB)
20221103 234230 worker: ARM arch  (aarch64, 64-bit)
20221103 234230 worker: MPD ver   (0.23.5)
20221103 234230 worker: CPU gov   (ondemand)
20221103 234230 worker: USB boot  (not enabled yet)
20221103 234231 worker: File sys  (expanded)
20221103 234231 worker: HDMI port (Off)
20221103 234231 worker: Sys LED0  (On)
20221103 234231 worker: Sys LED1  (On)
20221103 234231 worker: --
20221103 234231 worker: -- Network
20221103 234231 worker: --
20221103 234231 worker: eth0 adapter exists
20221103 234231 worker: eth0 check for address (No)
20221103 234231 worker: IP addr (192.168.1.97)
20221103 234231 worker: Netmask (255.255.255.0)
20221103 234231 worker: Gateway (192.168.1.1)
20221103 234231 worker: Pri DNS (168.126.63.1)
20221103 234231 worker: Domain  ()
20221103 234231 worker: wlan0 adapter exists
20221103 234231 worker: wlan0 country (US)
20221103 234231 worker: wlan0 SSID is "None (activates AP mode)"
20221103 234231 worker: wlan0 AP mode not started (eth0 active but Router mode is Off)
20221103 234231 worker: wlan0 address not assigned
20221103 234231 worker: wlan0 power save disabled
20221103 234231 worker: apd0 router mode (Off)
20221103 234231 worker: --
20221103 234231 worker: -- Software update
20221103 234231 worker: --
20221103 234231 worker: Automatic check (On)
20221103 234231 worker: Checking for available update...
20221103 234232 worker: Release 8.2.3, 2022-MM-DD is available
20221103 234232 worker: --
20221103 234232 worker: -- Audio config
20221103 234232 worker: --
20221103 234232 worker: MPD conf update skipped (USB device)
20221103 234232 worker: ALSA card number (2)
20221103 234232 worker: MPD audio output (VMV USB AUDIO)
20221103 234232 worker: WARNING: No device found at MPD configured card 2
20221103 234232 worker: ALSA mixer name (PCM)
20221103 234232 worker: MPD mixer type (fixed 0dB)
20221103 234232 worker: Hdwr volume controller exists
20221103 234232 worker: Max ALSA volume (100%)
20221103 234232 worker: ALSA output mode (Default: plughw)
20221103 234232 worker: ALSA loopback (Off)
20221103 234232 worker: Reset renderer active flags
20221103 234232 worker: CamillaDSP (off)
20221103 234232 worker: --
20221103 234232 worker: -- File sharing
20221103 234232 worker: --
20221103 234233 worker: SMB file sharing (On)
20221103 234233 worker: NFS file sharing (Off)
20221103 234233 worker: --
20221103 234233 worker: -- MPD startup
20221103 234233 worker: --
20221103 234236 worker: MPD started
20221103 234236 worker: MPD accepting connections
20221103 234236 worker: MPD output 1 ALSA Default (On)
20221103 234236 worker: MPD output 2 ALSA Bluetooth (Off)
20221103 234236 worker: MPD output 3 HTTP Server (Off)
20221103 234236 worker: MPD crossfade (off)
20221103 234236 worker: MPD ignore CUE files (no)
20221103 234236 worker: --
20221103 234236 worker: -- Music sources
20221103 234236 worker: --
20221103 234236 worker: USB sources
20221103 234236 worker: MusicLibrary
20221103 234236 worker: NAS sources
20221103 234236 worker: MusicLibrary
20221103 234245 worker: Try (mount -t cifs "//192.168.1.40/MusicLibrary" -o username="musiclover",password="iloveMusic!",rsize=61440,wsize=65536,iocharset=utf8,ro,dir_mode=0777,file_mode=0777 "/mnt/NAS/MusicLibrary")
20221103 234245 worker: Err (mount error(113): could not connect to 192.168.1.40Unable to find suitable address.)
20221103 234245 worker: Mount all submitted
20221103 234245 worker: --
20221103 234245 worker: -- Feature availability
20221103 234245 worker: --
20221103 234245 worker: Source select (available)
20221103 234245 worker: Source select (source: MPD)
20221103 234245 worker: Source select (output: VMV USB AUDIO)
20221103 234250 worker: Bluetooth (available: started)
20221103 234251 worker: AirPlay renderer (available)
20221103 234251 worker: Spotify renderer (available)
20221103 234251 worker: Squeezelite (available)
20221103 234251 worker: RoonBridge renderer (not installed)
20221103 234251 worker: Multiroom sender (available)
20221103 234251 worker: Multiroom receiver (available)
20221103 234251 worker: UPnP renderer (available)
20221103 234251 worker: DLNA server (available)
20221103 234251 worker: GPIO button handler (available)
20221103 234251 worker: Stream recorder (n/a)
20221103 234251 worker: --
20221103 234251 worker: -- Other
20221103 234251 worker: --
20221103 234251 worker: USB volume knob (Off)
20221103 234251 worker: USB auto-mounter (udisks-glue)
20221103 234251 worker: Saved MPD vol level (0)
20221103 234251 worker: Preamp volume level (0)
20221103 234251 worker: MPD volume level (0) restored
20221103 234251 worker: ALSA PCM volume (Invalid card number.)
20221103 234251 worker: Auto-play (Off)
20221103 234251 worker: CoverView toggle (-off)
20221103 234251 worker: On-screen keyboard (Off)
20221103 234251 worker: Library scope (all)
20221103 234251 worker: Maintenance interval (360 minutes)
20221103 234251 worker: Screen saver activation (Never)
20221103 234251 worker: Session permissions (OK)
20221103 234251 worker: Mount monitor (Off)
20221103 234251 worker: Watchdog started
20221103 234251 worker: Ready
pi@MyConcertHall:~ $

[Nutul]

It passed over one week after my moodeaudio had been updated to 8.2.2.
I feel 8.2.2 is very good and I enjoy music with moodeaudio everyday.
But, I met a strange thing when I trided to update library.
Whenever I try to update folder, moodeaudio shows me "Library update in progress".
In case of selecting 'update library' from menu, I always meet the same situation. 
I can't update my music library because of this problem.

There is for sure an offending file in the folder you cannot update, maybe something unusual with the tags. I noticed the same issue when debugging an MP3 file which contained a weird, html-looking tag: it crashed the JS in charge of the update, which also resulted in the flag indicating library-update from being reset, thus preventing any further update requests to be even considered...

I'd examine the files' metadata, possibly in those lately added, first, provided the update was working, till some day in the near past.


Cheers, Al.

[eroica]

It passed over one week after my moodeaudio had been updated to 8.2.2.
I feel 8.2.2 is very good and I enjoy music with moodeaudio everyday.
But, I met a strange thing when I trided to update library.
Whenever I try to update folder, moodeaudio shows me "Library update in progress".
In case of selecting 'update library' from menu, I always meet the same situation. 
I can't update my music library because of this problem.

There is for sure an offending file in the folder you cannot update, maybe something unusual with the tags. I noticed the same issue when debugging an MP3 file which contained a weird, html-looking tag: it crashed the JS in charge of the update, which also resulted in the flag indicating library-update from being reset, thus preventing any further update requests to be even considered...

I'd examine the files' metadata, possibly in those lately added, first, provided the update was working, till some day in the near past.


Cheers, Al.

Thank you for quick response.

I can update my music library by regenerating library.
I use one NAS and one USB disk for music library which contain about 8000 folders.
So, library regeneration takes a lot of time and it is not easy to listen music before it finished.
Partial updating such as 'update folder' must be very useful for users who have big library.
I hope this problem can be solved in soon.

[Nutul]

I use one NAS and one USB disk for music library which contain about 8000 folders.
So, library regeneration takes a lot of time and it is not easy to listen music before it finished.
Partial updating such as 'update folder' must be very useful for users who have big library.

this is exactly why I asked you to check for the recently added files, and see if some of them have some weird text in their metadata...
You don't need to update the library, just examine such files with a tag editor...

Other than this, cannot say.


Cheers, Al.

[5-pot-fan]

Hi,
I hope this is not hijacking the OP's thread but I have some queries along a similar path.


1) Is there a way of viewing a startup log that would indicate where the library updating/reading process stopped - or at least where it successfully got to - preferably by foldername or something similar? This must be easier than going through 100's of files/folders looking for some odd metadata!
2) What if anything is the difference between 'Regenerate Library' (in the Library dropdown) and 'Library Update' in the 'm' dropdown?
3) Does the 'Update This Folder' option in Folder view really just update the contents of the selected folder when later viewed in Tag view? (My system is offline at present while I create a completely new 8.2.2 configuration).

[eroica]

I use one NAS and one USB disk for music library which contain about 8000 folders.
So, library regeneration takes a lot of time and it is not easy to listen music before it finished.
Partial updating such as 'update folder' must be very useful for users who have big library.

this is exactly why I asked you to check for the recently added files, and see if some of them have some weird text in their metadata...
You don't need to update the library, just examine such files with a tag editor...

Other than this, cannot say.


Cheers, Al.

I've check the files in recently added folder.
But, I found nothing to suspect.
Refer to the attached pictures.

   
   

[Nutul]

I use one NAS and one USB disk for music library which contain about 8000 folders.
So, library regeneration takes a lot of time and it is not easy to listen music before it finished.
Partial updating such as 'update folder' must be very useful for users who have big library.

this is exactly why I asked you to check for the recently added files, and see if some of them have some weird text in their metadata...
You don't need to update the library, just examine such files with a tag editor...

Other than this, cannot say.


Cheers, Al.

I've check the files in recently added folder.
But, I found nothing to suspect.
Refer to the attached pictures.

1. I see an "&", but this should not be an issue, other than show up weirdly in the library (if this is also in the file's metadata)
2. what you are showing in the pictures is just the folder / file names, not the actual metadata in the files... Also, it is far from being complete...

You could probably also look at the mpd log itself for any clue (IIRC). Such file is /var/log/mpd/log
If the problem is at mpd level, that file should contain the last processed file (with more luck it will contain the offending one, but cannot tell for sure out of my mind)
If the problem, OTOH, is at JS level, opening up the developer tools (ctrl + shift + I) in the browser could give some help... Note that if the problem is at JS, it will show-up in any browser, so from your PC you're good to give it a go.


Cheers, Al.

[TheOldPresbyope]

@eroica

As @Nutul suggested, have a look at /var/log/mpd/log to see where MPD had got to when it stopped updating/or regenerating its library [1].

For instance, here's the last few lines in the log after I plugged in a USB thumbdrive containing some tracks

Code:

...
Nov 03 13:48 : update: added USB/39701C9F1828917E/HeartsOfSpace-Universe-2/Robert Rich - Universe 2 - 03 Tracery.flac
Nov 03 13:48 : update: added USB/39701C9F1828917E/HeartsOfSpace-Universe-2/Tim Story - Universe 2 - 08 And Evening Falls.flac
Nov 03 13:48 : update: added USB/39701C9F1828917E/HeartsOfSpace-Universe-2/Tim Story - Universe 2 - 09 Her Cathedral.flac

Note that it's pretty spartan but it does show the paths (relative to the "root" of the MPD library, which for us is /var/lib/mpd/music; symlinks in that directory point to filesystem mountpoints).

Regards,
Kent

[TheOldPresbyope]

Hi,
I hope this is not hijacking the OP's thread but I have some queries along a similar path.

Yeah, it is, kinda.

1) Is there a way of viewing a startup log that would indicate where the library updating/reading process stopped - or at least where it successfully got to - preferably by foldername or something similar? This must be easier than going through 100's of files/folders looking for some odd metadata!

See my reply to eroica. Unfortunately, MPD is not very helpful in identifying problems nor suggesting solutions.

2) What if anything is the difference between 'Regenerate Library' (in the Library dropdown) and 'Library Update' in the 'm' dropdown?

I think of them as "throw it out and start over" vs "make necessary changes".

3) Does the 'Update This Folder' option in Folder view really just update the contents of the selected folder when later viewed in Tag view? (My system is offline at present while I create a completely new 8.2.2 configuration).

Note that we (well, MPD, really) speak loosely when we say "Library". What's being updated is the database (a specialized file, actually) MPD maintains describing the tracks it has scanned. This particular choice restricts MPD to the selected folder when scanning tracks. Whatever changes are made to the database in the process may affect all views.

Regards,
Kent

[eroica]

I checked the moode log and mpd log when "Library update in progress" was seen.
But I found no log data in that time while I saw the mpd log contain the last processed library update data when the library update executed.