ReadyMedia / Bugs / #306 Minidlna 1.2 Network interface error

Shrimpkin - 2017-06-09

Make sure your network interface is up and configured with an ip address before starting minidlna.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Captain_Commando - 2017-06-09

are you serious? I have used various startup scripts, and I have a static ip assigned to this work station for hosting media from, so yes, the ip is assigned long before minidlna tries to find the interface.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Shrimpkin - 2017-06-09

How can someone else reproduce the bug? Post the steps needed to reproduce the issue. Does the issue exist only on your system or on other systems too? Do you get the same results with a fresh install? In a virtual machine? How about a different distro? You will have to provide more info to post a bug report.

I cannot reproduce your issue on my system or in a VM using Fedora 25. network_interface option works fine.

Three ways which will result in the error:
1) Nonexistent network interface.
2) Network interface is not up.
3) Network interface is up but not configured properly (ip add, etc).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Captain_Commando - 2017-06-10

to reproduce the bug, simply uncomment the line in the conf file. make sure you have verified the correct spelling for your network interface. as for mine, i have TRIPLE checked the spelling, and made SURE that it is up, functioning and assigned a STATIC address. I believe the previous posts on here detailed this same information.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Shrimpkin - 2017-06-10

I cannot reproduce your issue on three different systems. It is most likely an issue with yours. Try seeking support from your distro's support forum.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Captain_Commando - 2017-06-11

please post your results, as output by systemctl status minidlna so that I have proof of concept, and that you have a clear understanding of my original problem. I do not for one second believe that it works fine. Nor do I believe that it is a problem with just my setup, given the number of people having the same issue, as reported in bug 297. You may nat have an adequate understanding of the issue we all are having, with minidlna not listening on the correct Network Interface. Thank you.

Last edit: Captain_Commando 2017-06-11

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Shrimpkin - 2017-06-11

The failure in understanding is yours. The issue reported in 297 is not related to your issue, which was mentioned in that thread.

The problem lies with your system init not with minidlna. minidlna is being started before your network interfaces are up.

Try changing the service section in your systemd config for minidlna to this:

[Service] User=minidlna Group=minidlna Type=oneshot ExecStart=/usr/bin/sleep 60 ExecStart=/usr/sbin/minidlnad -S

See your distro's support forum for a proper fix. Good day, sir.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Captain_Commando - 2017-06-12

I do not believe your solution will solve the original problem that minidlna is ignoring/not recognizing the Network Interface parameter. As asked, please post the output of your tests, that you claim show a proper binding to the selected network interface. Barring production of those test results, I will continue to assert that minidlna is broken, and since you are NOT the codes author, I will respectfully request that you cease and desist your attempts to cover this up as a problem with my distro.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Troll?

grep network_interface /etc/minidlna.conf
network_interface=ens3

ifconfig ens3 | grep -i broadcast
ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255

minidlnad -d -f /etc/minidlna.conf | grep getifaddr
[2017/06/12 06:35:28] getifaddr.c:338: info: Enabling interface 10.0.2.15/255.255.255.0

ps -e | grep minidlnad
 2078 ?        00:00:00 minidlnad

grep network_interface /etc/minidlna.conf
network_interface=foobar

ifconfig -a | grep foobar | wc -l
0

minidlnad -d -f /etc/minidlna.conf | grep getifaddr
[2017/06/12 06:37:48] getifaddr.c:109: error: Network interface foobar not found

Captain_Commando - 2017-06-12

Troll? really? You a child? I have not denigrated your intellect or refered to you with disrespect. GFY.

Your postings do not show proof of load on startup. for all I know you ran from cli after you booted, and were sure that the IF was found. At this point I am done with dealing with you, and your name calling.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Shrimpkin - 2017-06-12

https://en.wikipedia.org/wiki/Systemd

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Minidlna 1.2 Network interface error

Group

Searches

Help

#306 Minidlna 1.2 Network interface error

Discussion