Re: minissdpd failure in update
- Date: Thu, 1 Feb 2018 21:57:43 +0100
- From: Sven Hartge <sven@xxxxxxxxxxxxx>
- Subject: Re: minissdpd failure in update
Sven Joachim <svenjoac@xxxxxx> wrote:
> On 2018-02-01 19:55 +0100, Sven Hartge wrote:
>> Frank M <debianlist@xxxxxxxxxxxx> wrote:
>>> Feb 01 13:39:07 franklin minissdpd: Error: please specify LAN
>>> network interface by name instead of IPv4 address : 0.0.0.0
>>> Feb 01 13:39:07 franklin minissdpd: can't parse "0.0.0.0" as a
>>> valid address or interface name
>> Your configuration is broken/wrong. You need to edit
>> /etc/default/minissdpd and put the correct IP or device name into the
>> variable "MiniSSDPd_INTERFACE_ADDRESS".
> There is no /etc/default/minissdpd in the package anymore.
# dpkg -L minissdpd | grep "/etc/default/minissdpd"
# dpkg -l minissdpd
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
ii minissdpd:amd64 1.5.20161216-1 amd64 keep memory of all UPnP devices that announ
> See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889028.
Also the /lib/systemd/system/minissdpd.service requires
/etc/default/minissdpd because this file is not marked as optional.
So the file must exist or the unit itself would fail.
Which it will when installed on a system where it has never been
| Feb 01 21:51:37 HOST systemd: minissdpd.service: Failed to load environment files: No such file or directory
| Feb 01 21:51:37 HOST systemd: minissdpd.service: Failed to run 'start' task: No such file or directory
| Feb 01 21:51:37 HOST systemd: minissdpd.service: Failed with result 'resources'.
| Feb 01 21:51:37 HOST systemd: Failed to start keep memory of all UPnP devices that announced themselves.
But if installed on a system where the older version was installed,
/etc/default/minissdpd still exists:
| # MiniSSDPd default configuration
| # Set this to 1 if you want to start the daemon
| # Set this to the IP of the interface you want the demon to run on
Note the wrong "MiniSSDPd_INTERFACE_ADDRESS". Version
1.2.20130907-4.1 doesn't seem to mind the "0.0.0.0" here and starts
Only after upgrading to 1.5.20161216-1 it barfs and fails.
There are really two errors at play here, depending on from where you
a) 1.2.20130907-4.1 was upgraded to 1.5.20161216-1:
Error because 0.0.0.0 is no longer correct.
b) 1.5.20161216-1 is the first version
unit fails, because /etc/default/minissdpd does not exist.
Solution in all cases is: Create a correct /etc/default/minissdpd.
Sigmentation fault. Core dumped.