Page 1 of 1

Making multiple backups simultaneous take up all memory (server crash)

Posted: Tue Sep 15, 2015 2:09 am
by SPQ-Koen
Hello everybody,

At our server we currently host around 140 websites with WordPress. We use Installatron to install WordPress and to make daily backups. Since around 2 weeks we notice an extreme memory consumption of the Apache webserver (httpd). We tried everything to find out what was causing this, but finally we noticed that this only occurs when Installatron is making backups.

So we today tried to backup 10 sites simultaneous to test this. In total 6 backups started (in the settings of Installatron we have active tasks set to auto) the other 4 had the status of waiting, and again httpd started to use over 13 GB of memory.We backup to DropBox but i have the feeling that actually creating the backups, is the problem not sending them to DropBox since memory consumption starts directly when the backup is created.

The server we use is a centos 6 with DirectAdmin. The server has 12 GB of RAM and 4 GB of Swapp memory available. When the server uses more then this 12 GB, the Swapp memory is used and of course the disk i/o increases significantly. On normal moments, the server uses a maximum of 4 GB of RAM so this memory spike is very high. Httpd simply starts 30 till 50 new pid's (according to the DirectAdmin Servicemonitor).

Since we now know, that the backups made with Installatron are causing this problem (the entire server stops from working and new requests can not be processed anymore, only after around 30 till 50 minutes the server is okay again), we hope that someone has a clue how to fix this? We also opened a support ticket about 2 weeks ago but we still don't have a reaction from Installatron self ...

Kind regards,

Koen

Re: Making multiple backups simultaneous take up all memory (server crash)

Posted: Tue Sep 15, 2015 2:55 am
by Phil
Hello,

It's possible to reduce the number of concurrent tasks allowed at Installatron Admin > Settings. I would recommend setting this to "1" for a period of time while we investigate the cause.

What's the ticket ID so I can look up what's going on there?

Thank you,
Phil