- Plesk for Linux
- The following error occurs on an attempt to install WordPress:
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
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/...')
- The following errors can be found in the
CONFIG_TEXT: sshd: input_userauth_request: invalid user osmc [preauth]
sshd: pam_unix(sshd:auth): check pass; user unknown
sshd: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=126.96.36.199
suexec: pam_systemd(plesk_resctrl:session): Failed to create session: Message did not receive a reply (timeout by message bus)
systemd: Starting Session c223 of user jdoe.
systemd: Started Session c223 of user cschlender.
systemd: systemd-logind.service has no holdoff time, scheduling restart.
systemd: Stopping Login Service...
systemd: Starting Login Service...
This is the systemd bug. "systemd. systemd-logind" takes ~25sec timeout after ~1000 ssh logins. During these 25 seconds, resctrl utility is doing its own maintenance and got dbus timeout. Additional information is available in these articles: one and two.
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
- Reload required services:
# service dbus restart
# systemctl daemon-reexec
Note: as this workaround has DDoS attack risk, do not forget to change SSH port as it is described in the following article:
How to change SSH port?