DLNA not running on Amahi 7
Section 1: DLNA Configuration Issue
1. DLNA installed just fine but would not start on boot.
2. I noticed that the miniDLNA config file is in /etc as minidlna.conf. On the F14 version of Amahi it is in the /var/hda... directory structure as amahi.conf. Is this the new way or is this going to change?
3. I looked into the minidlna.conf file and found that the network interface was pointing to eth0 which is different under A7 installs. The old production amahi.conf has it commented out (see attachment).
4. In the minidlna.conf the directories were not mapped correctly. The old amahi.conf uses the filesystems absolute path to /var/hda/files...
5. So I basically took my old amahi.conf file from my production system and named it to minidlna.conf. Placed it on my A7 test box. Did a manual restart on the minidlna application.
6. A7 control panel showed DLNA as running.
7. I was able to stream an mp4 video to my WD TV box and my Googe Nexus 7 tablet.
8. I did a system restart.
9. DLNA showed stopped in the A7 control panel.
10. I did a command line start on minidlna. DLNA shows running in A7 control panel.
11. Again, I was able to stream an mp4 video to my WD TV box and my Googe Nexus 7 tablet.
Section 2: DLNA Boot-up Issue
1. I made sure that DLNA was enabled to start on system boot:
systemctl enable minidlna.service
2. After reboot DLNA still not running, entered command:
systemctl status minidlna.service
minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Sat 2013-08-10 08:46:45 MDT; 16min ago
Process: 527 ExecStart=/usr/sbin/minidlna -f /etc/minidlna.conf -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
Aug 10 08:46:45 localhost systemd1: Starting MiniDLNA is a DLNA/UPnP-AV server software...
Aug 10 08:46:45 localhost systemd1: minidlna.service: control process exited, code=exited status=255
Aug 10 08:46:45 localhost systemd1: Failed to start MiniDLNA is a DLNA/UPnP-AV server software.
Aug 10 08:46:45 localhost systemd1: Unit minidlna.service entered failed state.
3. Checked /var/log/messages and found:
Aug 10 09:20:28 localhost minidlna526: [2013/08/10 09:20:28] minidlna.c:753: fatal: No IP address automatically detected!
4. Carefully checking with Dr. Google lead to the following items:
What does this all mean? DLNA loads faster before the network services are up and running properly. As result DLNA cannot find the server IP address.
5. The fix?
Enable NetworkManager Wait Online
If you have services which fail if they are started before the network is up, you have to use NetworkManager-wait-online.service in addition to the NetworkManager service. This is however hardly ever necessary since most network daemons start up fine, even if the network has not been configured yet.
You can enable NetworkManager Wait Online at startup with the following command:
- systemctl enable NetworkManager-wait-online
I did the wait-online and DLNA now runs on boot up and streams just fine with the configuration file. So I don't know what you need to do in A7 for these fixes.
NOTE: As of August 5th there was a new minidlna version 1.1. RPMFusion will be doing an rpm package it for F19 shortly.
#2 Updated by northridgegrp about 8 years ago
- File minidlna.conf.works added
Hmm for some reason the default minidlna.conf file that installs does not work. However the one I have attached to this post does. One thing I noticed with the default the network interface references eth0 in Fedora 19 it is em1. However when the network interface line is commented out when DLNA first starts it will go for the first network interface it finds. On the default I did comment it out but DLNA did not work. When I supplied (from my production box) my version it works.
#3 Updated by bigfoot65 about 8 years ago
That is interesting. On my Amahi 7, it works fine with no modification. It starts, stops, and restarts with no problems.
When did you install Amahi 7? There have been several changes to the platform that might require a reinstall. Not saying that is the problem, but odd that it works for me and not you.
#4 Updated by cpg about 8 years ago
- Subject changed from DLNA No Running on Amahi 7 to DLNA not running on Amahi 7
- Target version set to amahi-7-0
In the past we made custom modifications to the DLNA package to fix
things that have been bad, add the log, etc.
As such, we built an RPM package for it for and it was all fixed in that.
Looks like the systemctl service file in the server is not built
properly to require the network before starting. I am not too comfy
changing that in the install script, but it could be done. The
downside of doing it via the standard package and a "fix" via the
install script is that any updates upstream could break the app.
Finally, we used to have monit on top that would cover cases like this
too, for extra insurance. If the app crashed, it would restart it.
Is that not part of this app now?
#5 Updated by northridgegrp about 8 years ago
As per previous discussions I install F19 and A7 on my 64 bit test machine, without doing any yum updates. I installed DLNA. Per default A7 /etc/minidlna.conf configured network interface as "eth0".
Now regarding items in this bug report:
: DLNA Boot-up Issue
DLNA was still not running after boot up. Per previous discovery and testing I entered in to a terminal session as the root user, "systemctl enable NetworkManager-wait-online". After system reboot DLNA runs. Also per parallel testing by bigfoot65 not all F19/A7 systems are not effected by this issue.
: DLNA Configuration Issue
Per previous discussion, Amahi Package Manager changed settings in default A7 /etc/minidlna.conf file. I did testing with the default conf file and was able to play videos to a WD TV Live and Google Nexus 7 successfully.
Given that not all systems are effected by the "DLNA Boot-up Issue" I will update the Amahi DLNA Wiki article to show how to troubleshoot and repair this issue.
So I guess this bug report can now be closed?
#7 Updated by northridgegrp about 8 years ago
- Status changed from Closed to Feedback
- Target version changed from amahi-7-0 to amahi-7-1
I just DLNA on my Pentium 4 test machine and it runs fine after boot up. So the network interface problem I had on the other machine is probably unique to the hardware/software configuration I was using at the time. So now we know what to do if a problem of that nature crops up again.
Also available in: Atom