Thank you for the suggestion.
I am deleting the NAS first and will create a new drive when that is done. I will have to rescan, anyway, when the files finish copying to the new hard drive array, and I want the mount and the DLNA library to be on the same page. I will see if I can get a mount without using the IP address. I hope that resolves my issues.
I don’t think that using the IP address of the NAS is the cause of your problem. For testing I recently have successfully mounted a folder called “music” on a Samba share to my Volumio test system and used the IP address But deviating from your approach I adopted the folders name “music” for the alias.
I took your lead and started with a new image. Source is now just “Music.” DLNA library is NAS/Music. Music subdirectories appear when I look at folder structures of each.
Couldn’t have fixed this without you, gvolt. Thanks again.
Thanks for the plugin : I’m using volumio 3 on raspberry 2, I installed the DLNA plugin (2tb usb disk). Everything ok but at each restart the DLNA DB is lost and rebuilt (the music library is kept instead). Is there any way to avoid it? I did not find any settings in the web interface. Thanks in advance
Where do you see the recreation of the database? In the minidlna.log file?
The plugin is just a wrapper for the minidlna server providing access to minidlna’s options in Volumio’s UI. The behaviour you described is not initiated by the plugin.
It could be this happens because there is an error detected in the database. However, I am not sure if a database rebuild is not part of the standard behavior when minidlna gets started. If the latter should be the case: To my knowledge there is no (documented / known) option to force minidlna to refrain from doing so.
Maybe have a look at the minidlna.log file (default location: /var/log/minidlna.log) for possibly related error messages.
For testing purposes you may also stop the plugin, delete the .db file (default location: /data/configuration/music_service/minidlna/files.db) and start the plugin with a minimal set of audio files only.
I just checked it on a Volumio 3 test system and it seems that minidlna does indeed rebuild its database on every startup. On an openSUSE Leap 15.3 x86 machine, running minidlna 1.3.1 (i.e. newer than the version available for Buster based Volumio 3), I found the same behavior.
Hey Everyone.
Having some significant problems with MiniDLNA on the latest version OS. Keeps crashing at regular intervals. The crash interval depends on the expanded plugin setting for notifications, e.g. 5 sec. These are the error msgs samples. Basically the HTTP server shuts down. If I change the notify parameter to 10, the same happens every 10 sec.
[2024/03/26 20:26:44] upnphttp.c:1095: warn: HTTP Connection closed unexpectedly
[2024/03/26 20:26:44] upnpsoap.c:2193: warn: SoapMethod: Unknown: GetSortExtensionCapabilities
[2024/03/26 20:26:44] upnpsoap.c:123: warn: Returning UPnPError 401: Invalid Action
[2024/03/26 20:26:44] upnpsoap.c:2193: warn: SoapMethod: Unknown: GetFeatureList
[2024/03/26 20:26:44] upnpsoap.c:123: warn: Returning UPnPError 401: Invalid Action
[2024/03/26 20:26:49] upnphttp.c:1095: warn: HTTP Connection closed unexpectedly
[2024/03/26 20:26:49] upnpsoap.c:2193: warn: SoapMethod: Unknown: GetSortExtensionCapabilities
[2024/03/26 20:26:49] upnpsoap.c:123: warn: Returning UPnPError 401: Invalid Action
[2024/03/26 20:26:49] upnpsoap.c:2193: warn: SoapMethod: Unknown: GetFeatureList
[2024/03/26 20:26:49] upnpsoap.c:123: warn: Returning UPnPError 401: Invalid Action
[2024/03/26 20:26:54] upnphttp.c:1095: warn: HTTP Connection closed unexpectedly
When I change notify to 0 sec, MiniDLNA dies completely.
[2024/03/26 20:28:31] minidlna.c:155: warn: received signal 15, good-bye
[2024/03/26 20:28:31] minidlna.c:1060: warn: Starting MiniDLNA version 1.2.1.
[2024/03/26 20:28:31] minidlna.c:357: warn: New media_dir detected; rebuilding…
[2024/03/26 20:28:31] minidlna.c:1101: warn: HTTP listening on port 8200
[2024/03/26 20:28:35] upnphttp.c:1263: error: send(res_buf): Broken pipe
[2024/03/26 20:28:35] upnphttp.c:1263: error: send(res_buf): Broken pipe
[2024/03/26 20:28:36] upnphttp.c:1263: error: send(res_buf): Broken pipe
[2024/03/26 20:28:37] upnphttp.c:1095: warn: HTTP Connection closed unexpectedly
I tried all three supported versions of MiniDLNA, behaviour is the same. Using version 3.1.12 now
VolumioOS version 3.631. It was working fine on the previous OS
Package log from the last reinstall looks good to me:
2024-03-26 20:03:22 configure minidlna:armhf 1.2.1+dfsg-2+deb10u4
2024-03-26 20:03:22 status unpacked minidlna:armhf 1.2.1+dfsg-2+deb10u4
2024-03-26 20:03:22 status half-configured minidlna:armhf 1.2.1+dfsg-2+deb10u4
2024-03-26 20:03:27 status installed minidlna:armhf 1.2.1+dfsg-2+deb10u4
2024-03-26 20:03:27 trigproc libc-bin:armhf 2.28-10+rpt2+rpi1+deb10u2
2024-03-26 20:03:27 status half-configured libc-bin:armhf 2.28-10+rpt2+rpi1+deb10u2
2024-03-26 20:03:27 status installed libc-bin:armhf 2.28-10+rpt2+rpi1+deb10u2
2024-03-26 20:03:27 trigproc systemd:armhf 241-7~deb10u9+rpi1
2024-03-26 20:03:27 status half-configured systemd:armhf 241-7~deb10u9+rpi1
2024-03-26 20:03:28 status installed systemd:armhf 241-7~deb10u9+rpi1
No other logs show any related activity.
I think it’s a permissions problem. MiniDLNA is started as minidlna user, /var/log/<…> are all owned by root. Does it try to log somewhere else and can’t?
drwxr-xr-x 6 volumio adm 280 Mar 26 20:03 .
drwxr-xr-x 1 root root 1024 Feb 21 21:33 …
-rw-r–r-- 1 volumio volumio 0 Mar 26 19:57 albumart.log
drwxr-xr-x 2 root root 100 Mar 26 20:03 apt
-rw------- 1 root root 7267 Mar 26 19:57 boot.log
-rw-rw---- 1 root utmp 0 Mar 26 19:56 btmp
-rw-r–r-- 1 root root 3552 Mar 26 20:03 dpkg.log
-rw-rw-r-- 1 root utmp 292292 Mar 26 20:00 lastlog
drwxr-xr-x 2 minidlna minidlna 60 Mar 26 20:03 minidlna
-rw-r–r-- 1 volumio volumio 144585 Mar 26 20:31 minidlna.log
-rw-r–r-- 1 root root 60 Mar 26 19:58 mpd.log
drwx------ 2 root root 40 Mar 26 19:56 private
drwxr-xr-x 3 root root 180 Mar 26 19:57 samba
-rw-rw-r-- 1 root utmp 1920 Mar 26 20:00 wtmp
Found the problem. Network interface was set to eth0, wlan0. Removed wlan0 and now the server stays up. This may be an older problem, but I suppose MiniDLNA cannot run on two interfaces at the same time. It’s interesting that the problem manifests itself with the logging interval. And annoyingly, there are not error messages regarding multiple network interfaces.