FS#59689 - [lxc] pam_cgfs.so 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
Opened by vikk (vikk) - Friday, 17 August 2018, 14:38 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 11 March 2019, 13:10 GMT
|
Details
Description:
PAM unable to open pam_cgfs.so 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/pam_cgfs.so): /usr/lib/security/pam_cgfs.so: undefined symbol: strlcat Aug 17 16:06:25 localhost sshd[747]: PAM adding faulty module: /usr/lib/security/pam_cgfs.so 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 pam_cgfs.so -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
Fix: https://github.com/lxc/lxc/pull/2558/commits/71174d464fd3798a181d7768441f80f1952d93e9
We should backport this if they don't make a release soon...
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 :)