I hate getting these messages when running core:archive in Matomo.
My Matomo server is a $5 shared space hosted on Digital Ocean, the cheapest deployment, the least memory, all minimal RAM, CPUs, everything. Frustrated by these errors, I learned to overcome these errors by running console core:archive manually and changing options until it runs well. Here are the things I do. 1. Incrementally run longer time spans. I run today and yesterday. Then this month. Then forever. 2. Run it once with no segments. Then run it with segments. 3. Run it with the PHP memory allocation declared at run time. Case 1: Got errors during the archiving, in the section before scheduled tasks. Added the option --skip-all-segments. Still errors. Deleted the segment from the UI. Success! (Not sure why the option didn't do the trick.) Case 2 (September 2024 update) 1. Tons of errors: sudo su www-data -s /bin/bash -c "php -d memory_limit=8G /var/www/matomo/console core:archive" 2. Zero errors: sudo su www-data -s /bin/bash -c "php -d memory_limit=8G /var/www/littlefurnace.com/matomo/console core:archive --skip-all-segments --force-idsites=2" Conclusion: On underpowered servers, you can eliminate errors by doing one site at a time and by skipping segments." Then go back and do the segments, still doing only one site at a time 3. sudo su www-data -s /bin/bash -c "php -d memory_limit=8G /var/www/littlefurnace.com/matomo/console core:archive --force-idsites=1"
0 Comments
|
Troubleshooting + Deploying Matomo
Archives
December 2024
Categories |