Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#59689 - [lxc] load failure after upgrade to 3.0.2-1

Attached to Project: Community Packages
Opened by vikk (vikk) - Friday, 17 August 2018, 14:38 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 11 March 2019, 13:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


PAM unable to open after upgrade

Additional info:

Upgraded from 3.0.1-1 to 3.0.2-1 and got following errors in systemd journal...

Aug 17 16:06:25 localhost sshd[747]: PAM unable to dlopen(/usr/lib/security/ /usr/lib/security/ undefined symbol: strlcat
Aug 17 16:06:25 localhost sshd[747]: PAM adding faulty module: /usr/lib/security/

This affects unprivileged containers so they can't start...

lxc-start CONTAINER 20180817133714.509 ERROR cgfsng - cgroups/cgfsng.c:all_controllers_found:701 - No freezer controller mountpoint found
lxc-start CONTAINER 20180817133714.509 ERROR cgroup - cgroups/cgroup.c:cgroup_init:44 - Failed to initialize cgroup driver
lxc-start CONTAINER 20180817133714.509 ERROR start - start.c:lxc_init:861 - Failed to initialize cgroup driver

Reverted back to 3.0.1-1 and it works again.

Steps to reproduce:

$ cat "session optional -c freezer,memory,name=systemd,unified" >> /etc/pam.d/system-login

Upgrade to 3.0.1-2 and the "PAM unable to dlopen" should appear during boot.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Monday, 11 March 2019, 13:10 GMT
Reason for closing:  Fixed
Comment by Eli Schwartz (eschwartz) - Sunday, 02 September 2018, 06:10 GMT Comment by Kon Lykast (laerus) - Thursday, 06 September 2018, 08:07 GMT
please can you backport the fix? i'm stacked with kernel 4.17 and lxc 3.0.1
Comment by Sergej Pupykin (sergej) - Tuesday, 11 September 2018, 15:17 GMT
It looks like it needs update to git version, because of patched 3.0.2 cannot be compiled
Comment by Jérémie Roquet (Arkanosis) - Monday, 04 February 2019, 00:38 GMT
Hello everyone,

I had this issue with kernel 4.18 and lxc 3.0.2 back in October, but today, with kernel 4.20 and lxc 3.1.0, everything is working like a charm again.

I assume this bug can be closed, then?

Thanks a lot for the fix, btw :)