Upgrade to kernel 4.15.18-12-pve goes BOOM!

TheGrandWazoo

New Member
May 24, 2018
8
4
3
55
Just did an upgrade to 4.15.18-12-pve which looked like ZFS changes only and now my system boots into a read-only state just after 'cgmanager' starts and that's it. Just a '(none):~#' prompt.
I am running ZFS on the server. Scientific Progress Goes Boink.

-Waz
 

tjh

New Member
Feb 15, 2018
19
3
3
43
I noticed my "apt-get dist-upgrade" today removed insserv, which I did wonder if it was a bad thing or not.
I haven't rebooted yet though, now reading this post I'm too scared too.

root@orbit:~# dpkg -l | grep inss
rc insserv 1.14.0-5.4+b1 amd64 boot sequence organizer using LSB init.d script dependency information
 

TheGrandWazoo

New Member
May 24, 2018
8
4
3
55
I wouldn't unless you have a backup plan...right now, I don't except reinstall. Not even the 'rescue' on the ISO helping.
 

tjh

New Member
Feb 15, 2018
19
3
3
43
This was what apt did today, for anyone with clue following along:

Start-Date: 2019-03-19 10:31:42
Commandline: apt-get dist-upgrade
Install: pve-kernel-4.15.18-12-pve:amd64 (4.15.18-35, automatic)
Upgrade: zfs-initramfs:amd64 (0.7.12-pve1~bpo1, 0.7.13-pve1~bpo1), zfsutils-linux:amd64 (0.7.12-pve1~bpo1, 0.7.13-pve1~bpo1), spl:amd64 (0.7.12-pve1~bpo1, 0.7.13-pve1~bpo2), libzfs2linux:amd64 (0.7.12-pve1~bpo1, 0.7.13-pve1~bpo1), libzpool2linux:amd64 (0.7.12-pve1~bpo1, 0.7.13-pve1~bpo1), pve-kernel-4.15:amd64 (5.3-2, 5.3-3), libnvpair1linux:amd64 (0.7.12-pve1~bpo1, 0.7.13-pve1~bpo1), libuutil1linux:amd64 (0.7.12-pve1~bpo1, 0.7.13-pve1~bpo1)
Remove: insserv:amd64 (1.14.0-5.4+b1)
End-Date: 2019-03-19 10:32:27
 

tjh

New Member
Feb 15, 2018
19
3
3
43
Sorry @TheGrandWazoo looks like I might be totally wrong here:

root@orbit:~# apt-cache depends insserv
insserv
Depends: libc6
Breaks: sysv-rc
Suggests: bootchart2
root@orbit:~# dpkg -l | grep sysv-rc
root@orbit:~#


Pretty sure that's saying the only thing that depends on it is sysv-rc and sysv-rc isn't installed.
So I suspect your problem is/was something else, especially if the rescue CD didn't help. Good luck, I hope you get it fixed.
 

TheGrandWazoo

New Member
May 24, 2018
8
4
3
55
Reinstalled from the ISO 5.3-5 and recovered my ZFS and ZPOOL's. Restored the configs and all was fine in the world again. Then, just because, I did the upgrade again to 5.3-11 with that kernel 4.15.18-12 that just jack me and rebooted with no issues.
Go figure. Hopefully it was just a fluke.
Good Luck.

-Waz
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
1,841
281
103
South Tyrol/Italy
The issue is that the new version of "zfsutils-linux" conflicts with "insserv (<< 1.18)", and on Debian stretch the version of insserv is "1.14.0-5.4+b1", so they are in conflict.

Normally this is not an issue, insserv is left over and not needed anymore (and future PVE/PMG releases drop it also from the installer). But on some setups, where additional packages were installed with strange sysv-init relations you may have a state were this upgrade can not be easily resolveds by apt.

If you have such a setup you can fix this, or avoid it in the first place, using the following steps:

Code:
apt -f install
apt purge insserv sysv-rc initscripts openrc
apt update && apt full-upgrade
 

TheGrandWazoo

New Member
May 24, 2018
8
4
3
55
Thomas,

Thank you for the info. Thankfully it was my lab machine (home) and not production/customers machines...always do it in the lab ;). I will mark this post because I have gone through many upgrades from previous versions that might have caused the issue. I think the only thing I install over and beyond the original install is 'git' and 'librest-client-perl' because I develop the FreeNAS plugin for ZFS over iSCSI.

-Waz

P.S. - I do remember two write errors on an rc file at the end of the upgrade but I do not have that information available. I did NOT receive those errors after the reinstall.
 

TheGrandWazoo

New Member
May 24, 2018
8
4
3
55
The issue is that the new version of "zfsutils-linux" conflicts with "insserv (<< 1.18)", and on Debian stretch the version of insserv is "1.14.0-5.4+b1", so they are in conflict.

Normally this is not an issue, insserv is left over and not needed anymore (and future PVE/PMG releases drop it also from the installer). But on some setups, where additional packages were installed with strange sysv-init relations you may have a state were this upgrade can not be easily resolveds by apt.

If you have such a setup you can fix this, or avoid it in the first place, using the following steps:

Code:
apt -f install
apt purge insserv sysv-rc initscripts
apt update && apt full-upgrade
Thomas,

In your post you used...

Code:
apt update
apt full-upgrade
I always thought we had to do...

Code:
apt update
apt dist-upgrade
When should we use the 'full-upgrade'?

Thx,

-Waz
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
2,321
242
63
For `apt` (the high-level package manager and new frontend for `apt-get`, `apt-cache`, ...) `apt full-upgrade` and `apt dist-upgrade` call the same code and can be considered synonymous.

* `apt-get` (same source-package and codebase) has `dist-upgrade` only
* `aptitude` (different codebase and a separate source-package) has `full-upgrade` only (which afaik does the same, but has e.g. a different conflict resolution mechanism)

IOW - if you use `apt` you can use both `full-upgrade` and `dist-upgrade` interchangably.

Hope this helps!
 

Zamana

Member
Dec 20, 2015
41
0
11
51
The issue is that the new version of "zfsutils-linux" conflicts with "insserv (<< 1.18)", and on Debian stretch the version of insserv is "1.14.0-5.4+b1", so they are in conflict.

Normally this is not an issue, insserv is left over and not needed anymore (and future PVE/PMG releases drop it also from the installer). But on some setups, where additional packages were installed with strange sysv-init relations you may have a state were this upgrade can not be easily resolveds by apt.

If you have such a setup you can fix this, or avoid it in the first place, using the following steps:

Code:
apt -f install
apt purge insserv sysv-rc initscripts
apt update && apt full-upgrade
Your instructions saved my server (and my night).

Thank you very much!!!

Regards.
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
1,841
281
103
South Tyrol/Italy
When should we use the 'full-upgrade'?
as stoiko mentioned there the same, apt's man page talks only about "full-upgrade", thus I'm rather used to that, "dist-upgrade" was kept for backward compatibility.

But this mirroring behaviour is not always the case, "apt upgrade" and "apt-get upgrade" are not the same, the apt version pulls in new dependencies, whereas the apt-get doesn't. So apt "full-upgrade" or apt/apt-get "dist-upgrade" are still the recommended way to do updates.
 

jnieuw

Member
May 6, 2015
26
0
21
Just did an apt-get update && apt-get dist-upgrade this morning getting a message I have to reboot immediately, not sure what to do...
Should I reboot, or remove sysv-rc etc. first ?
Code:
apt -f install
apt purge insserv sysv-rc initscripts
apt update && apt full-upgrade
Here is the log from the update with the reboot message:
Code:
root@host:~# apt-get update && apt-get dist-upgrade
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.nl.debian.org/debian stretch InRelease
Hit:3 http://ftp.nl.debian.org/debian stretch Release
Hit:5 http://download.proxmox.com/debian stretch InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  sysv-rc
The following NEW packages will be installed:
  libeinfo1 librc1 openrc pve-kernel-4.15.18-12-pve
The following packages have been kept back:
  zfs-initramfs zfs-zed zfsutils-linux
The following packages will be upgraded:
  libnvpair1linux libuutil1linux libzfs2linux libzpool2linux pve-kernel-4.15
  spl
6 upgraded, 4 newly installed, 1 to remove and 3 not upgraded.
Need to get 0 B/53.5 MB of archives.
After this operation, 261 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading changelogs... Done
Selecting previously unselected package libeinfo1.
(Reading database ... 67643 files and directories currently installed.)
Preparing to unpack .../libeinfo1_0.23-1+b1_amd64.deb ...
Unpacking libeinfo1 (0.23-1+b1) ...
Selecting previously unselected package librc1.
Preparing to unpack .../librc1_0.23-1+b1_amd64.deb ...
Unpacking librc1 (0.23-1+b1) ...
dpkg: sysv-rc: dependency problems, but removing anyway as you requested:
 initscripts depends on sysv-rc | file-rc | openrc; however:
  Package sysv-rc is to be removed.
  Package file-rc is not installed.
  Package openrc is not installed.

(Reading database ... 67654 files and directories currently installed.)
Removing sysv-rc (2.88dsf-59.9) ...
Selecting previously unselected package openrc.
(Reading database ... 67633 files and directories currently installed.)
Preparing to unpack .../0-openrc_0.23-1+b1_amd64.deb ...
Unpacking openrc (0.23-1+b1) ...
Preparing to unpack .../1-libuutil1linux_0.7.13-pve1~bpo1_amd64.deb ...
Unpacking libuutil1linux (0.7.13-pve1~bpo1) over (0.7.12-pve1~bpo1) ...
Preparing to unpack .../2-libnvpair1linux_0.7.13-pve1~bpo1_amd64.deb ...
Unpacking libnvpair1linux (0.7.13-pve1~bpo1) over (0.7.12-pve1~bpo1) ...
Preparing to unpack .../3-libzpool2linux_0.7.13-pve1~bpo1_amd64.deb ...
Unpacking libzpool2linux (0.7.13-pve1~bpo1) over (0.7.12-pve1~bpo1) ...
Preparing to unpack .../4-libzfs2linux_0.7.13-pve1~bpo1_amd64.deb ...
Unpacking libzfs2linux (0.7.13-pve1~bpo1) over (0.7.12-pve1~bpo1) ...
Selecting previously unselected package pve-kernel-4.15.18-12-pve.
Preparing to unpack .../5-pve-kernel-4.15.18-12-pve_4.15.18-35_amd64.deb ...
Unpacking pve-kernel-4.15.18-12-pve (4.15.18-35) ...
Preparing to unpack .../6-pve-kernel-4.15_5.3-3_all.deb ...
Unpacking pve-kernel-4.15 (5.3-3) over (5.3-2) ...
Preparing to unpack .../7-spl_0.7.13-pve1~bpo2_amd64.deb ...
Unpacking spl (0.7.13-pve1~bpo2) over (0.7.12-pve1~bpo1) ...
Setting up pve-kernel-4.15.18-12-pve (4.15.18-35) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.15.18-12-pve /boot/vmlinuz-4.15.18-12-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.15.18-12-pve /boot/vmlinuz-4.15.18-12-pve
update-initramfs: Generating /boot/initrd.img-4.15.18-12-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.15.18-12-pve /boot/vmlinuz-4.15.18-12-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.18-12-pve
Found initrd image: /boot/initrd.img-4.15.18-12-pve
Found linux image: /boot/vmlinuz-4.15.18-11-pve
Found initrd image: /boot/initrd.img-4.15.18-11-pve
Found linux image: /boot/vmlinuz-4.15.18-10-pve
Found initrd image: /boot/initrd.img-4.15.18-10-pve
Found linux image: /boot/vmlinuz-4.15.18-9-pve
Found initrd image: /boot/initrd.img-4.15.18-9-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
done
Setting up libeinfo1 (0.23-1+b1) ...
Setting up librc1 (0.23-1+b1) ...
Setting up libuutil1linux (0.7.13-pve1~bpo1) ...
Setting up libnvpair1linux (0.7.13-pve1~bpo1) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Setting up spl (0.7.13-pve1~bpo2) ...
Processing triggers for systemd (232-25+deb9u9) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up openrc (0.23-1+b1) ...
Add existing services ...
 * service killprocs added to runlevel recovery
 * service bootlogs added to runlevel recovery
 * service motd added to runlevel recovery
 * service single added to runlevel recovery
 * service console-setup.sh added to runlevel default
 * service bootlogs added to runlevel default
 * service cgmanager added to runlevel default
 * service lvm2-lvmetad added to runlevel default
 * service lvm2-lvmpolld added to runlevel default
 * service motd added to runlevel default
 * service rbdmap added to runlevel default
 * service rrdcached added to runlevel default
 * service rsyslog added to runlevel default
 * service zabbix-agent added to runlevel default
 * service apcupsd added to runlevel default
 * service atd added to runlevel default
 * service atop added to runlevel default
 * service autofs added to runlevel default
 * service cgproxy added to runlevel default
 * service dbus added to runlevel default
 * service postfix added to runlevel default
 * service pve-cluster added to runlevel default
 * service smartmontools added to runlevel default
 * service ssh added to runlevel default
 * service sysstat added to runlevel default
 * service cron added to runlevel default
 * service pvefw-logger added to runlevel default
 * service rsync added to runlevel default
 * service pve-firewall added to runlevel default
 * service rc.local added to runlevel default
 * service rmnologin added to runlevel default
 * service stop-bootlogd added to runlevel default
 * service mountkernfs.sh added to runlevel sysinit
 * service udev added to runlevel sysinit
 * service keyboard-setup.sh added to runlevel sysinit
 * service mountdevsubfs.sh added to runlevel sysinit
 * service bootlogd added to runlevel sysinit
 * service hostname.sh added to runlevel sysinit
 * service hwclock.sh added to runlevel sysinit
 * service lvm2 added to runlevel sysinit
 * service checkroot.sh added to runlevel sysinit
 * service checkfs.sh added to runlevel sysinit
 * service checkroot-bootclean.sh added to runlevel sysinit
 * service kmod added to runlevel sysinit
 * service mountall.sh added to runlevel sysinit
 * service mountall-bootclean.sh added to runlevel sysinit
 * service apparmor added to runlevel sysinit
 * service ebtables added to runlevel sysinit
 * service procps added to runlevel sysinit
 * service urandom added to runlevel sysinit
 * service networking added to runlevel sysinit
 * service iscsid added to runlevel sysinit
 * service rpcbind added to runlevel sysinit
 * service nfs-common added to runlevel sysinit
 * service open-iscsi added to runlevel sysinit
 * service mountnfs.sh added to runlevel sysinit
 * service mountnfs-bootclean.sh added to runlevel sysinit
 * service bootmisc.sh added to runlevel sysinit
 * service x11-common added to runlevel sysinit
 * service stop-bootlogd-single added to runlevel sysinit
 * service sendsigs added to runlevel off
 * service umountnfs.sh added to runlevel off
 * service umountfs added to runlevel off
 * service umountroot added to runlevel off
 * service savecache added to runlevel off
 * Caching service dependencies ...                                       [ ok ]
**********************************************************************
*** WARNING: if you are replacing sysv-rc by OpenRC, then you must ***
*** reboot immediately using the following command:                ***
for file in /etc/rc0.d/K*; do s=`basename $(readlink "$file")` ; /etc/init.d/$s stop; done
**********************************************************************
Setting up pve-kernel-4.15 (5.3-3) ...
Setting up libzpool2linux (0.7.13-pve1~bpo1) ...
Setting up libzfs2linux (0.7.13-pve1~bpo1) ...
Processing triggers for systemd (232-25+deb9u9) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...

root@host:~#
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
1,841
281
103
South Tyrol/Italy
Should I reboot, or remove sysv-rc etc. first ?
a reboot would boot you into openRC and nothing would work (out of the box).

So yes, do my proposed steps first, maybe even add openrc and a autoremove of the pulled in packages:
Code:
apt purge insserv sysv-rc initscripts openrc
apt autoremove --purge
Ensure that systemd is still installed and in charge:
Code:
apt install --reinstall systemd
the you should be really on the safe side to reboot.
 
  • Like
Reactions: egidijus

jnieuw

Member
May 6, 2015
26
0
21
a reboot would boot you into openRC and nothing would work (out of the box).

So yes, do my proposed steps first, maybe even add openrc and a autoremove of the pulled in packages:
Code:
apt purge insserv sysv-rc initscripts openrc
apt autoremove --purge
Ensure that systemd is still installed and in charge:
Code:
apt install --reinstall systemd
the you should be really on the safe side to reboot.
Thank you!

Did the purge:
Code:
root@host:~# apt purge insserv sysv-rc initscripts openrc
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libeinfo1 librc1
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  initscripts* insserv* openrc* sysv-rc*
0 upgraded, 0 newly installed, 4 to remove and 3 not upgraded.
After this operation, 1,836 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 73956 files and directories currently installed.)
Removing initscripts (2.88dsf-59.9) ...
Removing openrc (0.23-1+b1) ...
Removing insserv (1.14.0-5.4+b1) ...
Processing triggers for systemd (232-25+deb9u9) ...
Processing triggers for man-db (2.7.6.1-2) ...
(Reading database ... 73817 files and directories currently installed.)
Purging configuration files for sysv-rc (2.88dsf-59.9) ...
Purging configuration files for insserv (1.14.0-5.4+b1) ...
Purging configuration files for openrc (0.23-1+b1) ...
Purging configuration files for initscripts (2.88dsf-59.9) ...
Processing triggers for systemd (232-25+deb9u9) ...
And reinstalled systemd:
Code:
root@host:~# apt install --reinstall systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libeinfo1 librc1
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 3 not upgraded.
Need to get 0 B/2,468 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 73777 files and directories currently installed.)
Preparing to unpack .../systemd_232-25+deb9u9_amd64.deb ...
Unpacking systemd (232-25+deb9u9) over (232-25+deb9u9) ...
Setting up systemd (232-25+deb9u9) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for dbus (1.10.26-0+deb9u1) ...
Also did the suggested autoremove:
Code:
root@host:~# apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  libeinfo1 librc1
0 upgraded, 0 newly installed, 2 to remove and 3 not upgraded.
After this operation, 125 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 73776 files and directories currently installed.)
Removing librc1 (0.23-1+b1) ...
Removing libeinfo1 (0.23-1+b1) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
And to be sure an apt-get update && apt-get dist-upgrade:
Code:
root@host:~# apt-get update && apt-get dist-upgrade
Ign:1 http://ftp.nl.debian.org/debian stretch InRelease
Hit:2 http://ftp.nl.debian.org/debian stretch Release
Hit:4 http://security.debian.org stretch/updates InRelease
Hit:5 http://download.proxmox.com/debian stretch InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  zfs-initramfs zfs-zed zfsutils-linux
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 384 kB of archives.
After this operation, 8,192 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 zfs-initramfs all 0.7.13-pve1~bpo1 [28.5 kB]
Get:2 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 zfsutils-linux amd64 0.7.13-pve1~bpo1 [289 kB]
Get:3 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 zfs-zed amd64 0.7.13-pve1~bpo1 [65.7 kB]
Fetched 384 kB in 0s (3,303 kB/s)
Reading changelogs... Done
(Reading database ... 73765 files and directories currently installed.)
Preparing to unpack .../zfs-initramfs_0.7.13-pve1~bpo1_all.deb ...
Unpacking zfs-initramfs (0.7.13-pve1~bpo1) over (0.7.12-pve1~bpo1) ...
Preparing to unpack .../zfsutils-linux_0.7.13-pve1~bpo1_amd64.deb ...
Unpacking zfsutils-linux (0.7.13-pve1~bpo1) over (0.7.12-pve1~bpo1) ...
Preparing to unpack .../zfs-zed_0.7.13-pve1~bpo1_amd64.deb ...
Unpacking zfs-zed (0.7.13-pve1~bpo1) over (0.7.12-pve1~bpo1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.15.18-12-pve
Setting up zfsutils-linux (0.7.13-pve1~bpo1) ...
Installing new version of config file /etc/zfs/zfs-functions ...
Setting up zfs-zed (0.7.13-pve1~bpo1) ...
Setting up zfs-initramfs (0.7.13-pve1~bpo1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.15.18-12-pve
root@host:~#
Will reboot later tonight.
 
Mar 19, 2018
104
8
18
How common is this issue likely to be? I don't particularly want to apt purge insserv sysv-rc initscripts openrc unless I have to, and it would seem you can't tell if you need to unless you get the errors after running apt-get dist-upgrade.
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
1,841
281
103
South Tyrol/Italy
I don't particularly want to apt purge insserv sysv-rc initscripts openrc
why? they're useless on a Proxmox VE system anyway, can only do harm.

you can't tell if you need to unless you get the errors after running apt-get dist-upgrade.
You can tell:

1) check if any of them is installed, especially sysv-rc and initscripts
2) do "apt update && apt full-upgrade" but before hitting blindly enter check what apt says it wants to do. if there are things like:
Code:
....
The following packages have been kept back:
  zfs-initramfs zfs-zed zfsutils-linux
....
or
Code:
The following packages will be REMOVED:
  *sysv-rc*
The following NEW packages will be installed:
  libeinfo1 librc1 *openrc*
you know that it is an issue for you, thus type n and enter to abort and do above steps.
if apt only speak of upgrading things (no removal, and no new installed package besides the new kernel) your good.
 
Mar 19, 2018
104
8
18
That's very useful, thank you.

Keep in mind that I'm not particularly familiar with Debian. I've been using Redhat/Centos for the past 20 years or so, and I'm not used to packages being replaced like this and don't know how to handle it or know what's important and what isn't. Give me another 20 years and I'll be an expert.
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
1,841
281
103
South Tyrol/Italy
I didn't want to imply anything and it's totally fine to ask, no worries. Just curious for your reasons, so to give you the best advise, e.g., if for whatever reasons in your setup those packages couldn't be removed as easily.

I mean normally this shouldn't happen, and it does not always happen - e.g., on a default new installation were only a small set of additional packages got installed, I never saw it happen.
My colleagues didn't either here, I did - but I've a really "butchered" host system around were I tried a lot, really a lot - so normally nothing found out in the wild. We only had a single machine in a test environment exhibit this, and it had amanda backup installed as single distinction against the other cluster nodes, AFAIK, which apparently pulled in a bit more than ideal (sysv-rc)... Together with the fact that we still shipped insserv and the new conflict against the version shipped from zfsutils-linux this non-ideal situation may sometimes be produced. So hopefully you can stay used to your old "packages not being replaced like this" experience in the future again :)
 

mrE

New Member
Apr 21, 2014
10
0
1
Grettings t.lamprecht
After reading this thread, I got the feeling that I'm in the same side with a potential problem, so I need to ask
If I run this :
Code:
# apt update && apt dist-upgrade
The following packages will be REMOVED:
  insserv
The following packages will be upgraded:
  zfs-initramfs zfsutils-linux
2 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
And I got this installed:
Code:
~# dpkg -l | grep inss
ii  insserv                              1.14.0-5.4+b1                  amd64        boot sequence organizer using LSB init.d script dependency information

~# apt-cache depends insserv
insserv
  Depends: libc6
  Breaks: sysv-rc
  Suggests: bootchart2

~# apt-cache depends sysv-rc
sysv-rc
  PreDepends: init-system-helpers
 |Depends: debconf
  Depends: <debconf-2.0>
    cdebconf
    debconf
  Depends: sysvinit-utils
  Depends: insserv
  Depends: startpar
  Breaks: systemd
  Recommends: lsb-base
  Suggests: bum
I wonder if was the "apcupsd" that I install in 2017 in our proxmox server, this are the scripts in /etc/init.d/
Code:
ls /etc/init.d/ -l
total 122
-rwxr-xr-x 1 root root 1554 Jan 16  2017 apcupsd
-rwxr-xr-x 1 root root 6485 Mar 28  2017 apparmor
-rwxr-xr-x 1 root root 1232 Apr  6  2017 console-setup.sh
-rwxr-xr-x 1 root root 3049 May  3  2015 cron
-rwxr-xr-x 1 root root 2813 Oct  1  2017 dbus
-rwxr-xr-x 1 root root 4352 Mar 15  2013 ebtables
-rwxr-xr-x 1 root root 3809 Mar 22  2017 hwclock.sh
-rwxr-xr-x 1 root root 1503 Jun 18  2017 iscsid
-rwxr-xr-x 1 root root 1479 May 18  2016 keyboard-setup.sh
-rwxr-xr-x 1 root root 2044 Dec 25  2016 kmod
-rwxr-xr-x 1 root root 4597 Sep 16  2016 networking
-rwxr-xr-x 1 root root 5658 Dec 15  2016 nfs-common
-rwxr-xr-x 1 root root 2503 Jun 18  2017 open-iscsi
-rwxr-xr-x 1 root root 3624 Jun 17  2017 postfix
-rwxr-xr-x 1 root root 1191 Nov 22  2016 procps
-rwxr-xr-x 1 root root 1479 Dec  7  2017 pve-firewall
-rwxr-xr-x 1 root root 1285 Dec  7  2017 pvefw-logger
-rwxr-xr-x 1 root root  844 Dec  9  2016 rbdmap
-rwxr-xr-x 1 root root 2358 May  5  2017 rpcbind
-rwxr-xr-x 1 root root 5246 Apr 25  2016 rrdcached
-rwxr-xr-x 1 root root 4355 Jul 10  2014 rsync
-rwxr-xr-x 1 root root 2868 Jan 18  2017 rsyslog
-rwxr-xr-x 1 root root 1222 Apr  2  2017 screen-cleanup
-rwxr-xr-x 1 root root 3505 Jul 30  2016 smartmontools
-rwxr-xr-x 1 root root 4033 Nov 18  2017 ssh
-rwxr-xr-x 1 root root 6087 Jul  5  2017 udev
lrwxrwxrwx 1 root root   22 Jan 16  2017 ups-monitor -> ../apcupsd/ups-monitor
-rwxr-xr-x 1 root root 2757 Nov 23  2016 x11-common

So I wonder If is safe to remove ALL as you sugest above:
Code:
apt purge insserv sysv-rc initscripts openrc
apt autoremove --purge
And Ensure that systemd is still installed and in charge:
Code:
apt install --reinstall systemd
Lucky me, my spider sense tingles before doing something very bad on this proxmox server.
** This refrends my need to get a suscription!
Regards!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!