Applicable to:
- Plesk for Linux
Symptoms
-
The following error occurs on an attempt to install WordPress via WordPress Toolkit in Plesk:
PLESK_ERROR: filemng failed: move_to_cgroup(): pam_open_session() failed 6: Permission denied
move process 15666 to cgroup for user plesktest failed
filemng: Error occurred during /bin/mkdir command.
-
The following error can be found in the
/var/log/plesk/panel.log
:CONFIG_TEXT: ERR [extension/wp-toolkit] #0 /opt/psa/admin/plib/modules/wp-toolkit/library/Helper/Util.php(199): Zend_Json::decode('move_to_cgroup(...')
#1 /opt/psa/admin/plib/modules/wp-toolkit/library/Capability/Command/Config.php(119): PleskExt\WpToolkit\Helper\Util::decode('move_to_cgroup(...')
#2 /opt/psa/admin/plib/modules/wp-toolkit/library/Capability/Command/Config.php(55): PleskExt\WpToolkit\Capability\Command\Config->reset()
...
#17 /opt/psa/admin/plib/api-cli/CliUtilityRunner.php(35): CliUtilityRunner->run()
#18 /opt/psa/admin/plib/api-cli/extension.php(4): require_once('/opt/psa/admin/...')
#19 {main} -
The following errors can be found in the
/var/log/syslog
:CONFIG_TEXT: sshd[13985]: input_userauth_request: invalid user osmc [preauth]
sshd[13985]: pam_unix(sshd:auth): check pass; user unknown
sshd[13985]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.188.10.179
suexec[14029]: pam_systemd(plesk_resctrl:session): Failed to create session: Message did not receive a reply (timeout by message bus)
systemd[1]: Starting Session c223 of user jdoe.
systemd[1]: Started Session c223 of user cschlender.
systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
systemd[1]: Stopping Login Service...
systemd[1]: Starting Login Service...
Cause
This is the systemd bug. "systemd. systemd-logind" takes ~25sec timeout after ~1000 ssh logins. During these 25 seconds, the resctrl
utility is doing its own maintenance and gets a dbus
timeout.
Additional information about the bug is available in these articles:
- https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1591411
- https://bugs.freedesktop.org/show_bug.cgi?id=95264.
Resolution
As a workaround, change dbus timeout for SSHD service as follows:
-
Connect to the server via SSH;
-
Create a dbus config with the following content setting timeout to 5 seconds:
# cat /etc/dbus-1/session-local.conf
<busconfig>
<limit name="auth_timeout">50000</limit>
</busconfig> -
Reload required services:
# service dbus restart
# systemctl daemon-reexec
Note: as this workaround has DDoS attack risk, do not forget to change the SSH port as it is described in the following article:
How to change the SSH port number on a Linux server?
Comments
0 comments
Please sign in to leave a comment.