Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 483780 - net-misc/minidlna-1.1.0-r3: systemd failed to start minidlna
Summary: net-misc/minidlna-1.1.0-r3: systemd failed to start minidlna
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal with 2 votes (vote)
Assignee: Michał Górny
Depends on:
Reported: 2013-09-05 18:42 UTC by Dmitry
Modified: 2018-11-25 10:15 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry 2013-09-05 18:42:36 UTC

I've installed last available minidlna for amd64 platform.
If I start minidlna then it fails:

# systemctl start minidlna.service
Job for minidlna.service failed. See 'systemctl status minidlna.service' and 'journalctl -xn' for details.

There are messages in logs:

Sep 05 22:20:59 srv systemd[1]: Starting MiniDLNA is a DLNA/UPnP-AV server software...
Sep 05 22:20:59 srv minidlnad[7292]: utils.c:271: warn: make_dir: cannot create directory '/var/run/minidlna'
Sep 05 22:20:59 srv minidlnad[7292]: minidlna.c:447: error: Unable to create pidfile directory: /var/run/minidlna/

It fails to create directory because minidlna run as separate user minidlna.

Please consider option -S for minidlnad. That option for systemd:
     -S changes behaviour for systemd
With that option it is possible (I think) to remove from After= section in minidlna.service file.

Thank you.
Comment 1 Dmitry 2013-09-05 19:16:58 UTC
It is possible to add file to /etc/tmpfiles.d containing line like that:

d       /run/minidlna   0755    minidlna        minidlna        -  

This will create directory for minidlna.
Comment 2 Dmitry 2013-09-05 19:30:04 UTC
It seems like minidlna supports systemd (option -S) and it is not required to specify Type=forking and PIDFile=... in minidlna.service, but minidlna always creates pid file.
Comment 3 Michael Weber (RETIRED) gentoo-dev 2013-09-05 20:05:40 UTC
Please don't CC maintainers, just wait for bug-wranglers to assign.
Comment 4 Michael Weber (RETIRED) gentoo-dev 2013-09-05 20:27:42 UTC
Hello Dmitry,

can you please check if the new version works as expected, i've modified 

+*minidlna-1.1.0-r3 (05 Sep 2013)
+  05 Sep 2013; Michael Weber <> +files/minidlna-1.1.0-r3.initd,
+  +files/minidlna-1.1.0-r3.service, +minidlna-1.1.0-r3.ebuild:
+  Revbump to fix systemd support (thanks Dmitry, bug 483780).Revbump to fix
+  systemd support (thanks Dmitry, bug 483780).

--- files/minidlna-1.1.0.service        2013-05-12 00:19:45.000000000 +0200
+++ files/minidlna-1.1.0-r3.service     2013-09-05 22:21:04.024389381 +0200
@@ -5,9 +5,7 @@
-ExecStart=/usr/sbin/minidlnad -f /etc/minidlna.conf -P /var/run/minidlna/
+ExecStart=/usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/ -S

--- minidlna-1.1.0-r2.ebuild    2013-06-25 21:47:43.511712234 +0200
+++ minidlna-1.1.0-r3.ebuild    2013-09-05 22:25:35.000000000 +0200
@@ -65,8 +65,10 @@
        doins ${PN}.conf
        newconfd "${FILESDIR}"/${PN}-1.0.25.confd ${PN}
-       newinitd "${FILESDIR}"/${PN}-1.1.0.initd ${PN}
-       systemd_newunit "${FILESDIR}"/${PN}-1.1.0.service ${PN}.service
+       newinitd "${FILESDIR}"/${PF}.initd ${PN}
+       systemd_newunit "${FILESDIR}"/${PF}.service ${PN}.service
+       echo "d /run/${PN} 0755 ${PN} ${PN} -" > "${T}"/${PN}.conf
+       systemd_dotmpfilesd "${T}"/${PN}.conf
        dodir /var/{lib,log}/${PN}
        fowners ${PN}:${PN} /var/{lib,log}/${PN}
Comment 5 Dmitry 2013-09-06 07:00:45 UTC
Thank you! This works fine if I start/stop service manually. But I can't fix problem at startup. If I enable service 'systemctl enable minidlna' then it [minidlna] will fail during boot (after restart of computer):

minidlna.c:528: No MAC address found.  Falling back to generic UUID.
minidlna.c:927: fatal: No IP address automatically detected!
systemd[1]: Unit minidlna.service entered failed state.

I have tried to add to minidlna.service but this doesn't help. 

Thank you!
Comment 6 Dmitry 2013-09-06 07:26:13 UTC
Temporary solution is add line 'ExecStartPre=/bin/sleep 10' to minidlna.service.
Comment 7 Michael Weber (RETIRED) gentoo-dev 2013-09-06 08:35:04 UTC
I hand this over to systemd maintainers for solving the dependency issue. I cannot test it on my environment. Thanks

The .service file is at
Comment 8 Mike Gilbert gentoo-dev 2013-09-06 14:16:07 UTC
(In reply to Dmitry from comment #5)

What do you use to configure your network interfaces?
Comment 9 Dmitry 2013-09-06 14:20:08 UTC
I'm new to Gentoo and I have installed dhcpcd to make network working on my home mini media server.
Comment 10 Mike Gilbert gentoo-dev 2013-09-06 14:41:21 UTC
Maybe try adding; that will at least ensure that dhcpcd is started before minidlna; it still might not have the interface configured, however.

Support for seems pretty spotty at this time.
Comment 11 Dmitry 2013-09-06 14:45:10 UTC already specified and it isn't help. It seems is intended for handle moment when network becomes working.
Comment 12 Mike Gilbert gentoo-dev 2013-09-06 14:57:13 UTC
Ok, ons solution would be to change dhcpcd.service work in forking mode and pass it the --waitip command line option.

     -w, --waitip
             Wait for an address to be assigned before forking to the background.

It should also have added.
Comment 13 Mike Gilbert gentoo-dev 2013-09-06 16:39:25 UTC
Can you try replacing dhcpcd.service with the unit below?

Description=Lightweight DHCP client daemon

# Pass --waitip so we can provide a sync point for
# Requres forking mode.
ExecStart=/sbin/dhcpcd --quiet --waitip

Comment 14 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2013-09-06 16:41:07 UTC
How would that work when networking is unavailable (e.g. the cable is disconnected)?
Comment 15 Mike Gilbert gentoo-dev 2013-09-06 16:48:11 UTC
(In reply to Michał Górny from comment #14)
> How would that work when networking is unavailable (e.g. the cable is
> disconnected)?

Good question. I'm not sure how --waitpid works if it cannot find a working connection.

Worst case, it times out after 90 seconds (systemd's limit).

We might want to add this as an alternative unit (dhcpcd-wait.service) so that we don't introduce delays for everybody.

Of course, ideally software would respond to network configuration changes. ^_^