Did you set the correct path to the music files on the config page of the miniDLNA plugin?,
yes, indeed the music library was active and accessible; then it lost suddenly with no reason
What was the version of the miniDLNA plugin before you tried to update?:
v1.1.4
Can you still enable / disable the plugin?
no, when I try to enable /disable, on the up screen corner appear this red alert message .
"miniDLNA
Failed: stop minidlna.service : Error: Command failed: /usr/bin/sudo /bin/systemctl stop minidlna.service Failed to stop minidlna.service: Unit minidlna.service not loaded.
Are you able to connect to Volumio via SSH?
Really I don´t know how to able via SSH, or what is the razon to use that SSH protocol. DLNA worked fine for a couple a weeks, suddenly DLNA server didn´t find any file and worse, the plugin is stuck, it can´t uninstalling, updating, etc. this really has been a thorn in the ass.
volumio@zerling:~$ ls -al /etc/systemd/system/
total 24
drwxr-xr-x 1 root root 4096 Aug 25 15:27 .
drwxr-xr-x 1 root root 4096 Nov 20 2018 …
lrwxrwxrwx 1 root root 40 Feb 20 2019 dbus-org.freedesktop.Avahi.service -> /lib/systemd/system/avahi-daemon.service
drwxr-xr-x 2 root root 38 Feb 20 2019 default.target.wants
drwxr-xr-x 2 root root 41 Feb 20 2019 getty.target.wants
drwxr-xr-x 2 root root 80 Feb 20 2019 halt.target.wants
drwxr-xr-x 1 root root 4096 May 7 07:17 multi-user.target.wants
drwxr-xr-x 2 root root 80 Feb 20 2019 poweroff.target.wants
drwxr-xr-x 2 root root 80 Feb 20 2019 reboot.target.wants
drwxr-xr-x 2 root root 60 Feb 20 2019 sockets.target.wants
drwxr-xr-x 2 root root 43 Feb 20 2019 sysinit.target.wants
volumio@zerling:~$ systemctl status -l minidlna.service
● minidlna.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
volumio@zerling:~$
The file minidlna.service is missing from /etc/systemd/system. Please create it like this:
Open the editor nano: sudo nano /etc/systemd/system/minidlna.service
Paste the following lines into it:
[Unit]
Description=MiniDLNA UPnP-A/V and DLNA media server
After=syslog.target var-run.mount nss-lookup.target network.target remote-fs.target local-fs.target
volumio@zerling:~$ sudo systemctl start minidlna.service
Failed to start minidlna.service: Unit minidlna.service failed to load: Invalid argument. See system logs and ‘systemctl status minidlna.service’ for details.
volumio@zerling:~$ systemctl status -l minidlna.service
● minidlna.service - MiniDLNA UPnP-A/V and DLNA media server
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
Aug 25 21:05:36 zerling systemd[1]: [/etc/systemd/system/minidlna.service:8] Executable path is not absolute, ignoring: $minidlnad -P /var/run/minidlna/minidlnad.pid -f /data/minidlna.conf
Aug 25 21:05:36 zerling systemd[1]: minidlna.service lacks both ExecStart= and ExecStop= setting. Refusing.
Aug 25 21:05:36 zerling systemd[1]: [/etc/systemd/system/minidlna.service:8] Executable path is not absolute, ignoring: $minidlnad -P /var/run/minidlna/minidlnad.pid -f /data/minidlna.conf
Aug 25 21:05:36 zerling systemd[1]: minidlna.service lacks both ExecStart= and ExecStop= setting. Refusing.
Aug 25 21:05:36 zerling systemd[1]: [/etc/systemd/system/minidlna.service:8] Executable path is not absolute, ignoring: $minidlnad -P /var/run/minidlna/minidlnad.pid -f /data/minidlna.conf
Aug 25 21:05:36 zerling systemd[1]: minidlna.service lacks both ExecStart= and ExecStop= setting. Refusing.
Aug 25 21:17:29 zerling systemd[1]: [/etc/systemd/system/minidlna.service:8] Executable path is not absolute, ignoring: $minidlnad -P /var/run/minidlna/minidlnad.pid -f /data/minidlna.conf
Aug 25 21:17:29 zerling systemd[1]: minidlna.service lacks both ExecStart= and ExecStop= setting. Refusing.
Aug 25 21:18:44 zerling systemd[1]: [/etc/systemd/system/minidlna.service:8] Executable path is not absolute, ignoring: $minidlnad -P /var/run/minidlna/minidlnad.pid -f /data/minidlna.conf
Aug 25 21:18:44 zerling systemd[1]: minidlna.service lacks both ExecStart= and ExecStop= setting. Refusing.
volumio@zerling:~$
volumio@zerling:~$ sudo systemctl start minidlna.service
volumio@zerling:~$ volumio@zerling:~$ sudo systemctl start minidlna.service
Active: inactive (dead)
Sorry, my bad… Please open minidlna.service with nano:
sudo nano /etc/systemd/system/minidlna.service
Then change the line beginning with ExecStart to ExecStart=/usr/bin/minidlnad -P /var/run/minidlna/minidlnad.pid -f /data/minidlna.conf
save the file as described above and try starting the plugin again…
Ok, the attempt(s) to uninstall the plugin seem(s) to have removed already the installed software packages.
Please post the results of ls -al /data/plugins/miscellanea/minidlna
and ls -al /data/configuration/miscellanea/minidlna
in order to check if theses folders have also been removed.
Check if /etc/systemd/system/minidlna.service still exists and has the content posted previously. If so try to start the plugin and maybe check the status of minidlna.service again.
Edit:@jepinzonh and I have worked it out using PM. The issue has been solved by manually reinstalling the missing software as proposed above. Last remaining culprit was to correct the minidlna.service file whose content had an error that initially crept into my post (which has already been edited and corrected).
Please enable SSH and log in to Volumio as described 