View Issue Details

IDProjectCategoryView StatusLast Update
0005249Kali Linux[All Projects] Kali Package Bugpublic2019-02-14 14:02
ReporterbroomdodgerAssigned Tosbrun 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Versionkali-dev 
Target VersionFixed in Version 
Summary0005249: minissdpd package post-installation script subprocess returned error
DescriptionSetting up minissdpd (1.5.20180223-5) ...
/var/lib/dpkg/info/minissdpd.config: 47: /var/lib/dpkg/info/minissdpd.config: /sbin/ifconfig: not found
Job for minissdpd.service failed because the control process exited with error code.
See "systemctl status minissdpd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript minissdpd, action "restart" failed.
● minissdpd.service - keep memory of all UPnP devices that announced themselves
   Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-02-11 09:04:14 PST; 11ms ago
     Docs: man:minissdpd(1)
  Process: 6578 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper ${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, status=1/FAILURE)

Feb 11 09:04:14 toshi systemd[1]: Starting keep memory of all UPnP devices that announced themselves...
Feb 11 09:04:14 toshi minissdpd-systemd-wrapper[6578]: Usage: /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i <interface> [-i <interface2>] ...
Feb 11 09:04:14 toshi minissdpd-systemd-wrapper[6578]: <interface> is either an IPv4 address with mask such as
Feb 11 09:04:14 toshi minissdpd-systemd-wrapper[6578]: 192.168.1.42/255.255.255.0, or an interface name such as eth0.
Feb 11 09:04:14 toshi minissdpd-systemd-wrapper[6578]: By default, socket will be open as /var/run/minissdpd.sock
Feb 11 09:04:14 toshi minissdpd-systemd-wrapper[6578]: and pid written to file /var/run/minissdpd.pid
Feb 11 09:04:14 toshi systemd[1]: minissdpd.service: Control process exited, code=exited, status=1/FAILURE
Feb 11 09:04:14 toshi systemd[1]: minissdpd.service: Failed with result 'exit-code'.
Feb 11 09:04:14 toshi 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)
Steps To Reproduceerror occurs during:
update
upgrade
Additional Informationuname -a
Linux 4.19.0-kali1-amd64 0000001 SMP Debian 4.19.13-1kali1 (2019-01-03) x86_64 GNU/Linux

cat /etc/*rel*
DISTRIB_ID=Kali
DISTRIB_RELEASE=kali-rolling
DISTRIB_CODENAME=kali-rolling
DISTRIB_DESCRIPTION="Kali GNU/Linux Rolling"
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2019.1"
VERSION_ID="2019.1"
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"

Activities

broomdodger

2019-02-12 00:14

reporter   ~0010286

more info:
" .......1.........2.........3.........4.........5.........6....

sudo systemctl status minissdpd.service

● minissdpd.service - keep memory of all UPnP devices that announced themselves
   Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-02-11 16:02:45 PST; 43s ago
     Docs: man:minissdpd(1)
  Process: 2275 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper ${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, status=1/FAILURE)

Feb 11 16:02:45 toshi systemd[1]: Starting keep memory of all UPnP devices that announced themselves...
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: Usage: /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i <interface> [-i <interface2>] ...
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: <interface> is either an IPv4 address with mask such as
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: 192.168.1.42/255.255.255.0, or an interface name such as eth0.
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: By default, socket will be open as /var/run/minissdpd.sock
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: and pid written to file /var/run/minissdpd.pid
Feb 11 16:02:45 toshi systemd[1]: minissdpd.service: Control process exited, code=exited, status=1/FAILURE
Feb 11 16:02:45 toshi systemd[1]: minissdpd.service: Failed with result 'exit-code'.
Feb 11 16:02:45 toshi systemd[1]: Failed to start keep memory of all UPnP devices that announced themselves.

" .......1.........2.........3.........4.........5.........6....

sudo journalctl -xe

-- Subject: A start job for unit minissdpd.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit minissdpd.service has begun execution.
--
-- The job identifier is 876.
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: Usage: /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i <interface> [-i <interface2>] ...
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: <interface> is either an IPv4 address with mask such as
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: 192.168.1.42/255.255.255.0, or an interface name such as eth0.
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: By default, socket will be open as /var/run/minissdpd.sock
Feb 11 16:02:45 toshi minissdpd-systemd-wrapper[2275]: and pid written to file /var/run/minissdpd.pid
Feb 11 16:02:45 toshi systemd[1]: minissdpd.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit minissdpd.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Feb 11 16:02:45 toshi systemd[1]: minissdpd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit minissdpd.service has entered the 'failed' state with result 'exit-code'.
Feb 11 16:02:45 toshi systemd[1]: Failed to start keep memory of all UPnP devices that announced themselves.
-- Subject: A start job for unit minissdpd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit minissdpd.service has finished with a failure.
--
-- The job identifier is 876 and the job result is failed.
Feb 11 16:02:56 toshi sudo[2124]: pam_unix(sudo:session): session closed for user root
Feb 11 16:03:00 toshi NetworkManager[420]: <info> [1549929780.0662] device (wlan0): set-hw-addr: set MAC address to 3A:4F:D9:7A:52:57 (scanning)
Feb 11 16:03:00 toshi kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 11 16:03:00 toshi NetworkManager[420]: <info> [1549929780.2197] device (wlan0): supplicant interface state: inactive -> disabled
Feb 11 16:03:00 toshi NetworkManager[420]: <info> [1549929780.2363] device (wlan0): supplicant interface state: disabled -> inactive
Feb 11 16:03:00 toshi wpa_supplicant[471]: wlan0: Reject scan trigger since one is already pending
Feb 11 16:03:29 toshi sudo[2291]: tech : TTY=pts/0 ; PWD=/home/tech ; USER=root ; COMMAND=/bin/systemctl status minissdpd.service
Feb 11 16:03:29 toshi sudo[2291]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 11 16:03:29 toshi sudo[2291]: pam_unix(sudo:session): session closed for user root
Feb 11 16:04:13 toshi sudo[2294]: tech : TTY=pts/0 ; PWD=/home/tech ; USER=root ; COMMAND=/bin/journalctl -xe
Feb 11 16:04:13 toshi sudo[2294]: pam_unix(sudo:session): session opened for user root by (uid=0)
lines 2449-2493/2493 (END)

" .......1.........2.........3.........4.........5.........6....

sbrun

2019-02-12 09:02

manager   ~0010291

The package net-tools that provides /sbin/ifconfig is not installed.
minissdpd should depend on that. The bug has already been reported in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921736
It should be fixed soon.
In the meantime you have to install the package net-tools manually.

broomdodger

2019-02-12 15:06

reporter   ~0010292

installing net-tools stopped the error

sbrun

2019-02-14 14:02

manager   ~0010305

fixed in new version 1.5.20180223-6

Issue History

Date Modified Username Field Change
2019-02-11 17:44 broomdodger New Issue
2019-02-12 00:14 broomdodger Note Added: 0010286
2019-02-12 09:02 sbrun Assigned To => sbrun
2019-02-12 09:02 sbrun Status new => acknowledged
2019-02-12 09:02 sbrun Note Added: 0010291
2019-02-12 15:06 broomdodger Note Added: 0010292
2019-02-14 14:02 sbrun Status acknowledged => resolved
2019-02-14 14:02 sbrun Resolution open => fixed
2019-02-14 14:02 sbrun Note Added: 0010305