thinkjarvis
Basic Pleskian
Unfortunately this leads me nicely back in the same circle again
We have not been able to identify anything unusual about the clients website setup that would cause high usage of phpfpm that could be classed as excessive.
Mysql continues to clime continually throughout the day.
The phpfpm is stable and consistent - It is the mysql memory and mariadb memory that is filling uncontrollably.
The only correlation is that process manager is reporting 100% ram usage at the moments leading to mariadb being killed - mariadb is occupying approx 90% of it and system the 0ther 10% inclusive of cache values.
It shouldnt kill mariadb - mariadb shouldnt be occupying the entire ram?
We have not been able to identify anything unusual about the clients website setup that would cause high usage of phpfpm that could be classed as excessive.
Mysql continues to clime continually throughout the day.
The phpfpm is stable and consistent - It is the mysql memory and mariadb memory that is filling uncontrollably.
The only correlation is that process manager is reporting 100% ram usage at the moments leading to mariadb being killed - mariadb is occupying approx 90% of it and system the 0ther 10% inclusive of cache values.
It shouldnt kill mariadb - mariadb shouldnt be occupying the entire ram?