minissdpd.service not working on Debian Bullseye

Kernels & Hardware, configuring network, installing services

minissdpd.service not working on Debian Bullseye

Postby hihu » 2020-05-03 08:06

Hello I have upgraded my system from Debian Stable to Debian Testing Bullseye. Now after using the package manager I always get errors concerning the minissdpd.service. But I don't know exactly what this service is about. I seems its the package which i not fully installed by the system. This is the error I get.

Code: Select all
root@debian-s0nd:/home/benni# apt autoremove
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  libgtkmm-2.4-1v5 libgtkspell0 python-backports.functools-lru-cache
  python-bs4 python-html5lib python-lxml python-numpy python-pkg-resources
  python-scour python-setuptools python-six python-soupsieve
  python-webencodings scour
0 upgraded, 0 newly installed, 14 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 26,5 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 207018 files and directories currently installed.)
Removing libgtkmm-2.4-1v5:amd64 (1:2.24.5-4) ...
Removing libgtkspell0:amd64 (2.0.16-1.3) ...
Removing python-bs4 (4.8.2-1) ...
Removing python-soupsieve (1.9.5+dfsg-1) ...
Removing python-backports.functools-lru-cache (1.5-3) ...
Removing python-html5lib (1.0.1-2) ...
Removing python-lxml:amd64 (4.5.0-1+b1) ...
Removing python-numpy (1:1.16.5-5) ...
Removing python-setuptools (44.0.0-2) ...
Removing python-scour (0.37-2) ...
Removing python-pkg-resources (44.0.0-2) ...
Removing python-six (1.14.0-3) ...
Removing python-webencodings (0.5.1-1) ...
Removing scour (0.37-4) ...
Setting up minissdpd (1.5.20190210-1+b1) ...
enp9s0 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 pres
et: enabled)
     Active: failed (Result: exit-code) since Sun 2020-05-03 10:34:37 CEST; 13ms
 ago
       Docs: man:minissdpd(1)
    Process: 3563 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper ${MiniS
SDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, status=1/FAILURE)

Mai 03 10:34:37 debian-s0nd systemd[1]: Starting keep memory of all UPnP devices
 that announced themselves...
Mai 03 10:34:37 debian-s0nd minissdpd-systemd-wrapper[3563]: Usage: /usr/sbin/mi
nissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i <interface> [
-i <interface2>] ...
Mai 03 10:34:37 debian-s0nd minissdpd-systemd-wrapper[3563]:   <interface> is ei
ther an IPv4 address with mask such as
Mai 03 10:34:37 debian-s0nd minissdpd-systemd-wrapper[3563]:   192.168.1.42/255.
255.255.0, or an interface name such as eth0.
Mai 03 10:34:37 debian-s0nd minissdpd-systemd-wrapper[3563]:   By default, socke
t will be open as /var/run/minissdpd.sock
Mai 03 10:34:37 debian-s0nd minissdpd-systemd-wrapper[3563]:   and pid written t
o file /var/run/minissdpd.pid
Mai 03 10:34:37 debian-s0nd systemd[1]: minissdpd.service: Control process exite
d, code=exited, status=1/FAILURE
Mai 03 10:34:37 debian-s0nd systemd[1]: minissdpd.service: Failed with result 'e
xit-code'.
Mai 03 10:34:37 debian-s0nd 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
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.30-4) ...
Errors were encountered while processing:
 minissdpd
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian-s0nd:/home/benni#


It seems there is a problem setting it up but I never had to do with this service.
Hope somebody can help me. Thank you very much in advance for some help.
hihu
 
Posts: 13
Joined: 2017-09-22 07:26

Re: minissdpd.service not working on Debian Bullseye

Postby Head_on_a_Stick » 2020-05-03 09:10

hihu wrote:I have upgraded my system from Debian Stable to Debian Testing Bullseye

Why? You do understand that bullseye is a development branch, right? Only people who are interested in helping find and fix bugs and problems for the next Debian stable release should be using that.

See also viewtopic.php?f=12&t=134762&p=655783 & https://www.debian.org/doc/manuals/debi ... .html#s3.1

hihu wrote:Now after using the package manager I always get errors concerning the minissdpd.service

What is the content of /etc/default/minissdpd?

Can we also see the full output of
Code: Select all
# /etc/init.d/minissdpd restart

It is possible to disable the post-install script at /var/lib/dpkg/info/minissdpd.postinst by removing the executable bit but that would be a very dirty hack.
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 12650
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: minissdpd.service not working on Debian Bullseye

Postby hihu » 2020-05-03 15:28

Thank you for the reply. I will switch to the new stable release once its released.

Code: Select all
benni@debian-s0nd:~$ cat /etc/default/minissdpd
# MiniSSDPd default configuration

# Set this to 1 if you want to start the daemon
# START_DAEMON deprecated, use service minissdpd enable/disable
#START_DAEMON=1

# Set this to the IP of the interface you want the demon to run on
MiniSSDPd_INTERFACE_ADDRESS=""
MiniSSDPd_OTHER_OPTIONS=""


Code: Select all
benni@debian-s0nd:~$ /etc/init.d/minissdpd restart
Restarting minissdpd (via systemctl): minissdpd.serviceJob for minissdpd.service failed because the control process exited with error code.
See "systemctl status minissdpd.service" and "journalctl -xe" for details.
 failed!


Code: Select all
benni@debian-s0nd:~$ systemctl status minissdpd.service
● minissdpd.service - keep memory of all UPnP devices that announced themselves
     Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; vendor pre>
     Active: failed (Result: exit-code) since Sun 2020-05-03 18:10:24 CEST; 1mi>
       Docs: man:minissdpd(1)
    Process: 6750 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper ${Mini>


This is the output I'm getting when using the commands.
hihu
 
Posts: 13
Joined: 2017-09-22 07:26

Re: minissdpd.service not working on Debian Bullseye

Postby cuckooflew » 2020-05-03 16:05

It might also be informative to look at https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=minissdpd;dist=unstable
But I don't know exactly what this service is about. I seems its the package which i not fully installed by the system. This is the error I get.

Why don't you try reading about the package before installing it, especiall if you don't even know what it is about ??? It is not logical when one does not do that. That is what the documentation is for
https://packages.debian.org/sid/minissdpd
=================
Hope somebody can help me

Learn how to use a search engine, then you can help your self.
https://lists.debian.org/debian-user/2018/02/msg00037.html
Solution in all cases is: Create a correct /etc/default/minissdpd.

Grüße,
Sven.

=================
http://forums.debian.net/viewtopic.php?f=30&t=47078
It has been a pleasure trying to help you, hope you have learned something :wink:
Please Read What we expect you have already Done
Search Engines know a lot, and
"If God had wanted computers to work all the time, He wouldn't have invented RESET buttons"
and
Just say NO to help vampires!
cuckooflew
 
Posts: 683
Joined: 2018-05-10 19:34
Location: Some where out west

Re: minissdpd.service not working on Debian Bullseye

Postby Francewhoa » 2020-09-27 01:40

I always get errors concerning the minissdpd.service. But I don't know exactly what this service is about.


Feel really free to use minissdpd or not. For much strong securité, I suggest to NOT use minissdpd.

In summary what minissdpd does is that it speeds up device discoveries. For example, if you plug a new device on your Debian, it will be detected faster. The challenge with MiniSSDPd is that, for example, routers, printers, and other devices can be remotely commandeered by a new attack that exploits a security flaw in the Universal Plug and Play network protocol. And MiniSSDPd has a very long history of weak security.

MiniSSDPd is optional. Either deactivating it or fully removing it, would not break anything.

If it is deactivated, the device discoveries will still work fine. But they might be slower though. If you deactivate or remove MiniSSDPd your Debian would have stronger security. So it depends on your needs.

--- --- --- --- --- --- --- --- --- ---

Below is the same answer as above. But with details if you're interested in those.

Speaking for myself only. I do NOT trust MiniSSDPd. Because it has a very weak security history. Catastrophically weak security history in fact. Find the examples & sources below. I deactivated my MiniSSDPd. Because to me security is more important than speed.

The good news is that starting with Debian 10 Buster. MiniSSDPd is deactivated by default.

Examples of security flaws with MiniSSDPd:

• June 2020 https://arstechnica.com/information-tec ... -internet/

___• https://archive.md/28Y6i

• October 2019 https://www.howtogeek.com/122487/htg-ex ... rity-risk/

___• https://archive.md/3Bnh0

• May 2019 https://www.debian.org/lts/security/201 ... 05.en.html

• May 2016 https://www.debian.org/lts/security/201 ... 54.en.html

• January 2013 https://www.hdm.io/writing/SecurityFlawsUPnP.pdf

___• https://web.archive.org/web/20200927005 ... wsUPnP.pdf
- - -
Loving back your Debian community result in multiple benefits for you at https://www.debian.org/intro/help
User avatar
Francewhoa
 
Posts: 24
Joined: 2013-04-12 17:59
Location: Powell River, British Columbia, Canada


Return to System configuration

Who is online

Users browsing this forum: No registered users and 23 guests

fashionable