• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Manual Backup with pmm-ras won`t stop the process when finished.

ldoerrdotcom

New Pleskian
Server operating system version
Ubuntu Server 20.04
Plesk version and microupdate number
18.
Hello everyone,

i have switched to a new Internet-Provider who doesn't provide IPv4 anymore. So i have to manually download the dumps from my plesk server. That works really good, while using an SCP Command from the Backup Server. When i had IPv4 it was no problem to create FTP Backups via Backup Manager.

Today i need to schedule a Backup, which creates the backup_info_0375928357.XML file. So i grab the newest backup_info everytime there is a new one and create a dump.tar File.

My problem now is, that this command:
Bash:
plesk sbin pmm-ras --export-dump-as-file --dump-specification=$backup_info_xml --dump-file-specification=$backup_file_path
...won't stop until i kill it manually.

I have created a dump now and this is the text from the pmmcli.log File:
[2022-11-06 01:45:07.131|3502749] DEBUG: LOG: custom log /var/log/plesk/PMM/backup-2022-11-06-01-45-07-131/backup.log
[2022-11-06 01:45:07.132|3502749] DEBUG: LOG: logs dir requested: /var/log/plesk/PMM/backup-2022-11-06-01-45-07-131
[2022-11-06 01:45:07.954|3502749] INFO: Executing asynchronously <subproc.Subprocess object at 0x7f75b5ac32e0>
[2022-11-06 01:45:07.955|3502749] DEBUG: LOG: logs dir requested: /var/log/plesk/PMM/backup-2022-11-06-01-45-07-131
[2022-11-06 01:45:07.956|3502749] DEBUG: Acquired session mutex: MainThread
[2022-11-06 01:45:07.956|3502749] DEBUG: detecting running pmmcli daemon...
[2022-11-06 01:45:07.956|3502749] DEBUG: starting pmmcli daemon...
[2022-11-06 01:45:07.960|3502749] DEBUG: Executing asynchronously [3502752] process. CmdLine is '/opt/psa/admin/sbin/pmmcli_daemon'
[2022-11-06 01:45:07.960|3502749] DEBUG: Create type=Backup
[2022-11-06 01:45:07.965|3502749] DEBUG: Released session mutex: MainThread
[2022-11-06 01:45:07.965|3502749] DEBUG: Acquired session mutex: MainThread
[2022-11-06 01:45:07.965|3502749] DEBUG: Update task id=2590, type=Backup
[2022-11-06 01:45:07.968|3502749] DEBUG: Released session mutex: MainThread
[2022-11-06 01:45:07.968|3502749] DEBUG: <__main__.MakeDumpAction object at 0x7f75b5b177f0>: response
[2022-11-06 01:45:07.971|3502749] INFO: Outgoing packet:
<?xml version="1.0" ?><response>
<errcode>0</errcode>
<errmsg/>
<data>
<task-id>2590</task-id>
</data>
</response>

Why does the process not stop, when the file is created? The strange thing is, that the backup.tar is finished when it doesn't get bigger. I can download it via SCP and import it later, when i have to. But i have to manually KILL the process, which is not nice in my opinion.

I have also found an old post here, where no real answer was found 6 years ago allready: pmm-ras won't stop until it's killed
 
Some things to consider: After a backup seems to be finished it can still take several minutes until the corresponding PMM job is also finished and removed. Also, make sure that no other hanging backup tasks are present.
 
When running the script from command line at night (1am for example today) it still didn't stop until i killed it this morning at 7am. The backup was 29GB big and the file was lastly changed on 2:23am - so the job kept going for that whole time.
 
Back
Top