Archiving report issue – Weeks, months, years not working

  • Resolved arfufu

    (@arfufu)


    4 years, 10 months ago

    Bonjour!

    Thanks a lot for this ethical analytics.
    Unfortunately everything looks to work fine except for the reports. I have all visitor logs, and can have the daily reports for each day, but as soon as I want to see weekly or monthly report I have no data at all.
    I checked my DB and even invalidated with your extra plugin / manually emptied all the report tables (blob), but I still get no data and these errors (below). When I try to display again a weekly report, it doesn’t work but the related table in PhPmyAdmin has created many rows (so it seems to be working at the end???)

    Background: I have PHP 7.X , OVH Pro, so I can’t update the settings of MySQL to increase max_allowed_packet. I don’t remeber exactly but I think I tried to install matomo manually before you relaeased the WP plugin, I didn’t manage to make it work, and I installed the WP plugin recently -in march (maybe there is a conflict with the old installation?). I’m not very technical I would need some help sorry.

    Thank you ??

    Diagnostics=
    Dernière exécution d’archivage réussie error L’archivage s’est exécuté avec succès le Samedi 7 mars 2020 17:40:04 soit il y a 45 jours 11:33:22

    Taille maximale des paquets warning Il est important de configurer une taille ‘max_allowed_packet’ dans votre base de données MySQL d’au moins 64MB. 32MB configuré en ce moment.

    archive_main 2020-04-22 04:50:40 1 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:602; CronArchive.php:595; CronArchive.php:330; Access.php:644; CronArchive.php:331; ScheduledTasks.php:225; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;

    Trouleshooting / create the archiving reports =
    Matomo Archive Warnings: ‘Empty or invalid response \’?a:52:{s:10:”2020-03-02″;a:19:{s:35:”Referrers_visitorsFromSearchEngines”;i:0;s:36:”Referrers_visitorsFromSocialNetworks”;i:0;s:33:”Referrers_visitorsFromDirectEntry”;i:0;s:30:”Referrers_visitorsFromWebsites”;i:0;s:31:”Referrers_visitorsFromCampaigns”;i:0;s:41:”Referrers_visitorsFromDirectEntry_percent”;s:2:”0%”;s:43:”Referrers_visitorsFromSearchEngines_percent”;s:2:”0%”;s:39:”Referrers_visitorsFromCampaigns_percent”;s:2:”0%”;s:44:”Referrers_visitorsFromSocialNetworks_percent”;s:2:”0%”;s:38:”Referrers_visitorsFromWebsites_percent”;s:2:”0%”;s:11:”bounce_rate”;s:2:”0%”;s:20:”nb_actions_per_visit”;i:0;s:16:”avg_time_on_site”;i:0;s:26:”avg_time_on_site_returning”;i:0;s:30:”nb_actions_per_visit_returning”;i:0;s:21:”bounce_rate_returning”;s:2:”0%”;s:20:”avg_time_on_site_new”;i:0;s:24:”nb_actions_per_visit_new”;i:0;s:15:”bounce_rate_new”;s:2:”0%”;}s:10:”2020-03-03″;a:19:{s:35:”Referrers_visitorsFromSearchEngines”;i:0;s:36:”Referrers_visitorsFromSocialNetworks”;i:0;s:33:”Referrers_visitorsFromDirectEntry”;i:0;s:30:”Referrers_visitorsFromWebsites”;i:0;s:31:”Referrers_visitorsFromCampaigns”;i:0;s:41:”Referrers_visitorsFromDirectEntry_percent”;s:2:”0%”;s:43:”Referrers_visitorsFromSearchEngines_percent”;s:2:”0%”;s:39:”Referrers_visitorsFromCampaigns_percent”;s:2:”0%”;s:44:”Referrers_visitorsFromSocialNetworks_percent”;s:2:”0%”;s:38:”Referrers_visitorsFromWebsites_percent”;s:2:”0%”;s:11:”bounce_rate”;s:2:”0%”;s:20:”nb_actions_per_visit”;i:0;s:16:”avg_time_on_site”;i:0;s:26:”avg_time_on_site_returning”;i:0;s:30:”nb_actions_per_visit_returning”;i:0;s:21:”bounce_rate_returning”;s:2:”0%”;s:20:”avg_time_on_site_new”;i:0;s:24:”nb_actions_per_visit_new”;i:0;s:15:”bounce_rate_new”;s:2:”0%”;}s:10:”2020-03-04″;a:19:{s:35:”Referrers_visitorsFromSearchEngines”;i:0;s:36:”Referrers_visitorsFromSocialNetworks”;i:0;s:33:”Referrers_visitorsFromDirectEntry”;i:0;s:30:”Referrers_visitorsFromWebsites”;i:0;s:31:”Referrers_visitorsFromCampaigns”;i:0;s:41:”Referrers_visitorsFromDirectEntry_percent”;s:2:”0%”;s:43:”Referrers_visitorsFromSearchEngines_percent”;s:2:”0%”;s:39:”Referrers_visitorsFromCampaigns_percent”;s:2:”0%”;s:44:”Referrers_visitorsFromSocialNetworks_percent”;s:2:”0%”;s:38:”Referrers_visitorsFromWebsites_percent”;s:2:”0%”;s:11:”bounce_rate”;s:2:”0%”;s:20:”nb_actions_per_visit”;i:0;s:16:”avg_time_on_site”;i:0;s:26:”avg_time_on_site_returning”;i:0;s:30:”nb_actions_per_visit_returning”;i:0;s:21:”bounce_rate_returning”;s:2:”0%”;s:20:”avg_time_on_site_new”;i:0;s:24:”nb_actions_per_visit_new”;i:0;s:15:”bounce_rate_new”;s:2:”0%”;}s:10:”2020-03-05″;a:19:{s:35:”Referrers_visitorsFromSearchEngines”;i:0;s:36:”Referrers_visitorsFromSocialNetworks”;i:0;s:33:”Referrers_visitorsFromDirectEntry”;i:0;s:30:”Referrers_visitorsFromWebsites”;i:0;s:31:”Referrers_visitorsFromCampaigns”;i:0;s:41:”Referrers_visitorsFromDirectEntry_percent”;s:2:”0%”;s:43:”Referrers_visitorsFromSearchEngines_percent”;s:2:”0%”;s:39:”Referrers_visitorsFromCampaigns_percent”;s:2:”0%”;s:44:”Referrers_visitorsFromSocialNetworks_percent”;s:2:”0%”;s:38:”Referrers_visitorsFromWebsites_percent”;s:2:”0%”;s:11:”bounce_rate”;s:2:”0%”;s:20:”nb_actions_per_visit”;i:0;s:16:”avg_time_on_site”;i:0;s:26:”avg_time_on_site_returning”;i:0;s:30:”nb_actions_per_visit_returning”;i:0;s:21:”bounce_rate_returning”;s:2:”0%”;s:20:”avg_time_on_site_new”;i:0;s:24:”nb_actions_per_visit_new”;i:0;s:15:”bounce_rate_new”;s:2:”0%”;}s:10:”2020-03-06″;a:19:{s:35:”Referrers_visitorsFromSearchEngines”;i:0;s:36:”Referrers_visitorsFromSocialNetworks”;i:0;s:33:”Referrers_visitorsFromDirectEntry”;i:0;s:30:”Referrers_visitorsFromWebsites”;i:0;s:31:”Referrers_visitorsFromCampaigns”;i:0;s:41:”Referrers_visitorsFromDirectEntry_percent”;s:2:”0%”;s:43:”Referrers_visitorsFromSearchEngines_percent”;s:2:”0%”;s:39:”Referrers_visitorsFromCampaigns_percent”;s:2:”0%”;s:44:”Referrers_visitorsFromSocialNetworks_percent”;s:2:”0%”;s:38:”Referrers_visitorsFromWebsites_percent”;s:2:”0%”;s:11:”bounce_rate”;s:2:”0%”;s:20:”nb_actions_per_visit”;i:0;s:16:”avg_time_on_site”;i:0;s:26:”avg_time_on_site_returning”;i:0;s:30:”nb_actions_per_visit_returning”;i:0;s:21:”bounce_rate_returning”;s:2:”0%”;s:20:”avg_time_on_site_new”;i:0;s:24:”nb_actions_per_visit_new”;i:0;s:15:”bounce_rate_new”;s:2:”0%”;}s:10:”2020-03-07″;a:19:{s:35:”Referrers_visitorsFromSearchEngines”;i:0;s:36:”Referrers_visitorsFromSocialNetworks”;i:0;s:33:”Referrers_visitorsFromDirectEntry”;i:0;s:30:”Referrers_visitorsFromWebsites”;i:0;s:31:”Referrers_visitorsFromCampaigns”;i:0;s:41:”Referrers_visitorsFromDirectEntry_percent”;s:2:”0%”;s:43:”Referrers_visitorsFromSearchEngines_percent”;s:2:”0%”;s:39:”Referrers_visitorsFromCampaigns_percent”;s:2:”0%”;s:44:”Referrers_visitorsFromSocialNetworks_percent”;s:2:”0%”;s:38:”Referrers_visitorsFromWebsites_percent”;s:2:”0%”;s:11:”bounce_rate”;s:2:”0%”;s:20:”nb_actions_per_visit”;i:0;s:16:”avg_time_on_site”;i:0;s:26:”avg_time_on_site_returning”;i:0;s:30:”nb_actions_per_visit_returning”;i:0;s:21:”bounce_rate_returning”;s:2:”0%”;s:20:”avg_time_on_site_new”;i:0;s:24:”nb_actions_per_visit_new”;i:0;s:15:”bounce_rate_new”;s:2:”0%”;}s:10:”2020-03-08″;a:19:{s:35:”Referrers_visitorsFromSearchEngines”;i:0;s:36:”Referrers_visitorsFromSocialNetworks”;i:0;s:33:”Referrers_visitorsFromDirectEntry”;i:0;s:30:”Referrers_visitorsFromWebsites”;i:0;s:31:”Referrers_visitorsFromCampaigns”;i:0;s:41:”Referrers_visitorsFromDirectEntry_percent”;s:2:”0%”;s:43:”Referrers_visitorsFromSearchEngines_percent”;s:2:”0%”;s:39:”Referrers_visitorsFromCampaigns_percent”;s:2:”0%”;s:44:”Referrers_visitorsFromSocialNetworks_percent”;s:2:”0%”;s:38:”Referrers_visitorsFromWebsites_percent”;s:2:”0%”;s:11:”bounce_rate”;s:2:”0%”;s:20:”nb_actions_per_visit”;i:0;s:16:”avg_time_on_site”;i:0;s:26:”avg_time_on_site_returning”;i:0;s:30:”nb_actions_per_visit_returning”;i:0;s:21:”bounce_rate_returning”;s:2:”0%”;s:20:”avg_time_on_site_new”;i:0;s:24:”nb_actions_per_visit_new”;i:0;s:15:”bounce_rate_new”;s:2:”0%”;}s:10:”2020-03-09″;a:19:{s:35:”Referrers_vi’
    ‘1 total errors during this script execution, please investigate and try and fix these errors.’
    ‘1 total errors during this script execution, please investigate and try and fix these errors.’

Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author Thomas

    (@tsteur)

    Thanks @arfufu

    It looks like maybe your WordPress is running out of memory? Could you paste how much memory is available on your server? This is also shown in the system report.

    Thread Starter arfufu

    (@arfufu)

    Hi @tsteur

    Thank you for your reply ??

    Do you mean this one? :
    “Memory Limit 512M
    At least 128MB recommended. Depending on your traffic 256MB or more may be needed.”

    I manually set up 512M a long time ago. I sent all the warnings I have in Diagnotics on my first message.

    • This reply was modified 4 years, 10 months ago by arfufu.
    • This reply was modified 4 years, 10 months ago by arfufu.
    • This reply was modified 4 years, 10 months ago by arfufu.
    Plugin Author Thomas

    (@tsteur)

    Thanks. That should be plenty of memory. Could you maybe send us the full report to wordpress at matomo.org?

    Or maybe you could tell us what it says for these points:

    * Supports Async Archiving
    * Debug Mode Enabled
    * Server Info
    * PHP Version

    Thread Starter arfufu

    (@arfufu)

    Dear @tsteur

    Supports Async Archiving Oui
    Debug Mode Enabled Non
    Server Info Apache
    PHP Version 7.3.16

    You would like me to send the full DIAGNOTICS report? where exactly in matomo.org?

    thanks again for your help

    Plugin Author Thomas

    (@tsteur)

    Thanks again @arfufu . Very much appreciated. By any chance, do you know if on your hoster you can access a so called “PHP error log”? If so, could you maybe check if any error messages appear in that log? It may be worth asking your hoster about it.

    Could you send the full diagnostics report to [email protected] ?

    Thread Starter arfufu

    (@arfufu)

    Dear @tsteur

    I have sent you 2 emails with the full diagnotics report and an error log I found on OVH.
    I just paste here a few lines in case it helps other people in the future:

    ERROR
    [Wed Apr 22 05:27:00 2020] [error] [client 49.148.94.78] [host https://www.serialhikers.com] (104)Connection reset by peer: AH10143: FastCGI: comm with server “/XXXXXXXXX/www/wp-content/plugins/matomo/app/index.php” aborted: read failed, referer: https://www.serialhikers.com/wp-content/plugins/matomo/app/index.php?module=CoreHome&action=index&idSite=1&period=day&date=yesterday
    [Wed Apr 22 08:46:38 2020] [error] [client 49.148.94.78] [host https://www.serialhikers.com] AH10149: FastCGI: incomplete headers (0 bytes) received from server “/XXXXXXXXXXXX/www/wp-content/plugins/matomo/app/index.php”, referer: https://www.serialhikers.com/wp-content/plugins/matomo/app/index.php?idSite=1&period=day&date=yesterday&module=CoreHome&action=index

    WEB
    193.165.97.168 https://www.serialhikers.com – [22/Apr/2020:00:06:40 +0200] “GET /wp-content/plugins/matomo/app/matomo.php?action_name=Hitchhiking%20World%20Tour%20-%20SerialHikers%20Alternative%20Travel%20Blog&idsite=1&rec=1&r=270154&h=0&m=6&s=40&url=https%3A%2F%2Fwww.serialhikers.com%2Fhome%2F&_id=9dd0c69f400fd6ef&_idts=1587497203&_idvc=4&_idn=0&_refts=0&_viewts=1587506800&send_image=1&cookie=1&res=375×812&gt_ms=5488&pv_id=lU59ID HTTP/1.1” 200 46 “https://www.serialhikers.com/home/” “Mozilla/5.0 (iPhone; CPU iPhone OS 13_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.4 Mobile/15E148 Safari/604.1”
    91.134.248.235 https://www.serialhikers.com – [22/Apr/2020:00:03:55 +0200] “POST /wp-cron.php?doing_wp_cron=1587506635.4086461067199707031250 HTTP/1.1” 200 25 “https://www.serialhikers.com/wp-cron.php?doing_wp_cron=1587506635.4086461067199707031250” “WordPress/5.4; https://www.serialhikers.com”
    93.35.245.29 https://www.serialhikers.com – [22/Apr/2020:00:03:54 +0200] “GET /wp-content/plugins/matomo/app/matomo.php?action_name=Tour%20du%20Monde%20en%20stop%20-%20hitchhiking%20World%20Tour%20-%20%C3%A9cologique%2C%20%C3%A9conomique&idsite=1&rec=1&r=604429&h=0&m=3&s=54&url=https%3A%2F%2Fwww.serialhikers.com%2F&_id=65c9ddb233d2acef&_idts=1587506634&_idvc=1&_idn=0&_refts=0&_viewts=1587506634&send_image=1&cookie=1&res=375×812&gt_ms=68&pv_id=MQYR9i HTTP/1.1” 200 46 “https://www.serialhikers.com/” “Mozilla/5.0 (iPhone; CPU iPhone OS 13_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.5 Mobile/15E148 Safari/604.1”

    I have no idea what it means. I didn’t send you the full WEB report as I don’t think it’s related to errors. But if you need it tell me, I will.

    • This reply was modified 4 years, 10 months ago by arfufu.
    • This reply was modified 4 years, 10 months ago by arfufu.
    Plugin Author Thomas

    (@tsteur)

    Thanks for this @arfufu very appreciated. I’m looking into the email you sent and do some research based on these logs and hoping to find something. Will also get the team to look into it.

    Does the error also happen if you click on Diagnostics -> Troubleshooting and there click on the button “Archive reports”?

    Plugin Author Thomas

    (@tsteur)

    Actually, sorry I can see in the logs you have tried that already and it is failing there as well.

    Plugin Author Thomas

    (@tsteur)

    @arfufu different question. Could you temporarily edit your wp-config.php and add this line:

    define( 'WP_DEBUG', true );

    Then go to Diagnostics -> Troubleshooting and click on the “Archive reports” button?

    After that be interesting if directly some error or warning appears, or whether maybe some different message appears in the system report under the section “Logs”.

    Then you could remove that line again.

    Sorry about all that. From researching it seems that something crashes for some reason but it’s hard to guess what it could potentially be without directly having access to the system.

    BTW: Do you mind letting us know what hoster you are with?

    Thread Starter arfufu

    (@arfufu)

    Dear @tsteur

    Thank you again ??
    I changed WP_DEBUG to TRUE, and I have this notification at the top of my administration:
    “Deprecated: contextual_help est obsolète depuis la version 3.3.0 ! Utilisez get_current_screen()->add_help_tab(), get_current_screen()->remove_help_tab() à la place. in /XXXXXX/www/wp-includes/functions.php on line 5088”

    I went to troubleshooting and clicked on “Archive reports” and something wrong happens (I guess): it seems that the source code of the page appears, starting with
    <!DOCTYPE html>
    <!–[if IE 8]>
    blabla … …
    I can go back but the same happens if I start to click again on “archive reports”.

    If you want the full code I can send you by email?

    I came back to WP_DEBUG FALSE and the notification at the top disappeared and it came back as “normal: When I click on “archive reports” I have like before:
    Matomo Archive Warnings: ‘Empty or invalid response \’?a:52:{s:10:”2020-03-04″;a:19:

    You want to know my host? yes OVH, the “pro” plan. I found this thread where we can see in the comments that 1 guy has a mutualized OVH and matomo works, and another guy also but matomo reports don’t work:
    https://forum.matomo.org/t/message-derreur-chez-ovh/26931/12

    • This reply was modified 4 years, 10 months ago by arfufu.
    Plugin Author Thomas

    (@tsteur)

    Be great if you could send the full source code of the page to us by email.

    I’ve tried to install the same plugins and can’t quite reproduce the issue yet. We’re a bit puzzled and don’t fully understand yet what happens. We’ll have a look again on Tuesday as it’s already weekend here and we have a public holiday on Monday. Sorry about that.

    In case you’re familiar with editing files on your server, if you could add these 3 lines https://github.com/matomo-org/wp-matomo/commit/b0d0d1207d07da988fb593e4e2ef736082331591#diff-ca76420ccf40e7866f7032f87693bb2dR79-R82 in the file wp-content/plugins/matomo/classes/WpMatomo/Admin/SystemReport.php then we’d maybe see the full error message the next time this error happens.

    This change will also be included in our next release.

    Thanks

    Thread Starter arfufu

    (@arfufu)

    Hi @tsteur

    thanks again.
    Something changed since my last message. I just checked the reports are showing now (weekly, monthly). I don’t know what happened, maybe the WP_DEBUG thing (even if it went wrong)?

    Now in Diagnostics I have this notification at the top:
    “Il y a quelques problèmes avec votre système. Matomo va démarrer, mais vous pourriez rencontrer quelques problèmes mineurs. Voir ci-dessous pour plus d’informations.”

    And I still have the yellow warnings but not anymore the red one saying the reports didn’t work. I sent you the full new diagnotics report too by email.

    I will make some more tests, edit the files in my FTP as you suggested, try again WP_DEBUG during the weekend.

    Enjoy your holidays!

    Thread Starter arfufu

    (@arfufu)

    Hi,

    I don ‘t know if it’s related, but in case it helps, I installed a plugin to check CRON and I found that 1 of the matomo cron has a warning (no action);
    Hook: puc_cron_check_updates-matomo
    Action: Aucun

    And since a while in SITE HEALTH of WP I have this issue that I didn’t manage to fix:
    Erreur Une extension a empêché les mises à jour en désactivant wp_version_check().
    Not due to one of my plugin as I already tried to deactivate everything and put a WP theme, didn’t change a thing.

    Later I have run again with WP_DEBUG true, got the same problem (source code showing), and when i went back to WP_DEBUG false and tried again to click on “archive reports” I didn’t get any warning for the first time, but nothing saying that it has been done correctly neither ( don’t know what should appear in a normal case ).

    I also added the 3 new lines in SystemReport.php and we will if the error comes back ??

    • This reply was modified 4 years, 10 months ago by arfufu.
    Plugin Author Thomas

    (@tsteur)

    > I also added the 3 new lines in SystemReport.php and we will if the error comes back ??

    Awesome, thanks for that!

    Seems a bit of a mystery. If the “puc_cron_check_updates” and “wp_version_check” fails it seems maybe your server is trying to connect to some external server but it is failing.

    The updated system report looks pretty much good. It be great to have an eye on it to see if it happens again. I see you have enabled “InvalidateReports” plugin as well. Did this maybe start happening after invalidating some reports by any chance?

    Thread Starter arfufu

    (@arfufu)

    Hi @tsteur

    I have no idea what is the reason for these issues “puc_cron_check_updates” and “wp_version_check” …

    Indeed it seems to be ok now, I just checked the Diagnostics:
    Archive Next run: 2020-04-28 04:50:21 (17 min 10s) Last started: 2020-04-28 03:52:44 (-40 min 27s). Last ended: 2020-04-28 03:52:45 (-40 min 26s). Interval: hourly
    As you say, it’s a mistery… Will see if archiving still works in the next days ??

    I just have still this warning but I can’t change it in a mutualized OVH server:
    Taille maximale des paquets warning Il est important de configurer une taille ‘max_allowed_packet’ dans votre base de données MySQL d’au moins 64MB. 32MB configuré en ce moment.

    No, InvalidateRports I installed it afterwards when I tried everything from your troubleshooting documentation. When I invalidated reports and clicked on “Archive reports” few days ago it didn’t work.

    Thank you for your help.
    Sorry I have a last question: I read all your documentation and didn’t find it possible to make matomo work on another database, using this “all-in-one” WP plugin (but I know it’s possible with the manual installation ?? Will it be a futur feature?

    Have a good day!

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Archiving report issue – Weeks, months, years not working’ is closed to new replies.