Re: minissdpd failure in update
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 22:54:39 > AEDT; 12ms ago > Docs: man:minissdpd(1) > Process: 4312 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper > ${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, > status=1/FAILURE) > > Nov 21 22:54:39 Isaac systemd[1]: Starting keep memory of all UPnP > devices that announced themselves... > Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: Usage: > /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f > device] -i [-i ] ... > can you help me why this error please Not without seeing the systemd unit file and the configuration files that it reads. Has anyone reported a bug on this yet? Have *you* reported a bug on this yet? I see now that there is some information buried in the Subject of your email that may or may not be relevant. I will warn you that many people do not read the Subject headers. Any information that is required to understand or solve your problem should be in the BODY of the email. In your Subject you include the word "update". Does this mean you were trying to update this package? If so, from what version to what version? You really need to provide more information. As I told you previously.
Re: minissdpd failure in update
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 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper ${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, status=1/FAILURE) Nov 21 22:54:39 Isaac systemd[1]: Starting keep memory of all UPnP devices that announced themselves... Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: Usage: /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i [-i ] ... Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]:is either an IPv4 address with mask such as Nov 21 22:54:39 Isaac minissdpd-systemd- wrapper[4312]: 192.168.1.42/255.255.255.0, or an interface name such as eth0. Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: By default, socket will be open as /var/run/minissdpd.sock Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: and pid written to file /var/run/minissdpd.pid Nov 21 22:54:39 Isaac systemd[1]: minissdpd.service: Control process exited, code=exited, status=1/FAILURE Nov 21 22:54:39 Isaac systemd[1]: minissdpd.service: Failed with result 'exit-code'. Nov 21 22:54:39 Isaac systemd[1]: Failed to start keep memory of all UPnP devices that announced themselves. dpkg: error processing package minissdpd (--configure): installed minissdpd package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: minissdpd E: Sub-process /usr/bin/dpkg returned an error code (1) root@Isaac:/home/isaac# can you help me why this error please
Re: minissdpd failure in update
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 it, and then it worked again. Granted, it's a crude method, and thoroughly unenlightening. https://www.reddit.com/r/debian/comments/ba05b5/buster_minissdpd/ There's an outstanding bug for minissdpd concerning IPV6, now apparently switched on by default, creating failures in systems where that protocol is disabled. > Thank you Isaac > > -- “The cradle rocks above an abyss, and common sense tells us that our existence is but a brief crack of light between two eternities of darkness.” "Speak, Memory," Vladimir Nabokov
Re: minissdpd failure in update
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 22:54:39 > AEDT; 12ms ago > Docs: man:minissdpd(1) > Process: 4312 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper > ${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, > status=1/FAILURE) > > Nov 21 22:54:39 Isaac systemd[1]: Starting keep memory of all UPnP > devices that announced themselves... > Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: Usage: > /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f > device] -i [-i ] ... Looks like systemd tried to run the daemon with the wrong arguments, which triggered this usage error message. Has this package previously been installed on your system, or have you copied over a configuration file for this package from another system, or has anything else occurred which might have left a broken configuration file lying around? If so, either fix the configuration file by hand, or purge the package (along with any remaining config files), and try reinstalling it. If that's not it, then this sounds like a bug in the package. You could look for existing bug reports, and see if anyone else has encountered it and has a workaround. Or, you could analyze the systemd unit file and any configuration files that it reads, find out where the problem is, and then report the bug yourself.
Re: minissdpd failure in update
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 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper ${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, status=1/FAILURE) Nov 21 22:54:39 Isaac systemd[1]: Starting keep memory of all UPnP devices that announced themselves... Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: Usage: /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i [-i ] ... Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]:is either an IPv4 address with mask such as Nov 21 22:54:39 Isaac minissdpd-systemd- wrapper[4312]: 192.168.1.42/255.255.255.0, or an interface name such as eth0. Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: By default, socket will be open as /var/run/minissdpd.sock Nov 21 22:54:39 Isaac minissdpd-systemd-wrapper[4312]: and pid written to file /var/run/minissdpd.pid Nov 21 22:54:39 Isaac systemd[1]: minissdpd.service: Control process exited, code=exited, status=1/FAILURE Nov 21 22:54:39 Isaac systemd[1]: minissdpd.service: Failed with result 'exit-code'. Nov 21 22:54:39 Isaac systemd[1]: Failed to start keep memory of all UPnP devices that announced themselves. dpkg: error processing package minissdpd (--configure): installed minissdpd package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: 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. Thank you Isaac
Re: minissdpd failure in update
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 : 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 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. No? See: # dpkg -L minissdpd | grep "/etc/default/minissdpd" /etc/default/minissdpd # dpkg -l minissdpd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture 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. Interesting. 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 installed before: , | Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed to load environment files: No such file or directory | Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed to run 'start' task: No such file or directory | Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed with result 'resources'. | Feb 01 21:51:37 HOST systemd[1]: 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 | START_DAEMON=1 | | # Set this to the IP of the interface you want the demon to run on | MiniSSDPd_INTERFACE_ADDRESS=0.0.0.0 ` 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 without problems. 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 come: 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. Grüße, Sven. How about aptitude purge minissdpd. That's how I fixed it. It only got installed as a recommend of transmission-gtk.
Re: minissdpd failure in update
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 minissdpd[9152]: 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. No? See: # dpkg -L minissdpd | grep "/etc/default/minissdpd" /etc/default/minissdpd # dpkg -l minissdpd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture 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. Interesting. 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 installed before: , | Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed to load environment files: No such file or directory | Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed to run 'start' task: No such file or directory | Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed with result 'resources'. | Feb 01 21:51:37 HOST systemd[1]: 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 | START_DAEMON=1 | | # Set this to the IP of the interface you want the demon to run on | MiniSSDPd_INTERFACE_ADDRESS=0.0.0.0 ` 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 without problems. 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 come: 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. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: minissdpd failure in update
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 on install without manual intervention. That said, it's sid and breakage is expected (and will presumably be fixed). Mike Stone
Re: minissdpd failure in update
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 >> 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. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889028. Cheers, Sven
Re: minissdpd failure in update
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 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". Grüße, Sven. -- Sigmentation fault. Core dumped.