Hi. Yes, I can’t even get the splash page to login. I have upped the memory, given it lots of swap. We have gone from a 4GB machine with 4GB of swap to an 8Gb machine with 8Gb swap.
Have just started seeing something similar on our install of Matomo. Been running fine for a year. Initial PHP memory limit was 128M, which we raised to 256M, and then finally 512M. It was running like that for about 6 months. Upgraded to 5.x last month. Now, today we noticed memory exhaustion messages going back to Feb 5th (sorry, no logs from further back available), and raised memory to 750M, 1G and finally 2G before it would start working. Is it possible changes to code in 5.x have contributed to this?
WRT the original poster, you shouldn’t have your PHP memory_limit greater than the amount of RAM in your machine! And as the machine is also running mysql etc, then probably the most you can try is ~ 4Gb i.e half installed RAM.
To update Mark’s post (I am a colleague): we’ve now increased to a 15GB PHP memory limit - and we’re still running out of memory.
Monolog is throwing the error, regardless of it being enabled. Matomo is in maintenance mode. We cannot even log in; Matomo runs out of memory before displaying the login page.
Issues began less than a week after upgrading to Matomo 5. Until the upgrade we ran on Matomo 4 with 128MB PHP memory for literally years, trouble-free.
We have downgraded to 4.13.1 and its working. We have lost weeks of processing I guess, had to go back 2 weeks. We have updated php to 8.3 from 8.0 and its still sound. We are a big site Luke says … so it potentially a performance issue.
Fishing around for answers myself. Do you have anything in your mysql slow_query_log? I’ve got a couple of queries running for 30 and 40 seconds, which is quite a grind. Not sure if its related, but certainly odd.