Music library folder was reset to default

[cloo]

I'm not sure how to check when it happened, but my guess would be it was on last update (probably months ago).
Using 0.47.5~ynh2 on YunoHost 4.3.5

(Sorry for not using template - it should be clear enough though.. )

[cloo]

Also, after setting the library folder back, I found my playlists wiped. All playlists are listed in UI, but with no content.
When playlist downloaded via UI, the only line in .m3u file is
#EXTM3U

[ericgaspar]

it is hard to tell without logs...

[zecamigo]

@cloo

Were you using a custom location for your music library?

@ericgaspar
This just happened to me because when you upgrade the configuration file is reset.

Which means the music library location is reset to default and immediately after upgrade a scan is performed. This breaks all the favorites, playlists etc...

I couldn't find a way to stop navidrome from either resetting the configuration file or at least not start the service immediately so I can change the library location to my custom setting.

[ericgaspar]

The configuration file has been regenerated to be synchronized with the new upstream settings. Some parameters have been added to the config_panel.

[zecamigo]

The webadmin upgrades are awesome btw

So the workaround here would be to backup the database manually and the restore it after the upgrade?

[ericgaspar]

There is a sum check done to the replaced config file to check if it as custom changes, if so, a copy is then made before the file gets regenerated (I can't recall where this copy is stored...)

[zecamigo]

Yes the config file is saved, but before you have time to restore it, navidrome is already scanning the music library and breaking the favorites, playlists because it can't find the music files.

[zecamigo]

So the workaround here would be to backup the database manually and the restore it after the upgrade?

@ericgaspar would this be a viable workaround?
The custom config is saved, it's the scan after the update that instantly resets any favorites, playlists etc based on the files on a custom location.

This is permanent, even after the custom library location setting is restored, the database remains broken. This is possibly an upstream problem?

[IsidoreIsou]

Anyone found any solution to that problem?

[zecamigo]

@IsidoreIsou @ericgaspar
This is being discussed here:
navidrome/navidrome#2671

And an upstream improvement is being considered.

As this behavior in the YNH package breaks irreversibly the favorites playlist etc it would it be possible to also fix it also on this side?

For now I just restored from the backup and I'm waiting for a fix before I upgrade.

[IsidoreIsou]

thanks @zecamigo.

Something I'm not sure to understand:

Before the update, is there a location where Navidrome auto backup some config files like the "Recently Added" list? And can I restore this file after the update?

[zecamigo]

Before the update, is there a location where Navidrome auto backup some config files like the "Recently Added" list?

I'm guessing the date each file is added should be on the database before update.

The only backups should be the automatic ones if you have them running, and the backup ynh does just before the update. I don't know how to extract the database from that backup.

But even then the database structure might change from one version to the other, so it's not advisable to restore a previous' version database into the upgraded version.

[zecamigo]

This issue seems to have been fixed in the upstream code in version 0.51.1
@cloo @IsidoreIsou