Problem starting miniDLNA Plugin

Quacksalber · Sep 7th 2024

after a reboot, miniDLNA has problems starting.

systemctl status minidlna.service shows:

Code

× minidlna.service - MiniDLNA lightweight DLNA/UPnP-AV server
     Loaded: loaded (/lib/systemd/system/minidlna.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sat 2024-09-07 14:08:19 CEST; 2h 17min ago
   Duration: 723ms
       Docs: man:minidlnad(1)
             man:minidlna.conf(5)
   Main PID: 890 (code=exited, status=255/EXCEPTION)
        CPU: 104ms

Sep 07 14:08:18 data-nas systemd[1]: Started minidlna.service - MiniDLNA lightweight DLNA/UPnP-AV server.
Sep 07 14:08:19 data-nas minidlnad[890]: [2024/09/07 14:08:19] utils.c:295: warn: make_dir: cannot create directory '/var/log/minidlna'
Sep 07 14:08:19 data-nas minidlnad[890]: [2024/09/07 14:08:19] minidlna.c:670: error: Media directory "A,/srv/dev-disk-by-uuid-ef441e85-82a0-4a30-a1b7-c962eb3fd390/long-retention/Multimedia/Musik/_Categorized_/" not accessible [No such >
Sep 07 14:08:19 data-nas minidlnad[890]: [2024/09/07 14:08:19] minidlna.c:670: error: Media directory "A,/srv/dev-disk-by-uuid-ef441e85-82a0-4a30-a1b7-c962eb3fd390/long-retention/Multimedia/Musik/__Playlists-for-miniDLNA__/" not accessi>
Sep 07 14:08:19 data-nas minidlnad[890]: minidlna.c:1028: fatal: Failed to open log file '/var/log/minidlna/minidlna.log': No such file or directory
Sep 07 14:08:19 data-nas systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION
Sep 07 14:08:19 data-nas systemd[1]: minidlna.service: Failed with result 'exit-code'.

Display More

indicating, that is has problems accessing any of the paths.

When I started it manually (after looking into it) with systemctl start minidlna.service, it had no problems at all.

Again output of systemctl status minidlna.service

Code

● minidlna.service - MiniDLNA lightweight DLNA/UPnP-AV server
     Loaded: loaded (/lib/systemd/system/minidlna.service; enabled; preset: enabled)
     Active: active (running) since Sat 2024-09-07 16:47:28 CEST; 48s ago
       Docs: man:minidlnad(1)
             man:minidlna.conf(5)
   Main PID: 131114 (minidlnad)
      Tasks: 3 (limit: 23789)
     Memory: 435.4M
        CPU: 6.908s
     CGroup: /system.slice/minidlna.service
             ├─131114 /usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/minidlna.pid -S -r
             └─131117 /usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/minidlna.pid -S -r

Sep 07 16:47:28 data-nas systemd[1]: Started minidlna.service - MiniDLNA lightweight DLNA/UPnP-AV server.

Display More

Any ideas what I could do?

ryecoaaron · Sep 7th 2024

Quote from Quacksalber

Any ideas what I could do?

It looks like minidlna is starting before your storage is mounted.

Thread

minidlna starts before automount the hard disk

Hello,

and sorry for my translator english.

I use OMV 6 and have problems with the miniDLNA-plugin.
When the NAS is booted, the miniDLNA service is activated before the data disk is recognized.
(Code, 18 lines)

After "service minidlna restart" I get the following display ...
(Code, 16 lines)

After a while, the released data will also be available on the TV.
Now restarting the miniDLNA service via ssh every time the NAS is restarted is not a permanent solution.

Does anyone know of a way to fix this…

orcape

Jan 10th 2022

Quacksalber · Sep 9th 2024

Thanks. I have inserted that "wait loop".

We'll see, what happens...

Quacksalber · Sep 10th 2024

That seems to solve the topic.

Nevertheless, I didn't really like the idea of just putting some arbitrary timer in the startup process.

So I did some further reading on that topic (including the basics of systemd) and I wonder it putting a dependency on multi-user.target would solve that topic.

Has anybody already tied this?

Is there anything obvius that I am missing?

ryecoaaron · Sep 10th 2024

Having a dependency on multi-user.target isn't uncommon. There would be little risk with minidlna. I would just try it.

Quacksalber · Sep 10th 2024

Adding that dependency also solves that issue (at least for me).

Tested with one reboot and one real shut down, waiting some time and bringing the system back up.

theking2 · Feb 16th 2025

so how make the systemv job wait for mouting?

Quacksalber · Feb 19th 2025

well im my case I copied a file into this directory: /etc/systemd/system/minidlna.service.d

Filename is: override.conf

Content of that file is:

Code

[Unit]
After=multi-user.target

#[Service]
#ExecStartPre=/bin/sleep 30
#StartLimitIntervalSec=300s

ryecoaaron · Feb 20th 2025

Quote from Quacksalber

well im my case I copied a file into this directory: /etc/systemd/system/minidlna.service.d
Filename is: override.conf

sudo systemctl edit minidlna will automatically create the directory and open the file for editing.

Quacksalber · Mar 10th 2025

I probably did it that way - I just forgot it.

Thanks for reminding me (and the others).

theking2 · Jun 10th 2025

Quote from ryecoaaron

It looks like minidlna is starting before your storage is mounted.

Thread

minidlna starts before automount the hard disk

Hello,

and sorry for my translator english.

I use OMV 6 and have problems with the miniDLNA-plugin.
When the NAS is booted, the miniDLNA service is activated before the data disk is recognized.
(Code, 18 lines)

After "service minidlna restart" I get the following display ...
(Code, 16 lines)

After a while, the released data will also be available on the TV.
Now restarting the miniDLNA service via ssh every time the NAS is restarted is not a permanent solution.

Does anyone know of a way to fix this…

orcape

Jan 10th 2022

would it be possible to add this to the wiki?

ryecoaaron · Jun 10th 2025

Quote from theking2

would it be possible to add this to the wiki?

What wiki? I don't even recommend people use the minidlna plugin. It only exists because I use it as a reference plugin when porting plugins to the next version of OMV. So, I don't really want to spend to spend the time to write a wiki about it.

Problem starting miniDLNA Plugin

Participate now!

Tags