I can login fine, however, after logging out these errors appear in the secure log:
Mar 26 01:10:20 ns1 proftpd: Deprecated pam_stack module called from service "proftpd" Mar 26 01:10:20 ns1 proftpd: pam_env(proftpd:setcred): Unable to open config file: /etc/security/pam_env.conf: No such file or directory Mar 26 01:10:20 ns1 proftpd[16972]: ns1.xxxxxxxxx (xx.xx.xx.xx[xx.xx.xx.xx]]) - PAM(setcred): System error Mar 26 01:10:20 ns1 proftpd: Deprecated pam_stack module called from service "proftpd" Mar 26 01:10:20 ns1 proftpd: pam_succeed_if(proftpd:session): error retrieving information about user 0 Mar 26 01:10:20 ns1 proftpd: pam_unix(proftpd:session): session closed for user xxxxxxx Mar 26 01:10:20 ns1 proftpd[16972]: xxxxxxxxxx (xx.xx.xx.xx[xx.xx.xx.xx]) - PAM(close_session): System error Mar 26 01:10:20 ns1 proftpd[16972]: ns1.xxxxxxxxx (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.If I comment out DefaultRoot in proftpd.conf the error disappears but this doesn't seem like a safe work around.
Evidently chroot confuses the system as to the location of pam_env.conf. Given the lack of response to my query should I assume this error doesn't matter?<br><br>Post edited by: mdtiberi, at: 2009/03/26 16:18
Well, personally, my lack of response comes from having absolutely no idea what to suggest :-)
I hadn't run into that error before. That said, if it actually works either way, I'm not sure I'd worry about it too much :-)
Otherwise, the best I can offer is that there are number of folks on Google who seem to have run into that, some of those may be of help if you want to try and get rid of the message.
-Eric
I upgraded to proftpd 1.3.2 from the dag repo and logs no longer show a <i>PAM(setcred): System error</i>, however, after chroot still can't find /etc/security/pam_env.conf.
I'll continue to chip away at this and post any progress.