Symptoms
- 
Unable to connect to FTP. The following error is shown in a FTP client: Error: Failed to retrieve directory listing 
 Error: Connection timed out after 20 seconds of inactivity
 Error: Could not connect to server
- 
The issue occurs intermittently. Only sometimes a FTP connection works 
- 
Plesk File Manager is loading very slow 
- 
Websites and webmailer are not accessible with "502 Bad Gateway" error 
- 
Attempts to start systemd-logind service or other services fail with a similar error message: # systemctl start systemd-logind.service 
 Job for systemd-logind.service failed. See 'systemctl status systemd-logind.service' and 'journalctl -xn' for details.
- 
The following error can be observed via journalctl: # journalctl -u dbus 
 -- Logs begin at Tue 2017-12-19 06:44:01 CET, end at Wed 2017-12-20 01:18:50 CET. --
 Dec 19 06:44:01 example.com dbus[695]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
- 
The following error message is displayed in Plesk: New configuration files for the Apache web server were not created due to errors in the configuration models: Can not restart web server: INFO: Service: httpd, Action: stop Trying to stop service httpd ... WARNING! Httpd - control script does not exist or does not executable (see log file: /var/log/plesk/rc_actions.log) Continue ... INFO: Service: httpd, Action: stop Trying to stop service httpd ... WARNING! Some http: // http: // log file: /var/log/plesk/rc_actions.log) Continue ... WARNING! Some problems are found during httpd stop service (see log file: /var/log/plesk/rc_actions.log) Continue ... / usr / local / psa / admin / sbin / pleskrc execution failed: Failed to get D-Bus connection : Connection refused Failed to get D-Bus connection: Connection refused 
Cause
This is a DBus bug with ID 95263 which is fixed in version 1.11.10.
Resolution
For RHEL operating system:
- 
Connect to the Plesk server via SSH. 
- 
Update system packages: # yum update -y 
- 
Reboot the server. Note: if reboot via SSH does not work, reboot the server from your service provider panel (AWS, GCP, Hetzner Robot, etc.). 
For CentOS/Debian/Ubuntu-based distributions the bug fix is yet to be implemented. Contact the operating system vendor for further assistance.