3805 2013-01-29 11:20:08 +0000 PAM support: missing pam_systemd.so 2013-09-25 12:40:47 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.4 x86 Multiple VERIFIED FIXED Medium normal 1.5 1 yi.zhao ross.burton alexandrux.palalau hongxu.jia liang.li2 meta.mr.watcher meta.watcher Qi.Chen ross.burton sgw yi.zhao --- --- No (bug/feature does not impact docs) oldest_to_newest 29288 0 yi.zhao 2013-01-29 11:20:08 +0000 Tree/Branch: poky/master Git Rev: 8d6e55bf2192524bda84138b5356a2791adbbe61 When build an image with pam support, there is a error message with missing pam_systemd.so Steps: ############## 1. Add DISTRO_FEATURES_append = " pam" to conf/local.conf and build the image. 2. Boot up the image and check the /var/log/message ############## ############# Jan 29 11:13:41 qemuppc authpriv.err login[438]: PAM unable to dlopen(/lib/security/pam_systemd.so): /lib/security/pam_systemd.so: cannot open shared object file: No such file or di rectory 231 Jan 29 11:13:41 qemuppc authpriv.err login[438]: PAM adding faulty module: /lib/security/pam_systemd.so ############# 29344 1 ross.burton 2013-01-30 12:03:09 +0000 Hm, I thought pam would silently handle that. Clearly that change needs to be conditional on the systemd distro feature. 29386 2 radu.moisan 2013-01-31 09:46:56 +0000 I checked and indeed the library is missing, however I could not reproduce the same way, with my current setup (pulled master yesterday) it breaks gconf complaining about the same thing. I also tried my systemd branch, which has the systemd.bbclass and it works, so I'm chasing that lead now. 29387 3 ross.burton 2013-01-31 10:07:23 +0000 The problem is that pam_systemd only exists in systemd distros, but the pam configuration always refers to it. I was under the impression that pam would silently handle optional pam modules without error, but that doesn't appear to be the case. The systemd reference in the pam configuration needs to be conditional on the systemd feature, or truly optional. Actually, pam.conf says: "If the type value from the list above is prepended with a - character the PAM library will not log to the system log if it is not possible to load the module because it is missing in the system. This can be useful especially for modules which are not always installed on the system and are not required for correct authentication and authorization of the login session." Sounds ideal. 29388 4 radu.moisan 2013-01-31 10:12:26 +0000 ok, missed the part where systemd was disabled. Looking into pam then. 29443 5 radu.moisan 2013-02-01 09:42:19 +0000 I could initially reproduce this, but could not anymore after Thursday morning pull. 29564 6 yi.zhao 2013-02-06 09:50:37 +0000 I can reproduce it with latest master branch: git rev: ee1f126ad5cb2c6af66815e55720257a1efc5a49 Steps: ############## 1. Add DISTRO_FEATURES_append = " pam" to conf/local.conf and build the image. 2. Boot up the image and check the /var/log/message ############## Check the message log, I can see the following error: ############### Feb 6 09:03:29 qemux86 authpriv.err passwd[822]: PAM unable to dlopen(/lib/security/pam_systemd.so): /lib/security/pam_systemd.so: cannot open shared object file: No such file or directory Feb 6 09:03:29 qemux86 authpriv.err passwd[822]: PAM adding faulty module: /lib/security/pam_systemd.so ############### 29762 7 radu.moisan 2013-02-13 13:18:35 +0000 (In reply to comment #6) > I can reproduce it with latest master branch: > git rev: ee1f126ad5cb2c6af66815e55720257a1efc5a49 > > Steps: > ############## > 1. Add DISTRO_FEATURES_append = " pam" to conf/local.conf and build the > image. > 2. Boot up the image and check the /var/log/message > ############## > > Check the message log, I can see the following error: > ############### > Feb 6 09:03:29 qemux86 authpriv.err passwd[822]: PAM unable to > dlopen(/lib/security/pam_systemd.so): /lib/security/pam_systemd.so: cannot > open shared object file: No such file or directory > Feb 6 09:03:29 qemux86 authpriv.err passwd[822]: PAM adding faulty module: > /lib/security/pam_systemd.so > ############### please dump here the output for "systemctl --version" 29783 8 radu.moisan 2013-02-14 09:33:38 +0000 I can't reproduce. I checked that systemd is compiled with pam support and it is. The pam_systemd.so is in it's place and in consequence there is not error message trying to load the library. Please confirm. 29940 9 yi.zhao 2013-02-19 03:10:22 +0000 (In reply to comment #8) > I can't reproduce. > I checked that systemd is compiled with pam support and it is. The > pam_systemd.so is in it's place and in consequence there is not error > message trying to load the library. > > Please confirm. Hi Radu, I made a mistake. I didn't set the init manager to systemd in local.conf. After added the line DISTRO_FEATURES_INITMAN ?= "systemd" in local.conf, the error message disappeared. But if we don't use systemd, the pam still want to load pam_systemd.so, is this a bug ? Do we need to fix it ? 29946 10 radu.moisan 2013-02-19 08:14:29 +0000 Ok, then I'll give a shot to what Ross was suggesting. 29982 11 radu.moisan 2013-02-20 09:59:28 +0000 (In reply to comment #9) > Hi Radu, > > I made a mistake. I didn't set the init manager to systemd in local.conf. > After added the line DISTRO_FEATURES_INITMAN ?= "systemd" in local.conf, the > error message disappeared. But if we don't use systemd, the pam still want > to load pam_systemd.so, is this a bug ? Do we need to fix it ? I've tried this morning a clean build on master with sysvinit enabled (and pam). I could not find any warning/error message in logs with regard to pam_systemd.so or anything related to systemd for that matter. 30036 12 radu.moisan 2013-02-22 12:37:13 +0000 same on my side. 30113 13 yi.zhao 2013-02-26 12:04:12 +0000 (In reply to comment #11) > (In reply to comment #9) > > > Hi Radu, > > > > I made a mistake. I didn't set the init manager to systemd in local.conf. > > After added the line DISTRO_FEATURES_INITMAN ?= "systemd" in local.conf, the > > error message disappeared. But if we don't use systemd, the pam still want > > to load pam_systemd.so, is this a bug ? Do we need to fix it ? > > I've tried this morning a clean build on master with sysvinit enabled (and > pam). I could not find any warning/error message in logs with regard to > pam_systemd.so or anything related to systemd for that matter. Which image type do you test ? The issue happens on sato and sato-sdk image. 30114 14 radu.moisan 2013-02-26 12:08:42 +0000 tried sato. 30117 15 yi.zhao 2013-02-26 12:23:20 +0000 DISTRO_FEATURES_append = " pam" There must be a space between " and pam I tried qemuarm, still have this issue. 31154 16 yi.zhao 2013-03-26 06:07:25 +0000 This issue still happens on master: 9ffee9add2d0380f4025e7a678a166f25a7d659e Reopen it. 31291 17 radu.moisan 2013-03-29 11:09:04 +0000 asked QA to take a look over 31344 18 radu.moisan 2013-04-02 09:10:15 +0000 gave another try today, sato and sato-sdk Build Configuration: BB_VERSION = "1.17.1" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "1.3+snapshot-20130402" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "master:92aeb31341b28b193d616ab5cf38af1b9673e37d" run both images in quemu and grep'd for systemd in /var/log/messages, nothing came up. @Yi Zhao: Please don't reopen this, let QA team to give it a try, and if they can't please work with them until they do, assuming this is a valid bug. 31439 19 ross.burton 2013-04-03 11:57:50 +0000 I can replicate. The key is that this only happens on sysvinit images. 31458 20 radu.moisan 2013-04-03 16:19:34 +0000 (In reply to comment #19) > I can replicate. The key is that this only happens on sysvinit images. so a clean build with systemd disabled should do it, right? 31460 21 ross.burton 2013-04-03 16:24:31 +0000 Yep, or an autobuilt image. Annoying prefixing the pam line with - doesn't seem to work, this machine I just tried it on won't start X anymore. 31929 22 alexandrux.palalau 2013-04-11 12:18:56 +0000 Could not reproduce on master branch, commit ID: fe336b149552b1f4f24d979c40302653298b98cc 33067 23 radu.moisan 2013-05-13 13:19:11 +0000 tried again following builds (core-image-sato) (clean builds) Build Configuration: BB_VERSION = "1.19.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "1.3+snapshot-20130513" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "master:f7afeeb75993b159bb8959e0309bc5eb3978a8fb" Build Configuration: BB_VERSION = "1.19.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS = "powerpc-poky-linux" MACHINE = "qemuppc" DISTRO = "poky" DISTRO_VERSION = "1.3+snapshot-20130513" TUNE_FEATURES = "m32 fpu-hard ppc603e" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "master:f7afeeb75993b159bb8959e0309bc5eb3978a8fb" 36937 24 ross.burton 2013-09-19 10:43:12 +0000 Still happening: Sep 19 11:31:54 genericx86 login[1329]: PAM unable to dlopen(/lib/security/pam_systemd.so): /lib/security/pam_systemd.so: cannot open shared object file: No such file or directory Will investigate. 36983 25 ross.burton 2013-09-19 15:03:32 +0000 Patch sent to oe-core. 37130 26 ross.burton 2013-09-24 15:18:52 +0000 Merged in oe-core 3ccb0855a7a6b147e5025855c6376747ba72986a. 37198 27 alexandrux.palalau 2013-09-25 12:40:47 +0000 Verified in master branch. Commit ID: 4d8ab87d25ea6e59dc88375813ef88ee0ac813d0 No errors in /var/log/messages.