Re: minissdpd failure in update

2019-11-22 Thread Greg Wooledge
On Fri, Nov 22, 2019 at 01:06:25PM +1100, isaac wrote: > minissdpd.service - keep memory of all UPnP devices that announced > themselves >Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; > vendor preset: enabled) >Active: failed (Result: exit-code) since Thu 2019-11-21

Re: minissdpd failure in update

2019-11-21 Thread isaac
minissdpd.service - keep memory of all UPnP devices that announced themselves Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-11-21 22:54:39 AEDT; 12ms ago Docs: man:minissdpd(1) Process: 4312

Re: minissdpd failure in update

2019-11-21 Thread Curt
On 2019-11-21, isaac wrote: > minissdpd > E: Sub-process /usr/bin/dpkg returned an error code (1) > root@Isaac:/home/isaac# > > can you help me why minissdpd is not working. You might try dpkg-reconfigure minissdpd and if that fails, the Reddit fellow below purged the package, reinstalled

Re: minissdpd failure in update

2019-11-21 Thread Greg Wooledge
On Thu, Nov 21, 2019 at 11:03:42PM +1100, isaac wrote: > minissdpd.service - keep memory of all UPnP devices that announced > themselves >Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; > vendor preset: enabled) >Active: failed (Result: exit-code) since Thu 2019-11-21

Re: minissdpd failure in update

2019-11-21 Thread isaac
minissdpd.service - keep memory of all UPnP devices that announced themselves Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-11-21 22:54:39 AEDT; 12ms ago Docs: man:minissdpd(1) Process: 4312

Re: minissdpd failure in update

2018-02-01 Thread Frank M
On 02/01/2018 03:57 PM, Sven Hartge wrote: Sven Joachim wrote: On 2018-02-01 19:55 +0100, Sven Hartge wrote: Frank M wrote: Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN network interface by name instead of IPv4 address :

Re: minissdpd failure in update

2018-02-01 Thread Sven Hartge
Sven Joachim wrote: > On 2018-02-01 19:55 +0100, Sven Hartge wrote: >> Frank M wrote: >>> Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN >>> network interface by name instead of IPv4 address : 0.0.0.0 >>> Feb 01 13:39:07 franklin

Re: minissdpd failure in update

2018-02-01 Thread Michael Stone
On Thu, Feb 01, 2018 at 07:55:53PM +0100, Sven Hartge wrote: 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". Umm, no. It is expected that a debian package will not self destruct

Re: minissdpd failure in update

2018-02-01 Thread Sven Joachim
On 2018-02-01 19:55 +0100, Sven Hartge wrote: > Frank M wrote: > >> Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN >> network interface by name instead of IPv4 address : 0.0.0.0 >> Feb 01 13:39:07 franklin minissdpd[9152]: can't parse "0.0.0.0" as a

Re: minissdpd failure in update

2018-02-01 Thread Sven Hartge
Frank M wrote: > Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN > network interface by name instead of IPv4 address : 0.0.0.0 > Feb 01 13:39:07 franklin minissdpd[9152]: can't parse "0.0.0.0" as a > valid address or interface name Your

minissdpd failure in update

2018-02-01 Thread Frank M
Updating my Sid installation this morning. Setting up minissdpd (1.5.20161216-1) ... Installing new version of config file /etc/init.d/minissdpd ... Job for minissdpd.service failed because the control process exited with error code. See "systemctl status minissdpd.service" and "journalctl