We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Backup crashing server - Cannot allocate memory
Backup crashing server - Cannot allocate memory
Hi everyone,
I am running a LXC container with VestaCP on Proxmox.
At 5:10 every day the backup kicks off.
gzip/tar takes up 100% of the CPU trying to compress the mail.
The swap slowly goes to 100% and the server becomes unresponsive.
(It gets stuck on a user with a collective mail size of about 30 GB.)
The server then turns off completely.
Upon turning the server back on, the vesta service does not start automatically so I have to start it manually.
This has been happening for the last couple of days.
At one stage I think that there may not have been enough drive space, but i have since double the drive space, memory, CPU's and swap.
I have also tried to remove the swap completely. Nothing makes any difference.
Allocated specs
8 CPUs/8GB Memory/4GB SWP/256GB HDD (19% used)
Debian 9
Please help.
I am running a LXC container with VestaCP on Proxmox.
At 5:10 every day the backup kicks off.
gzip/tar takes up 100% of the CPU trying to compress the mail.
The swap slowly goes to 100% and the server becomes unresponsive.
(It gets stuck on a user with a collective mail size of about 30 GB.)
The server then turns off completely.
Upon turning the server back on, the vesta service does not start automatically so I have to start it manually.
This has been happening for the last couple of days.
At one stage I think that there may not have been enough drive space, but i have since double the drive space, memory, CPU's and swap.
I have also tried to remove the swap completely. Nothing makes any difference.
Allocated specs
8 CPUs/8GB Memory/4GB SWP/256GB HDD (19% used)
Debian 9
Please help.
Last edited by afm on Sat Jan 20, 2018 10:09 am, edited 1 time in total.
Re: Backup crashing server - Cannot allocate memory
In addition to this,
When deleting users from the VestaCP, it fails to delete lines from some of the service configs.
nginx and apache2 fail to start and I have to manually go into the vesta.conf files and remove the line of the deleted user.
When deleting users from the VestaCP, it fails to delete lines from some of the service configs.
nginx and apache2 fail to start and I have to manually go into the vesta.conf files and remove the line of the deleted user.
Re: Backup crashing server - Cannot allocate memory
Hi,
Can you provide access to your server, we will try to help you.
Can you provide access to your server, we will try to help you.
Re: Backup crashing server - Cannot allocate memory
Thanks for your reply.
I have sent you a PM.
In case PM's are not allowed:
I can provide access, but I'm not sure what the process is.
I have managed to zip the mail files for the large user and it doesn't crash the server like gzip.
I have set up a Centos 7 VM and have tried to restore some of the working backups but get the following error:
[root@linux01 backup]# v-restore-user admin admin.2018-01-21_05-10-01_2.tar
Error: invalid backup format :: admin.2018-01-21_05-10-01_2.tar
I have tried all fixes that I can find on the forums with no luck.
I have sent you a PM.
In case PM's are not allowed:
I can provide access, but I'm not sure what the process is.
I have managed to zip the mail files for the large user and it doesn't crash the server like gzip.
I have set up a Centos 7 VM and have tried to restore some of the working backups but get the following error:
[root@linux01 backup]# v-restore-user admin admin.2018-01-21_05-10-01_2.tar
Error: invalid backup format :: admin.2018-01-21_05-10-01_2.tar
I have tried all fixes that I can find on the forums with no luck.