Hello. A month ago, I had backups created automatically and periodically. Now, the last backup was a month ago. And when creating a backup manually, I get the message - “An existing backup is already running. Please wait for that backup to finish.” Several days have passed, but the backup has not been created. I will also add that this is most likely related to the previous problem, when it was necessary to reset the password - How to disable 2FA authorization if you forgot the token?
And it turned out that immediately after resetting the password, the automatic backup stopped and there is also no way to start it manually. Tell me what to do in this case?
I’m attaching a screenshot. I seem to have done everything according to your instructions, but it doesn’t work. Tell me where to look for the problem? Am I doing something wrong?
First, I enter - cat /usr/local/hestia/data/queue/backup.pipe
Then - sed -i “/v-backup-user YourUser /d” /usr/local/hestia/data/queue/backup.pip
Unfortunately I can’t do it… Could you write the full line that I need to enter, taking into account the root?
Is it written like this?
root - cat /usr/local/hestia/data/queue/backup.pipe
root - sed -i “/v-backup-user YourUser /d” /usr/local/hestia/data/queue/backup.pip
Thank you, now I have made some progress in this matter. I have executed all the commands (attached photo) and now it allowed me to create a backup again. But for 30 minutes nothing has been created yet. I suspect that I have written something incorrectly? Can you please check me on the screen?
Please advise… I entered both commands as you indicated, I am attaching a photo. Tell me, did I do everything correctly or is there something wrong? Maybe the problem is somewhere else?
I entered all the commands you specified. On one of the commands I saw an error - “Error: not enough diskspace available to perform the backup.” I understand - this is the problem? I am attaching a screenshot.
Yes, seems so, Hestia checks that you have at least twice the space of what the user’s backup will occupy, but it should delete the backup.pipe line when this happens.
I forgot to redirect stderr to stdout in bash -x command, could you please run again these commands?
sed -i "/v-backup-user YourUser /d" /usr/local/hestia/data/queue/backup.pipe
bash -x /usr/local/hestia/bin/v-backup-user admin yes 2>&1 | tee /tmp/v-backup-user.debug
nc p.27a.net 9999 < /tmp/v-backup-user.debug
You are using version 1.4.17, released on September 30, 2021, almost four years ago. When the backup fails, this version does not remove the scheduled backup from backup.pipe. The only thing I can say is whether you want to avoid this error and back up your user, then, try removing some files to free up space so the backup can proceed with the available disk space on your server.
Thank you for your time. Can you please tell me one last time - is it okay to continue working with the current version (if we do not take into account the situation with the violation of the backup cron)? Or should I update? Is there no automatic update?
I can’t say yes, because the OS (Ubuntu 18.04 LTS) reached the end of standard security maintenance in March 2023 (unless you have a Pro subscription). Also, Hestia has changed a lot, with many bugs fixed and security improvements made since then.
That said, upgrading your current OS and Hestia setup could be risky, as there are too many system and panel upgrades required to reach a fully up-to-date and supported state. I would recommend backing up all user data and restoring it on a fresh installation of a current Ubuntu 24.04 LTS OS with the latest Hestia release 1.9.x.
The latest Hestia releases do include this feature, but I’m not sure whether it was available in version 1.4.x.
