Applicable to:
- Plesk for Linux
Symptoms
-
The backup process can be stuck since Plesk update to 18.0.41 spawning a lot of backupmng processes
-
The following messages can be found in the backup logs in
/var/log/plesk/PMM/backup-YYYY-MM-DD-hh-mm-ss-ms:CONFIG_TEXT: INFO: TransportError Transport error: unable to check directory existence: Curl error: (7) Couldn't connect to server: Last FTP request: Last FTP response: [common/plesk-utils/PMM/repository-transport/transport.cpp:TransportError]
virtual bool plesk::tRepositoryFtp::IsDirExist(const string&)
INFO: pmm-ras finished. Exit code: 125
INFO: The utility succesfully executed.
CONFIG_TEXT: INFO: Curl error: (28) Timeout was reached: Last FTP request: STOR backup_2202161157.tar: Last FTP response: 150 Opening BINARY mode data connection for backup_2202161157.tar
CONFIG_TEXT: INFO: Unable to resume upload. Have got 550 error code from FTP server
INFO: Cancel export
INFO: Data sending interrupted, because of lost connection to FTP
INFO: Error occured while writing archive to FTP Curl error: Unable to resume an interrupted upload: (25) Upload failed (at start/before it took off): Last FTP request: STOR backup_2202200441.tar: Last FTP response: 550 backup_2202200441.tar: Disc quota exceeded: Connection to the FTP server has lost
Cause
Product issue:
- #PPPM-13411 "Scheduled backup processes no longer get stuck indefinitely when backing up to FTP storage if the configured FTP server is unavailable or if the provided credentials do not match."
Fixed in:- Plesk Obsidian 28 February 2022
Resolution
Workaround
If update is not possible for some reason you may try the following
-
Connect to the Plesk server via SSH.
-
Stop cron service
On Debian/Ubuntu:
# systemctl stop cron
On CentOS/RHEL/CloudLinux:
# systemctl stop crond
-
Kill these processes using their PID:
# kill -9 `ps auxfw | grep -i pmm | grep -v grep | awk {'print $2'}`
# kill -9 `ps auxfw | grep -i backup | grep -v grep | awk {'print $2'}`
-
Start cron service
On Debian/Ubuntu:
# systemctl stop cron
On CentOS/RHEL/CloudLinux:
# systemctl stop crond
-
Either wait until the next scheduled backup is launched or launch the process manually through the following command:
# /opt/psa/admin/sbin/backupmng
Warning: If the tasks are launched manually through the command above, all the pending scheduled backups will be launched at the same time. Consider this for resource usage.
Comments
1 comment
Just a note: In the instructions above for the workaround, under the section "Start cron service", it should say
systemctl start cron for Debian
systemctl start crond for CentOS/RHEL/CloudLinux
It says "stop" in both Stop and Start sections in the workaround article:-)
Also: the command for CentOS/RHEL/CloudLinux is missing to run manual
/usr/local/psa/admin/sbin/backupmng
Please sign in to leave a comment.