"Accessing a corrupted shared library" after upgrade to v8

ikus060

New Member
Nov 18, 2021
23
9
3
38
Hello,

I have a cluster of promox v7. I upgrade one of the node to proxmox v8. I ran into an issue for the networking and manage to get arround it by installing chrony (apt install chrony) as recommended by the documentation.

Now I'm planning to migrate back the LXC and VM to the v8 node and I'm facing an issue.
Once the migration is complete, the LXC refused to start. With debugging log, I see and error: "Accessing a corrupted shared library"

Code:
 lxc-start -F -l DEBUG --logfile=boot119.log --logpriority=9 -F 119
lxc-start: 119: ../src/lxc/sync.c: sync_wait: 34 An error occurred in another process (expected sequence number 7)
lxc-start: 119: ../src/lxc/start.c: __lxc_start: 2107 Failed to spawn container "119"
lxc-start: 119: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: 119: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
root@boxter:~# cat boot119.log
lxc-start 119 20230711155136.414 ERROR    start - ../src/lxc/start.c:start:2197 - Accessing a corrupted shared library - Failed to exec "/sbin/init"
lxc-start 119 20230711155136.414 ERROR    sync - ../src/lxc/sync.c:sync_wait:34 - An error occurred in another process (expected sequence number 7)
lxc-start 119 20230711155136.470 ERROR    start - ../src/lxc/start.c:__lxc_start:2107 - Failed to spawn container "119"
lxc-start 119 20230711155137.704 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 119 20230711155137.704 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options

I'n not sure what is the meaning of this.

I tried to chroot into "/rpool/data/subvol-119-disk-1" and I'm getting similar result.

Code:
chroot /rpool/data/subvol-119-disk-1
chroot: failed to run command ‘/bin/bash’: Accessing a corrupted shared library

I've migrate back the container to the original server and manage to start it without issue.

Do you think data integrity of the new server was compromised ? Is it possible to verify that ?
 
Not sure what happen to be honest. I destroyed the replica and recreate it from zero and now everything is working. Seams the Filesystem was really corrupted. It's a bit scarry.
 

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!

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!