Upgrade to kernel 4.15.18-12-pve goes BOOM!

mrE said:
Grettings t.lamprecht
...
Click to expand...
I found that I use one script, so I can make changes on the network interfaces without Restart the server, maybe this is the origin or maybe not:

Code: 
cat ./donetworkingrestart.sh

#!/bin/bash
echo ==== Proxmox Network-tap-ssh RESTART
brctl show | grep 'vmbr' | awk '{print $1}'

brctl show | grep 'vmbr' | awk '{print $1}' | while read line
do
>$line
brctl show $line | egrep -v 'bridge name|vmbr' | awk {'print $1'} >> $line
done

/etc/init.d/networking stop && /etc/init.d/networking start

ls |grep vmbr | while read line
do
input="$line"
while IFS=',' read -r f1 f2 f3 f4 f5 f6 f7 f8 f9 f10
do
ip link set dev $f1 $f2 $f3 $f4 $f5 $f6 $f7 $f8 $f9 master "$input"
done < "$input"
done
 
... I bite the bullet (after read more posts) and go for the remove - upgrade way, and I hope to restart this server at night, this is the output of all the process and doesn't look any bad... someone can read and tell me if I can reboot with confidence our server? Thanks and regards!

Code: 
# apt -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

# apt purge insserv sysv-rc initscripts openrc
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'openrc' is not installed, so not removed
Package 'initscripts' is not installed, so not removed
Package 'sysv-rc' is not installed, so not removed
The following packages will be REMOVED:
  insserv*
0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
After this operation, 143 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 90462 files and directories currently installed.)
Removing insserv (1.14.0-5.4+b1) ...
Processing triggers for man-db (2.7.6.1-2) ...
(Reading database ... 90444 files and directories currently installed.)
Purging configuration files for insserv (1.14.0-5.4+b1) ...

# apt update && apt full-upgrade
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Hit:2 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:3 http://ftp.us.debian.org/debian stretch Release                                         
Hit:5 http://security.debian.org stretch/updates InRelease                                                   
Hit:6 http://download.proxmox.com/debian/pve stretch InRelease   
Reading package lists... Done         
Building dependency tree       
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  zfs-initramfs zfsutils-linux
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 318 kB of archives.
After this operation, 9,216 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 zfs-initramfs all 0.7.13-pve1~bpo1 [28.5 kB]
Get:2 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 zfsutils-linux amd64 0.7.13-pve1~bpo1 [289 kB]
Fetched 318 kB in 0s (385 kB/s)         
Reading changelogs... Done
(Reading database ... 90444 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) ...
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-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
 
I was applying some updates and noticed that pve-kernel-4.15 version 5.3-2 was being held back as well as pve-kernel-4.15.18-11 version 4.15.18-34 was being held back, would it be related to the above changes that need to be made?
 
t.lamprecht said:
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.
Click to expand...

Thank you, worked like a charm.

I ran the purge remove first,
then I ensured systemd is in charge,
then I rebooted.

After this, I was able to upgrade the ZFS tools:

Code: 
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, 18.4 kB of additional disk space will be used.
Do you want to continue? [Y/n] y


Code: 
========== zfs versions ===========
zfsutils:
  Installed: 0.6.5.9-pve15~bpo80
  Candidate: 0.6.5.9-pve15~bpo80
  Version table:
 *** 0.6.5.9-pve15~bpo80 100
        100 /var/lib/dpkg/status
========== zfs versions ===========
zfsutils-linux:
  Installed: 0.7.13-pve1~bpo1
  Candidate: 0.7.13-pve1~bpo1
  Version table:
 *** 0.7.13-pve1~bpo1 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
        100 /var/lib/dpkg/status
     0.7.12-pve1~bpo1 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.11-pve2~bpo1 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.11-pve1~bpo1 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.9-pve1~bpo9 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.8-pve1~bpo9 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.7-pve1~bpo9 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.6-pve1~bpo9 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.4-pve2~bpo9 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.3-pve1~bpo9 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.7.2-pve1~bpo90 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.6.5.11-pve18~bpo90 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.6.5.11-pve17~bpo90 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.6.5.9-pve16~bpo90 500
        500 http://download.proxmox.com/debian stretch/pve-no-subscription amd64 Packages
     0.6.5.9-5 500
        500 http://ftp.uk.debian.org/debian stretch/contrib amd64 Packages
 
mrE said:
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.
Click to expand...

As your upgrade did not held back any packages, and tried to install some sysv/openrc packages you were safe to begin with.
It can be expected that insserv will be removed, and no official Debian or Proxmox VE Package in stretch should rely on it without an alternative, especially in Proxmox VE which only supports systemd as an init system.
Looking at the reverse dependencies of insserv:
Code: 
# apt rdepends insserv
insserv
Reverse Depends:
  Depends: sysv-rc (>> 1.12.0-10)
  Depends: file-rc (>= 1.14.0-4)
  Suggests: startpar
  Depends: openrc
  Breaks: file-rc (<< 1.14.0-4)
  Conflicts: zfsutils-linux (<< 1.18)

We see that only sysV (old, alternative and PVE unsupported init system), openrc (newer, alternative and PVE unsupported init system) and file-rc (belonging to sysV) are listed as "Depends".
Systemd can use the old /etc/init.d scripts as well, just not fully integrated with all its features, but simple start/stop/restart works. All PVE services have now a well defined systemd unit file, so they should not depend on it anyway,
and a lot of packages install both on debian, to ensure that they are compatible with all Init systems supported by Debian.
 
sektor said:
I was applying some updates and noticed that pve-kernel-4.15 version 5.3-2 was being held back as well as pve-kernel-4.15.18-11 version 4.15.18-34 was being held back, would it be related to the above changes that need to be made?
Click to expand...

Yes, could well be.
 
mrE said:
... I bite the bullet (after read more posts) and go for the remove - upgrade way, and I hope to restart this server at night, this is the output of all the process and doesn't look any bad... someone can read and tell me if I can reboot with confidence our server? Thanks and regards!
Click to expand...

Yes, from the output posted your safe to go forward, you never were in the "bad" situation were an alternative init system was selected by apt/dpkg to resolve this.
Also, insserv came preinstalled from our ISOs, as it was simply left over from older versions and did no harm until the recent conflict, were it then got noticed, and future ISO images won't include it anymore to begin with.
 
  • Like
Reactions: maxprox and mrE
Thanks a lot t.lamprecht,
Today I'll schedule the server restart. (I was waiting to read an answer for this)

I wonder, if in the Proxmox's forum, apart of posting our issues, exists some kind of announce for upgrades/updates with notes before this kind of issues appear, so we can read before to proceed with the upgrades. :)
 
t.lamprecht said:
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.
Click to expand...
Sorry I'm a little bit confused how to proceed. I have the "The following packages have been kept back: zfs-initramfs zfs-zed zfsutils-linux" problem since I've upgraded from Proxmox 4 to 5 and finally want to solve it. My system says:

Code: 
# apt policy insserv

insserv:

  Installed: 1.18.0-2

  Candidate: 1.18.0-2

  Version table:

 *** 1.18.0-2 500

        500 http://ftp.debian.org/debian buster/main amd64 Packages

        100 /var/lib/dpkg/status

# cat /etc/debian_version

10.11

"conflicts with "insserv (<< 1.18)" means "concflicts with insserv older than 1.18?
 
You must log in or register to reply here.

About

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

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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 yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back