Hello
I’m using Matomo for the first time, and have installed it in a WordPress site on a project development server, set up so that it tracks me and the site owner – the two people who are working on this website. This is so that I can get a feel for how it works and the reports it generates.
All worked well for a week or two, until I noticed it had stopped showing data, both in the WP summary area and in the more detailed reports.
There, it said:
"Oops… there was a problem during the request. Maybe the server had a temporary issue, or maybe you requested a report with too much data. Please try again. If this error occurs repeatedly please contact your Matomo administrator for assistance."
I went through the steps on the troubleshooting page: https://matomo.org/faq/wordpress/matomo-for-wordpress-is-not-showing-any-statistics-not-archiving-how-do-i-fix-it/ and noticed that the cron job had stopped working a few days previously, on the same day that the Akeeba Backup plugin wasn’t able to complete a site backup.
Working through that troubleshooting page, I wasn’t able to activate manual archiving. Standard WP debugging didn’t give me any clues either, but I found this page: https://matomo.org/faq/wordpress/my-wp-cron-is-not-working-how-do-i-enable-browser-archiving/ about browser archiving.
I enabled this, and Matomo > Summary showed me the following error:
"Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in mysite.com/wp-content/plugins/akeebabackupwp/app/Solo/engine/Psr/Log/AbstractLogger.php on line 135.
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0"
Lines 133–135 of that Akeeba file say:
public function debug($message, array $content = [])
{
$this->debug($message, $context);
}
I disabled Akeeba Backup, and Matomo started working again. It was tracking visits, running the cron and showing reports.
When I reenabled/reinstalled it, Matomo stopped working again. And Akeeba also wasn’t able to make a backup. According to the progress report, it stopped when it got to the Matomo directory.
I then excluded the Matomo directory from the backups, and they now complete OK, although Matomo doesn’t work. It’s also not ideal that the Matomo info isn’t included in the backups.
At some point during all this a fatal WordPress error occurred. From the email it triggered:
"An error of type E_ERROR was caused in line 135 of the file XXX"
(the same line in the same Akeeba Backup file mentioned above.)
My guess is that there isn’t an incompatibility between Matomo and Akeeba Backup, but rather a lack of server resources that is impacting both of these plugins and/or how they interact with each other.
Somewhere along the line I also increased the PHP memory limit to 512MB.
What seems to be the actual problem here? Lack of disc space? Lack of database capacity? Lack of server memory?
Would installing the on-premises version of Matomo instead of the WP version make a difference? Or do I need to address disc space/database capacity/server memory first?
I’d really appreciate some expert input, as I’d love to get this working and ideally use Matomo on other projects. And sorry for the long post. I thought I’d better explain things as well as possible.
Thanks, Paul
