Applicable to:
- Plesk for Linux
Symptoms
-
Unable to connect to Plesk server via SSH with
rootuser:CONFIG_TEXT: Access denied
Permission denied -
The following error can be found in
/var/log/messages(e.g. when connected not asroot):CONFIG_TEXT: hostname crond[30531]: PAM unable to dlopen(/usr/lib64/security/pam_imunify.so): /usr/lib64/security/pam_imunify.so: cannot open shared object file: No such file or directory
-
Plesk notifications may not be sent after the execution of a Daily Maintenance task.
-
Cron tasks are not executed at the required time. In the
/var/log/cronlog file the following errors may persist:CONFIG_TEXT: crond[28816]: (root) PAM ERROR (Module is unknown)
crond[28816]: (root) FAILED to authorize user with PAM (Module is unknown)
Cause
The Imunify360 extension has been recently deleted from the server, however, its leftovers are still present in the /etc/pam.d/system-auth and /etc/pam.d/password-auth configuration files.
Resolution
-
Install SSH Terminal extension and login to the server.
-
Comment out corresponding lines in
/etc/pam.d/system-authand/etc/pam.d/password-authas follows, e.g. using Vi:CONFIG_TEXT: #%PAM-1.0
...
#auth required pam_imunify.so check_only
...
#auth required pam_imunify.so
...
Comments
4 comments
I get this problem and so far I can't login with rootHello Alan Gonzales,
Please apply the solution from the article and comment out the required lines in the
/etc/pam.d/system-authand/etc/pam.d/password-authfiles via the SSH Terminal extension.Hi,
I'm missing an extra step.
vim /etc/ssh/sshd_config
Line:
Match user , comment line.
i did this and it worked
Hello Alan Gonzales,
Thank you for sharing. However, the `Match User` directive is not adjusted during the installation/removal of the Imunify360 extension. The solution described in the article is complete and no additional actions are required in this case.
Please sign in to leave a comment.