[SOLVED] Alert Library update is already in progress.

[schwidi]

    I have a Raspberry Pi4 with 2 GB RAM.
My complete database with Flac File from the NAS was read in and works perfectly when playing. The problem I have is when I add a new interpreter, I click on NAS Flac files and then update on this folder, has been the following error since 9.0 and 9.01: Alert
The library update is already carried out.

Even a restart didn't help, what can I do?

[DRONE7]

Please post in English for best response :-)
Für eine optimale Antwort posten Sie bitte auf Englisch

I have a Raspberry Pi4 with 2 GB of RAM. My complete database with Flac file from the NAS was read in and works perfectly when playing. The problem I have is when I add a new interpreter, I click on NAS flac files and then update to this folder, since 9.0 and 9.01 the following error appears: Alert The library update is already in progress. Even a restart did not help, what can I do?

[DRONE7]

How big is your library ? How many files ? and have you waited for the spinner (top right main page) to compleat ?

[schwidi]

The database is 3TB large, Done: 5575 folders scanned, 4 thumbs created, 5571 already in cache.
Everything was already read, it's just a new artist that I pushed on the NAS. I then press update this folder nothing turns at the top right, only the error is alert
Library Update is already in progress.

[Tim Curtis]

To troubleshoot do the following:

1. Reboot
2. Open the Browser Javascript console
3. Folder view, navigate to folder containing the newly added track, Update this folder
4. Look for errors in the Javascript console

[TheOldPresbyope]

I can repro the issue with a modest library of 300+ albums on a NAS plus just the stereo test file on the SDCARD and not adding any new files.

moOde 9.0.1 on a RPi3B+ with local display. OpenMediaVault NAS software.

Pre-test state: NAS has been added as music source and the library updated.

Test:

1. reboot moOde player. Open the Javascript console. See some interesting but likely unrelated messages.
2. in the Browse by folders view, select "update this folder" on the SDCARD. "Info Library is being updated...SDCARD" popup appears, sinner runs briefly, and both go away.
3. do the same with the NAS folder. "Info Library is being updated...NAS" popup appears and after a time goes away while spinner runs for a time, and then goes away.

So far, so good, but repeating steps 2 and 3

4. :"update this folder" on SDCARD runs the same as above.
5. "update this folder" on NAS and "Alert Library update already in process" popup appears.
6. repeat "update this folder" on NAS; this time runs normally, the same as 3.

Thoughts?

Regards,
Kent

[Tim Curtis]

Before you repeat steps 2,3 switch to Tag or Album view, Menu, refresh then back to Folder view, then try 2,3 again.

ETA: There is a global "library loading" flag that gets set when Update library is run then cleared when the update finishes and the libcache loads into Tag/Album view.

[schwidi]

I don't know about such things at all, the only thing I found were these mistakes.
Also helps me a new installation of Mood to fix the error, that would be the easiest for me.

Uncaught TypeError: Cannot read properties of undefined (reading 'slice')
at albumHDBadge (playerlib.js:4778:19)
at renderAlbums (scripts-library.js:644:57)
at renderArtists (scripts-library.js:587:2)
at renderGenres (scripts-library.js:567:2)
at renderLibrary (scripts-library.js:128:2)
at Object.success (scripts-library.js:108:3)
at u (jquery-1.8.2.js:974:30)
at Object.fireWith [as resolveWith] (jquery-1.8.2.js:1082:7)
at N (jquery-1.8.2.js:7788:14)
at XMLHttpRequest.n (jquery-1.8.2.js:8500:8)

[schwidi]

I reinstalled Moode 9.01 again.
The complete database again read up to the end.
Mood restarted, clicked at any interpreter update this folder, the same error again: Alert
Library Update is already in progress.
I tested all the browsers, the same problem with the smartphone.
With Moode 8.3.9 no problems.

[Tim Curtis]

The console log shows "Uncaught TypeError:"
This is a bug fixed for upcoming 9.0.2 release.

I think you can avoid the bug by setting "Preferences, Library, Sample rate" to something other than "HD only".