• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

PAM error messages

L

links2world

Guest
Hello,

Every time a ftp user disconnects, I get the following error messages in /var/log/messages:

May 10 21:20:29 columbia proftpd[23471]: columbia.domain.com (64.116.x.x[64.116.x.x]) - PAM(setcred): System error
May 10 21:20:29 columbia proftpd[23471]: columbia.domain.com (64.116.x.x[64.116.x.x]) - PAM(close_session): System error
May 10 21:20:29 columbia proftpd[23471]: columbia.domain.com (64.116.x.x[64.116.x.x]) - FTP session closed.

There is no problem with the ftp user authentication. Those error messages goes away only if I disable PAM.

Any ideeas? Thanks in advance,

Regards,
 
I have the same problem. I have plesk 8.0.0 on a RHE4.

When I had Plesk 7.5.4 on a RHE4, didn't have it.

Thanks,

Xavi.
 
Same here

Logwatch is filled with these PAM Syste errors for proftpd.

What's this all about?
 
cross-post NOT INTENDED, but no one else will...RE PAM errors

In reference to PAM dlopen, dlerror I am not intentionally cross-posting, but there are two and only two post on this entire forum pertaining to Plesk 8 and/or CENTOS so we need to join them since support is limited to a few!!

Posting this to all current posts relating to PSA8 in recent days:

http://forum.swsoft.com/showthread.php?s=&threadid=34087

I'm still looking at it, but it seems turning off mailman and/or disabling mailing lists for each client has resulted in the PAM....pam_plesk.so errors going away.

Not sure just yet, only know the messages and secure logs no longer reflect PAM errors.

Will continue to update on our progress.
 
Back
Top