Re: Upgrade issue with Debian 9 -> 10
On 7/3/22 4:28 PM, Miroslav Skoric wrote:
Haven't tried that, but something else already helped: While it was
idling with fsck in tty1, I went to tty2 and entered: apt --fix-broken
install ... and it did/resumed full upgrade. (Interestingly, this time
it did not complain about no space in / and /usr.) When it finished, I
tested startx and it brought GUI. Not sure now but I think that I then
rebooted and it went it into GUI as expected. So far - so good. Few red
[FAILED] warnings during CLI phase related to not starting UFV,
Shorewall, and minissdpd services, so I need to check for that.
As a temporary cure for [FAILED] warnings, I removed ufw and gufw as I
sparsely used them anyway. Then I also removed completely all shorewall
things, purged its old folders, and reinstalled again. Now the shorewall
service starts properly. The only remaining [FAILED] warning comes from
minissdpd:
# 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
Active: failed (Result: exit-code) since Tue 2022-07-05 13:00:48
CEST; 3min 1
Docs: man:minissdpd(1)
Process: 1225 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper
${MiniSSD
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: can't parse
"wlo1" as
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: Usage:
/usr/sbin/mini
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: <interface>
is eith
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]:
192.168.1.42/255.25
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: By default,
socket
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: and pid
written to
Jul 05 13:00:48 localhost minissdpd[1225]: ioctl(s, SIOCGIFADDR, ...):
Cannot as
Jul 05 13:00:48 localhost systemd[1]: minissdpd.service: Control process
exited,
Jul 05 13:00:48 localhost systemd[1]: minissdpd.service: Failed with
result 'exi
Jul 05 13:00:48 localhost systemd[1]: Failed to start keep memory of all
UPnP de
lines 1-16/16 (END)...skipping...
● 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 Tue 2022-07-05 13:00:48
CEST; 3min 16s ago
Docs: man:minissdpd(1)
Process: 1225 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper
${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited,
status=1
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: can't parse
"wlo1" as a valid address or interface name
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: Usage:
/usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f
device] -i <int
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: <interface>
is either an IPv4 address with mask such as
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]:
192.168.1.42/255.255.255.0, or an interface name such as eth0.
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: By default,
socket will be open as /var/run/minissdpd.sock
Jul 05 13:00:48 localhost minissdpd-systemd-wrapper[1225]: and pid
written to file /var/run/minissdpd.pid
Jul 05 13:00:48 localhost minissdpd[1225]: ioctl(s, SIOCGIFADDR, ...):
Cannot assign requested address
Jul 05 13:00:48 localhost systemd[1]: minissdpd.service: Control process
exited, code=exited, status=1/FAILURE
Jul 05 13:00:48 localhost systemd[1]: minissdpd.service: Failed with
result 'exit-code'.
Jul 05 13:00:48 localhost systemd[1]: Failed to start keep memory of all
UPnP devices that announced themselves.
~
~
~
~
... Seems it does not like network device change (wlan0 --> wlo1). It
makes me wonder if I shall try to remove/reinstall minissdpd. Any idea?
Well, for sure I missed to uninstall some software that I rarely used in
stretch, and if I did so I might have not got into trouble. Now will
take more care with buster.
I freed some 1.5 GB by removing LaTeX and TeX Live packages that I
installed few years ago just for test but never really used. Probably
need to get rid of more unneeded stuff.
So far - so good. Seems that buster runs a bit faster (than stretch) on
this old laptop.
Misko
Reply to: