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

Resolved Backup error: Warning: Extension "Git"Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 3: System user unavailabl

Martijn_mb

New Pleskian
Server operating system version
CentOS Linux 7.6.1810/CentOS 7.9.2009/AlmaLinux 8.6
Plesk version and microupdate number
Version 18.0.46 Update #2,/Version 18.0.47 Update #4
This morning we got warnings on our overnight backup tasks on 6 different servers running Plesk 18.0.46/18.0.47, some a bit older on CentOS Linux 7.6.1810 and CentOS 7.9.2009 others on AlmaLinux 8.6.


All warnings are the same:
Warning: Extension "Git"
Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 3: System user unavailable
On 1 server the warning is repeated 20+ times, the others range from 3 to 10 warnings. The server with 20+ warnings has a lot more domains/websites running on it compared to the other servers. But all of them have 30+ sites running on them - but the number is of warnings is not equal to the number of sites using the Git extention.

But we also have a couple of other servers running simular setups and same Plesk versions without these warings in there backup tasks. And on these the Git extention is installed and used on a couple of domains.



Any suggestion what this might be and how we can remove these warnings from our backup tasks?
 
I have this too

OS: AlmaLinux release 8.6 (Sky Tiger)
Plesk: Version 18.0.46 Update #2

Going to update to 18.0.47

The error is (3 times - Incremental backup - Yesterday worked fine):
Warning: Extension "Git"
Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 3: System user unavailable
 
Hi, same thing here, on 3 servers, for other servers no warnings
I've seen that there was an update to do of the git extension, I've made it (after the warnings).
Could be that the reason?
 
Hi, I'm having the same problem with the backup:

OS: Ubuntu 22.04.1 LTS
Plesk: Version 18.0.47 Update #4

Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 3: System user unavailable
 
Hi, I'm having the same problem with the backup:

OS: CentOS Linux 7 (Core)

Plesk Obsidian v18.0.47_build1800221017.13


Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 3: System user unavailable
 
I have had the same update on servers today, however only on the one backup that was running during the update. A new backup did not show the error. I assume that something was changed during the update so that the backup process was disturbed, but on new backups things should be alright again. Can any of you confirm this?
 
I have had the same update on servers today, however only on the one backup that was running during the update. A new backup did not show the error. I assume that something was changed during the update so that the backup process was disturbed, but on new backups things should be alright again. Can any of you confirm this?
I'll confirm tomorrow how the backup went tonight (will be incremental also, i think)
 
I have had the same update on servers today, however only on the one backup that was running during the update. A new backup did not show the error. I assume that something was changed during the update so that the backup process was disturbed, but on new backups things should be alright again. Can any of you confirm this?
I've just checked the overnight backups - all servers with the warning on yesterdays overnight backup are now without warning.
 
I have had the same update on servers today, however only on the one backup that was running during the update. A new backup did not show the error. I assume that something was changed during the update so that the backup process was disturbed, but on new backups things should be alright again. Can any of you confirm this?
Two days without the error, only the one I reported.
 
Back
Top