• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Backup job activated but not running

raytracy

Basic Pleskian
CentOS Linux 7.4.1708 (Core)‬, Product Plesk Onyx Version 17.5.3 Update #34

This system running scheduled backup job very well at several weeks ago.
I found the job seems stuck forever since last week, the situation looks like below:

A backup job animation circle has display on front of latest job name in the backup manager panel, seems running, but CPU and disk has no activity. I could not find some processes related to backup such as: tar, pigz, pmm-ras...etc. there were only pmmcli_daemon exist.

look at /var/log/plesk/PMM/backup-<date/time>/pmmcli.log, the last few lines shown:
=============
[2017-12-15 23:49:07.654|6885] INFO: Executing asynchronously <subprocess[6900] 'nice --adjustment=10 /usr/bin/perl /usr/local/psa/admin/bin/plesk_agent_manager server --owner-uid=4c02a67e-0a52-4000-a976-8a3cc98fb5c7 --owner-type=server --description=All configuration and content --exclude-pattern-file=/usr/local/psa/PMM/sessions/2017-12-15-234906.303/exclude -vvvv --session-path=/usr/local/psa/PMM/sessions/2017-12-15-234906.303 --output-file=ftp://[email protected]// --ftp-passive-mode'>
[2017-12-15 23:49:07.654|6885] DEBUG: Acquired session mutex: MainThread
[2017-12-15 23:49:07.655|6885] DEBUG: detecting running pmmcli daemon...
[2017-12-15 23:49:07.655|6885] DEBUG: pmmcli daemon is running
[2017-12-15 23:49:07.655|6885] DEBUG: Create type=Backup
[2017-12-15 23:49:07.669|6885] DEBUG: Released session mutex: MainThread
[2017-12-15 23:49:07.669|6885] DEBUG: Acquired session mutex: MainThread
[2017-12-15 23:49:07.669|6885] DEBUG: Update task id=4, type=Backup
[2017-12-15 23:49:07.683|6885] DEBUG: Released session mutex: MainThread
[2017-12-15 23:49:07.683|6885] DEBUG: <pmmcli.MakeDumpAction object at 0x298d210>: response
[2017-12-15 23:49:07.685|6885] INFO: Outgoing packet:
<?xml version="1.0" ?><response>
<errcode>0</errcode>
<data>
<task-id>4</task-id>
</data>
</response>

=============

But the backup.log stuck as these lines:
==========
[6900]: 2017-12-15 23:49:08.298 DEBUG Execute: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/sbin/backup_restore_helper --get-extensions-hooks
[6900]: 2017-12-15 23:49:08.980 TRACE SQL: SELECT id, host, port, type, admin_login, admin_password, server_version FROM DatabaseServers: Params:
[6900]: 2017-12-15 23:49:08.980 DEBUG Set backup owner guid '4c02a67e-0a52-4000-a976-8a3cc98fb5c7', type 'server'

[6900]: 2017-12-15 23:49:08.980 DEBUG Select to backup Administrator info
[6900]: 2017-12-15 23:49:08.980 DEBUG Select to backup server settings
[6900]: 2017-12-15 23:49:08.980 DEBUG Select to backup server settings

============
I found the backup.log has logged the total size of all sites on earlier lines as:
============
[6886]: 2017-12-15 23:49:07.640 DEBUG Get backup size finished. Backup size of selected objects is 229433577068 bytes
============
The size that calculated was correct.

In the mean time, the animation circle keep running, but no progress in log files.
Whatever backup to either local server or remote ftp both are same, no dump file generated.
The only way to stop infinite backup job is remove it manually in backup manager.
(the job can lasting over 24hr and no any disk/cpu activity related to backup)

I have no idea about this, where can I go more in-depth troubleshooting?

(I would like to upload complete log file, but the forum uploader blocked the file type: log and zip)
 
Actually, you can stop these this task. Just go to Plesk database with:

# plesk db

Find task in longtasks table:

mysql>select * from longtasks;

and delete this stuck task.
 
Hmm...I could remove the stuck task without problem via plesk panel. But the major issue is it did not generate any dump file for backup.

How can I force it to generate backup file but not just stuck?
 
Back
Top