Can't create backup, can't parse error
Can't create backup, can't parse error
Hello,
I tried to create a backup, and i realized it stops working, /var/log/vesta/backup.log says "Error: can't parse config /home/admin/conf/web/apache2.conf" .
Then it's trying to create the backup again and again, i have a lot of temp directory under /backup...
Any ideas? And how to stop it until i solve the problem? I've tried to kill the gzip process, also tried to reboot the whole system, but it's trying to create the backup anyway...
Thanks for help!
I tried to create a backup, and i realized it stops working, /var/log/vesta/backup.log says "Error: can't parse config /home/admin/conf/web/apache2.conf" .
Then it's trying to create the backup again and again, i have a lot of temp directory under /backup...
Any ideas? And how to stop it until i solve the problem? I've tried to kill the gzip process, also tried to reboot the whole system, but it's trying to create the backup anyway...
Thanks for help!
Re: Can't create backup, can't parse error
Hello,
Finally i found the cron job what made the backups, deleted it, and tried to make the backup using commandline. Same error again, so i changed the apache2.conf file to a previous version from a backup, and now it's working. I could set up the backup to a remote ftp server without any problem too. :)
Thanks for help!
Finally i found the cron job what made the backups, deleted it, and tried to make the backup using commandline. Same error again, so i changed the apache2.conf file to a previous version from a backup, and now it's working. I could set up the backup to a remote ftp server without any problem too. :)
Thanks for help!
XoXiLhJ0mn wrote:Hi,
I am sure that the installer did not install a backup ghost on your server, or did it ;) But it did install crons to run backups. All you need to do is to deactivate the cron that executes backups. Thats all and so easy.
Generally speaking I would advise everyone to use CLI instead of web interface. Using web interface, there are some additional parameters that comes into the game and they could create some extra troubles. But ofcourse, the choice is yours.
One solution to a similar ptoblem I found wa to create a DUMMYUSER. Move all existing domains and databases ownerships to the DUMMYUSER account. Delete the OLDUSER. CREATE a new user with the same name (or different one, if possible) OLDUSER. Then shift all the domains and databases back to the OLDUSER.
With this system, all the conf files are recreated AFTER A NEW UNIX USER WITH THE SAME NAME is newly created as OLDUSER. This will also rebuild all files and install everything properly.
Ofcourse, as the backup system is not working, you shall need to make a manual backup of certain directories, like html/mail/db before you begin such an operation.
Let me know if you need more help or have questions.