• 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.

restore backup

M

MOUCHON STEPHANE

Guest
I have some problem with a restore of complete server backup :

The error message is

<response>
<errcode>1000</errcode>
<errmsg>pmm utility 'Conflict Resolver' raised an exception. Error code is: 255
See pmmcli.log to find out detailed information on this</errmsg>
</response>


it seems that it is due to the creation of files in the directory /usr/local/psa/rsession/ during the process.

There no customer 's session during the process, it is not a production server.

My file is up to 7Go. I have some 35 go files to restore. Is it possible to make that with plesk ????

The backup utility is very bugged. It seems that the backup utility cannot be use in production.

How do you work for securised this product ?

Thanks by advance

Regards
 
Not enough information. Could you please provide related error messages from pmmcli.log?
 
error message

extract of my file /usr/local/psa/PMM/pmmcli.log


14951: 2010-03-31 14:09:59,706 INFO Clone restore session from session 20100331140523761 started
14951: 2010-03-31 14:09:59,706 INFO Create restore session 20100331140959569 started
14951: 2010-03-31 14:09:59,779 INFO Initialized restore session 20100331140959569
14951: 2010-03-31 14:10:10,366 INFO Create restore session 20100331140959569 done
14951: 2010-03-31 14:10:10,367 INFO Clone restore session 20100331140959569 from session 20100331140523761 done
14951: 2010-03-31 14:10:34,645 DEBUG /usr/local/psa/PMM/rsessions/20100331140959569/restore.xml copied to /usr/local/psa/PMM/rsessions/20100331140959569/restore.xml.conflicted
14951: 2010-03-31 14:10:34,709 INFO Executing <subprocess[15201] '/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/backup/Conflicts/Runner.php --resolve-conflicts --plesk-dump=/usr/local/psa/PMM/rsessions/20100331140959569/dump.xml --owner-guid=8fd222dc-15d3-4be5-be79-69039a1f83ed --restore-specification=/usr/local/psa/PMM/rsessions/20100331140959569/restore.xml.conflicted --conflicts-description=/usr/local/psa/PMM/rsessions/20100331140959569/conflict_description --conflicts-resolution-rules=/usr/local/psa/PMM/rsessions/20100331140959569/conflict_resolution_rules --restore-specification-out=/usr/local/psa/PMM/rsessions/20100331140959569/restore.xml --session-path=/usr/local/psa/PMM/rsessions/20100331140959569'>
14951: 2010-03-31 14:10:43,346 INFO Subprocess raised ExecuteException: Subprocess <subprocess[15201] '/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/backup/Conflicts/Runner.php --resolve-conflicts --plesk-dump=/usr/local/psa/PMM/rsessions/20100331140959569/dump.xml --owner-guid=8fd222dc-15d3-4be5-be79-69039a1f83ed --restore-specification=/usr/local/psa/PMM/rsessions/20100331140959569/restore.xml.conflicted --conflicts-description=/usr/local/psa/PMM/rsessions/20100331140959569/conflict_description --conflicts-resolution-rules=/usr/local/psa/PMM/rsessions/20100331140959569/conflict_resolution_rules --restore-specification-out=/usr/local/psa/PMM/rsessions/20100331140959569/restore.xml --session-path=/usr/local/psa/PMM/rsessions/20100331140959569'> was finished with exit code 255
== STDOUT ====================

== STDERR ====================
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 46 bytes) in /usr/local/psa/admin/plib/backup/Conflicts/ConflictsDoc.php on line 1386

14951: 2010-03-31 14:10:43,347 CRITICAL PMMUtility exception:
Subprocess <subprocess[15201] '/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/backup/Conflicts/Runner.php --resolve-conflicts --plesk-dump=/usr/local/psa/PMM/rsessions/20100331140959569/dump.xml --owner-guid=8fd222dc-15d3-4be5-be79-69039a1f83ed --restore-specification=/usr/local/psa/PMM/rsessions/20100331140959569/restore.xml.conflicted --conflicts-description=/usr/local/psa/PMM/rsessions/20100331140959569/conflict_description --conflicts-resolution-rules=/usr/local/psa/PMM/rsessions/20100331140959569/conflict_resolution_rules --restore-specification-out=/usr/local/psa/PMM/rsessions/20100331140959569/restore.xml --session-path=/usr/local/psa/PMM/rsessions/20100331140959569'> was finished with exit code 255
== STDOUT ====================

== STDERR ====================
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 46 bytes) in /usr/local/psa/admin/plib/backup/Conflicts/ConflictsDoc.php on line 1386

Traceback (most recent call last):
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 1846, in main
data_action_response, errcode_response, error_message = actions.get(sys.argv[1][2:])(parameters)
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 1695, in resolve_conflicts
return ActionRunner(ResolveConflictsAction, resolve_conflicts_task_description, None).doActivity()
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 75, in doActivity
result = self.processor.doActivity()
File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 1070, in doActivity
rsession.resolveConflictsOnce(rsession.get_plesk_actual_dump(),self.get_resolve_conflicts_task_description().get_conflict_resolution_rules())
File "/usr/local/psa/admin/share/pmmcli/pmmcli_session.py", line 328, in resolveConflictsOnce
self.__doResolveConflictsOnce(plesk_actual_dump, conflict_resolution_rules_object)
File "/usr/local/psa/admin/share/pmmcli/pmmcli_session.py", line 325, in __doResolveConflictsOnce
pmm_conflict_detector.ConflictResolver.run(owner_guid, plesk_actual_dump, stored_restore_specification, self.__restore_specification, self.__conflict_description, stored_conflict_resolution_rules, self.__session_path)
File "/usr/local/psa/admin/share/pmmcli/pmm_conflict_detector.py", line 128, in run
raise PMMUtilityException('Conflict Resolver', x)
PMMUtilityException: was finished with exit code 255

14951: 2010-03-31 14:10:43,348 INFO Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>1000</errcode>
<errmsg>pmm utility 'Conflict Resolver' raised an exception. Error code is: 255
See pmmcli.log to find out detailed information on this</errmsg>
</response>
 
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 46 bytes) in /usr/local/psa/admin/plib/backup/Conflicts/ConflictsDoc.php on line 1386

The problem is caused by memory lack for PHP operation. Check following parameter for admin's PHP and try to increase it.

# grep memory_limit /usr/local/psa/admin/conf/php.ini
memory_limit = 128M

134217728 bytes = 128M
 
Back
Top