Bug#1032517:

[Piotr Jurkiewicz]

On Wed, 8 Mar 2023 19:05:39 +0100 Jan Mojzis  wrote:

Hello,
can You please send me the steps how i can reproduce it
- packages list/versions before the upgrade
- exact apt/apt-get command
- packages list/versions after the upgrade

Jan




I used aptitude to perform upgrade.

Before upgrade:

ii  libnginx-mod-http-echo 1.22.0-3 amd64
ii  libnginx-mod-http-perl 1.22.0-3 amd64
ri  nginx-common   1.22.0-3 all
ii  nginx-light1.22.0-3 amd64
ii  python3-certbot-nginx  1.29.0-1 all

After:

ii  libnginx-mod-http-echo 1:0.63-4 amd64
ii  libnginx-mod-http-perl 1.22.1-7 amd64
ii  nginx  1.22.1-7 amd64
ii  nginx-common   1.22.1-7 all
ii  nginx-light1.22.1-7 all
ii  python3-certbot-nginx  2.1.0-2  all

Then I used aptitude to purge leftover configuration files:

# aptitude purge ?config-files
The following packages will be REMOVED:
  emacsen-common{p} libpython3.10-minimal{p} nginx-common{p} 
php8.1-cli{p} php8.1-common{p} php8.1-fpm{p} php8.1-opcache{p} 
php8.1-readline{p} python3.10-minimal{p}

0 packages upgraded, 0 newly installed, 9 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?] y

Bug#1032517: nginx settings deleted on upgrade

[Piotr Jurkiewicz]

I can confirm this bug. Happened to me twice yesterday. The problem 
occurs also when pruning is being done after system upgrade, in a 
separate step.

Bug#917166: Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted

[Piotr Jurkiewicz]

After downgrading udev and libudev1 to 239-15, swap volume is mounted 
properly on boot.


"lvm2-activation-generator: lvmconfig failed" is still produced on boot, 
but only once and seems not to break anything.


Thanks.

Bug#917166: Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted

[Piotr Jurkiewicz]

Package: lvm2
Version: 2.03.01-2
Severity: grave

On two machines running sid I observed errors during the upgrade to 
2.03.01-2. One of these machines became practically unusable immediately 
after the update (disk IO operations became so slow that even closing 
aptitude took 2 minutes instead usual 3 seconds, I had to reboot it). On 
second machine I observed the same errors in log, but without the 
slowdown (maybe because it was RAID-based).


After the update, both machines generate errors on boot:

Dec 23 15:41:16 sonata lvm2-activation-generator: lvmconfig failed
Dec 23 15:41:16 sonata lvm2-activation-generator: Activation generator 
failed.
Dec 23 15:41:16 sonata systemd[547]: 
/lib/systemd/system-generators/lvm2-activation-generator failed with 
exit status 1.


Additionally, one of the machines is using lvm-based swap partition, 
which fails since the update:


Dec 23 15:42:45 sonata systemd[1]: dev-mapper-sonata\x2dswap.device: Job 
dev-mapper-sonata\x2dswap.device/start timed out.
Dec 23 15:42:45 sonata systemd[1]: Timed out waiting for device 
/dev/mapper/sonata-swap.
Dec 23 15:42:45 sonata systemd[1]: Dependency failed for 
/dev/mapper/sonata-swap.

Dec 23 15:42:45 sonata systemd[1]: Dependency failed for Swap.
Dec 23 15:42:45 sonata systemd[1]: swap.target: Job swap.target/start 
failed with result 'dependency'.
Dec 23 15:42:45 sonata systemd[1]: dev-mapper-sonata\x2dswap.swap: Job 
dev-mapper-sonata\x2dswap.swap/start failed with result 'dependency'.
Dec 23 15:42:45 sonata systemd[1]: dev-mapper-sonata\x2dswap.device: Job 
dev-mapper-sonata\x2dswap.device/start failed with result 'timeout'.


Because this error:

1. Repeats on all machines I use.
2. All of which have completely default lvm config.
3. Results in swap being not activated.

I set the severity to grave.

Log recorded during the update:

Dec 23 15:28:02 sonata systemd[1]: Reloading.
Dec 23 15:28:02 sonata lvm2-activation-generator: lvmconfig failed
Dec 23 15:28:02 sonata lvm2-activation-generator: Activation generator 
failed.
Dec 23 15:28:02 sonata systemd[44153]: 
/lib/systemd/system-generators/lvm2-activation-generator failed with 
exit status 1.

Dec 23 15:28:02 sonata systemd[1]: Reloading.
Dec 23 15:28:02 sonata lvm2-activation-generator: lvmconfig failed
Dec 23 15:28:02 sonata lvm2-activation-generator: Activation generator 
failed.
Dec 23 15:28:02 sonata systemd[44169]: 
/lib/systemd/system-generators/lvm2-activation-generator failed with 
exit status 1.

Dec 23 15:28:03 sonata systemd[1]: Reloading.
Dec 23 15:28:03 sonata lvm2-activation-generator: lvmconfig failed
Dec 23 15:28:03 sonata lvm2-activation-generator: Activation generator 
failed.
Dec 23 15:28:03 sonata systemd[44190]: 
/lib/systemd/system-generators/lvm2-activation-generator failed with 
exit status 1.

Dec 23 15:28:03 sonata systemd[1]: Reloading.
Dec 23 15:28:03 sonata lvm2-activation-generator: lvmconfig failed
Dec 23 15:28:03 sonata lvm2-activation-generator: Activation generator 
failed.
Dec 23 15:28:03 sonata systemd[44209]: 
/lib/systemd/system-generators/lvm2-activation-generator failed with 
exit status 1.

Dec 23 15:28:03 sonata systemd[1]: Reexecuting.
Dec 23 15:28:04 sonata systemd[1]: systemd 240 running in system mode. 
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTIL

Dec 23 15:28:04 sonata systemd[1]: Detected architecture x86-64.
Dec 23 15:28:04 sonata lvm2-activation-generator: lvmconfig failed
Dec 23 15:28:04 sonata lvm2-activation-generator: Activation generator 
failed.
Dec 23 15:28:04 sonata systemd[44271]: 
/lib/systemd/system-generators/lvm2-activation-generator failed with 
exit status 1.
Dec 23 15:28:04 sonata systemd[1]: lvm2-lvmetad.service: Current command 
vanished from the unit file, execution of the command list won't be resumed.
Dec 23 15:28:04 sonata systemd[1]: lvm2-lvmetad.socket: Socket unit 
configuration has changed while unit has been running, no open socket 
file descriptor left. The socket unit is not functional until
Dec 23 15:28:04 sonata systemd[1]: Stopping LVM event activation on 
device 8:3...

Dec 23 15:28:04 sonata systemd[1]: Stopping Network Time Synchronization...
Dec 23 15:28:04 sonata systemd[1]: systemd-timesyncd.service: Succeeded.
Dec 23 15:28:04 sonata systemd[1]: Stopped Network Time Synchronization.
Dec 23 15:28:04 sonata systemd[1]: Starting Network Time Synchronization...
Dec 23 15:28:04 sonata systemd[1]: lvm2-pvscan@8:3.service: Succeeded.
Dec 23 15:28:04 sonata systemd[1]: Stopped LVM event activation on 
device 8:3.

Dec 23 15:28:04 sonata systemd[1]: Started Network Time Synchronization.
Dec 23 15:28:04 sonata systemd[1]: systemd-journal-flush.service: Succeeded.
Dec 23 15:28:04 sonata systemd[1]: Stopped Flush Journal to Persistent 
Storage.
Dec 23 15:28:04 sonata systemd[1]: Stopping Flush Journal to Persistent 
Storage...

Dec 23 15:28:04 sonata systemd-journald[15332]: Journal stopped
Dec 23 15:28:04 

Bug#910400: mysqli stopped connecting to MySQL servers using caching_sha2_password

[Piotr Jurkiewicz]

Package: php7.3-mysql
Version: 7.3.0~rc2-2
Severity: grave

After update to 7.3.0~rc2-2 (sid), mysqli extension stopped working. It 
can't connect to MySQL server, giving the following error message:


PHP message: PHP Warning:  mysqli::__construct(): The server requested 
authentication method unknown to the client [caching_sha2_password]


It worked before the update (version 7.3.0~alpha3-1, I think).

caching_sha2_password is the default authentication method in MySQL 8.0.