Hi all. When we moved from phpbb 3.0 to 3.2, we decided to use the newest version of the database server on AWS.
It turned out that this version has a slow memory leak that would cause the server to stall for an hour, and then reboot on a 3 day cycle..
What we did was double the size of the memory on the database, and this made the system last about a month, but stall for 2-3 hours before rebooting as the memory filled up. Obviously not a solution.
I tried tweaking all kinds of database settings and also upgraded to a new subversion that claimed to fix the problem, but neither approach worked. I had planned on downgrading the database next week, but noticed that the system had stalled and rebooted twice in the last week, and was hung this morning.. so i took the system down and did the downgrade. Total downtime was around 6 hours.. mostly because the size of our database is just enormous and takes eons to process.
Sorry for no heads up on the downtime. I figured sunday morning was an ideal time to tackle the problem while the system was down already.
Here's hoping that the problem is cured once and for all. If not, there's more tricks up my sleeve, but i've already blown collectively ~18 hours on this problem so ... cross your fingers for me, fellas.
It turned out that this version has a slow memory leak that would cause the server to stall for an hour, and then reboot on a 3 day cycle..
What we did was double the size of the memory on the database, and this made the system last about a month, but stall for 2-3 hours before rebooting as the memory filled up. Obviously not a solution.
I tried tweaking all kinds of database settings and also upgraded to a new subversion that claimed to fix the problem, but neither approach worked. I had planned on downgrading the database next week, but noticed that the system had stalled and rebooted twice in the last week, and was hung this morning.. so i took the system down and did the downgrade. Total downtime was around 6 hours.. mostly because the size of our database is just enormous and takes eons to process.
Sorry for no heads up on the downtime. I figured sunday morning was an ideal time to tackle the problem while the system was down already.
Here's hoping that the problem is cured once and for all. If not, there's more tricks up my sleeve, but i've already blown collectively ~18 hours on this problem so ... cross your fingers for me, fellas.