Mini dlna plugin error

Volumio Information

Volumio Version: 2.555
Hardware: Raspberry Pi 3b
DAC:AOIDE HIFI DIGI PRO + DAC FX X6

Hello Everyone, I have really issues with Mini DLNA Plugin. the DLNA server can´t find any music file of my SSD External Disc connected to the USB Raspberry port… I tried to update the MINI DLNA Plugin, and reinstall but volumio shows an persistent error (1), I tried too of Uninstall de Plugin but is not possible (2).
1:
" Updating plugin

The following error occurred when installing the plugin: Error: on stopping miniDLNA plugin

0%

- Ocultar Detalles

Downloading plugin at http://plugins.volumio.org/plugins/volumio/armhf/miscellanea/minidlna/minidlna.zip
END DOWNLOAD: http://plugins.volumio.org/plugins/volumio/armhf/miscellanea/minidlna/minidlna.zip
Creating folder on disk
The following error occurred when installing the plugin: Error: on stopping miniDLNA plugin"

2: Uninstalling plugin:

"An error occurred uninstalling the plugin. Details: Error: on stopping miniDLNA plugin

Can anyone help me, about this problem.

Hi @jepinzonh,

Did you set the correct path to the music files on the config page of the miniDLNA plugin?

What was the version of the miniDLNA plugin before you tried to update?

Can you still enable / disable the plugin?

Are you able to connect to Volumio via SSH?

Hello m friend.
In reply your questions:

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.

I don´t know how fix the problem.

This did happen before you tried to update the plugin, right?

It is useful to SSH into Volumio in order to get your issue solved :wink: Please enable SSH and log in to Volumio as described here.

Then post the results of
ls -al /etc/systemd/system/
and
systemctl status -l minidlna.service

1 Like

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:~$

Look the results

The file minidlna.service is missing from /etc/systemd/system. Please create it like this:

  1. Open the editor nano:
    sudo nano /etc/systemd/system/minidlna.service

  2. 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

    [Service]
    Type=forking
    PIDFile=/var/run/minidlna/minidlnad.pid
    ExecStart=/usr/bin/minidlnad -P /var/run/minidlna/minidlnad.pid -f /data/minidlna.conf
    StandardOutput=syslog
    StandardError=syslog
    SyslogIdentifier=volumio
    User=root
    Group=volumio

    [Install]
    WantedBy=multi-user.target

  3. Save the file by pressing Ctrl-x, y and Enter.

  4. Try to enable the plugin.

EDIT: Corrected ExecStart= line.

Thank you man…I followed every pass sucesfully, however Mini DLAN still no working.

-trying to able / disable shows:
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.

trying to update:

Downloading plugin at http://plugins.volumio.org/plugins/volumio/armhf/miscellanea/minidlna/minidlna.zip
END DOWNLOAD: http://plugins.volumio.org/plugins/volumio/armhf/miscellanea/minidlna/minidlna.zip
Creating folder on disk
The following error occurred when installing the plugin: Error: on stopping miniDLNA plugin

trying to uninstall:

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.

:sweat:

Check that minidlna.service is still present in /etc/systemd/system and try to start the service manually with sudo systemctl start minidlna.service

Also check what systemctl status -l minidlna.service yields now.

1 Like

look the results.

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…

no man… the problem persist

Is the result of systemctl status -l minidlna.service the same as posted above?

Please execute whereis -b minidlnad to check if the minidlna binary is present.

Is the result of systemctl status -l minidlna.service the same as posted above? yes. bad results

Please execute whereis -b minidlnad to check if the minidlna binary is present…
Do I must execute this code on sudo nano?

No, just from the command line.

The results on command line:
volumio@zerling:~$ whereis -b minidlnad
minidlnad:
volumio@zerling:~$

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.

volumio@zerling:~$ ls -al /data/plugins/miscellanea/minidlna
total 104
drwxr-xr-x 4 volumio volumio 4096 Jun 15 18:23 .
drwxr-xr-x 3 volumio volumio 4096 Jun 15 18:20 …
-rw-r–r-- 1 volumio volumio 35626 Dec 19 2019 UIConfig.json
-rw-r–r-- 1 volumio volumio 2316 Jun 15 18:23 config.json
-rw-r–r-- 1 volumio volumio 29 Dec 19 2019 gitignore
drwxr-xr-x 2 volumio volumio 4096 Jun 15 18:20 i18n
-rw-r–r-- 1 volumio volumio 11390 Dec 19 2019 index.js
-rw-r–r-- 1 volumio volumio 963 Dec 19 2019 install.sh
-rw-r–r-- 1 volumio volumio 5779 Dec 19 2019 minidlna.conf.tmpl
-rw-r–r-- 1 volumio volumio 440 Dec 19 2019 minidlna.service
drwxr-xr-x 12 volumio volumio 4096 Jun 15 18:20 node_modules
-rw-r–r-- 1 volumio volumio 2981 Dec 19 2019 package-lock.json
-rw-r–r-- 1 volumio volumio 447 Dec 19 2019 package.json
-rw-r–r-- 1 volumio volumio 5 Dec 19 2019 requiredConf.json
-rw-r–r-- 1 volumio volumio 370 Dec 19 2019 uninstall.sh
volumio@zerling:~$ ls -al /data/configuration/miscellanea/minidlna
total 12
drwxr-xr-x 2 volumio volumio 4096 Aug 25 15:34 .
drwxr-xr-x 8 volumio volumio 4096 Aug 25 15:34 …
-rw-r–r-- 1 volumio volumio 2315 Aug 25 18:32 config.json
volumio@zerling:~$

So, the plugin’s files still exist. You could try to reinstall the missing software with:

sudo apt-get update
sudo apt-get -y install minidlna
sudo rm /etc/minidlna.conf
sudo chown -R volumio:volumio /var/cache/minidlna/

Then make another attempt on enabling the plugin. For the moment don’t try to uninstall the plugin.

[quote=“gvolt, post:18, topic:40832”]
sudo apt-get update
Each command one by one? or copy all lines at same time?

One by one. Wait until each command has finished executing.