MySQL service out of memory

[sebastienserre]

Yes, I have increased to 3GB, then 6 and now the max I have => 8gb.
I will see tomorrow if I have the same issue

[nebulon]

oh that is a lot! For which app does this happen or is this happening with more apps? Overall though of course it could also be that the server simply does not have enough memory left to spare, regarless of the upper limit set.

[sebastienserre]

I'm running Dolibarr, Surfer, Sogo, Mastodon Matomo, Stirlingpdf, Freescout, WordPress developer, Miniflux
I will check on my host (Hostinger) log if I have something interesting.

[sebastienserre]

I can see my VPS used 7.47gb/8gb lastnight during the backup.
The fact is, I haven't changed anything, and it was not consuming all this RAM on Cloudron 9.X

[sebastienserre]

Yes, again today with 8gb...

[james]

Hello @sebastienserre
I am looking into it.

[james]

Hello @sebastienserre
Can you please check if there are any Unable to update container in the box.log and maybe older box logs like box.log.1 and so on?

[girish]

Looks like the fix in https://forum.cloudron.io/topic/15767/mysql-service-still-runs-with-the-default-128m-innodb_buffer_pool_size might be the regression .

[sebastienserre]

Sorry I missed your messages.
Last night the backup went OK by deactivating the StirlingPDF apps.
I will restore it from the archive and check the tomorrow logs.

WHere can I find the box.log ?

[girish]

I made a fix to cap innodb_buffer_pool_size now to 1GB. It was quite aggressive previously. @sebastienserre are you already on 10.0.5 ?

[sebastienserre]

Yes I updated yesterday to 10.0.5
That may explain I didn't had the issue in the scheduled backup not in the manual I have tried.
Thanks for the fix