Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cron: archive not working #14404

Closed
bahooha opened this issue May 2, 2019 · 8 comments
Closed

Cron: archive not working #14404

bahooha opened this issue May 2, 2019 · 8 comments
Labels
answered For when a question was asked and we referred to forum or answered it.
Milestone
3.10.0

Comments

@bahooha
Copy link

bahooha commented May 2, 2019 •
edited

I have archiving via CRON set up as per: https://matomo.org/docs/setup-auto-archiving/#linux-unix-how-to-set-up-a-crontab-to-automatically-archive-the-reports

This has worked perfectly for years, but unfortunately since a couple of weeks not anymore. I'm not sure if this is since the update to 3.9.1 or if it has started failing earlier. If I understand correct, the update to Matomo 3.9.1 has been installed on March 22 and the error/not working cron started on April 3rd.

On this day I've recieved an error email from cron:

[Exception]                                                                                    
2 total errors during this script execution, please investigate and try and fix these errors.  

core:archive [--url="..."] [--force-all-websites] [--force-all-periods[="..."]] [--force-timeout-for-periods[="..."]] [--skip-idsites[="..."]] [--skip-all-segments] [--force-idsites[="..."]] [--force-periods[="..."]] [--force-date-last-n="..."] [--force-date-range[="..."]] [--force-idsegments="..."] [--concurrent-requests-per-website[="..."]] [--concurrent-archivers[="..."]] [--disable-scheduled-tasks] [--accept-invalid-ssl-certificate] [--php-cli-options[="..."]]

At the times the CRON fires, I can see that the archive.log file is being updated, but shows an empty response. I can't find anything in the error logs.

When I manually trigger the archive.php as described in https://matomo.org/docs/setup-auto-archiving/#web-cron-when-your-web-host-does-not-support-cron-tasks I get the following error:

Full definition:
Object (
    class = Piwik\Plugins\Monolog\Formatter\LineMessageFormatter
    scope = singleton
    lazy = false
    __construct(
        $logMessageFormat = #UNDEFINED#
        $allowInlineLineBreaks = (default value) true
    )
)

I have checked if all files are available against a clean install. Nothing seems wrong.

Can anybody shed any light on this?
@tsteur
Copy link
Member

tsteur commented May 2, 2019

Looking at the code it does sound like some files are missing. Make sure you have the latest version and try maybe again to update the code using the manual 3 step update: https://matomo.org/docs/update/#the-manual-three-step-update

In case you're installing Matomo from git: that's not really recommended.

@bahooha
Copy link
Author

bahooha commented May 2, 2019

I had already checked file integrity, but to be sure I've followed the steps from your link: no avail.

File are 100% identical to a clean installation.

Any other ideas?

@tsteur
Copy link
Member

tsteur commented May 2, 2019 •
edited

Do you have some config/config.php created? Or maybe the plugin Monolog is not active?

@tsteur
Copy link
Member

tsteur commented May 2, 2019

In general we're not seeing this problem somewhere else, so it looks like some configuration or server issue.

@bahooha
Copy link
Author

bahooha commented May 2, 2019

I do not understand why, but it turns out the Monolog plugin was inactive.

Thank you very much for your help, Thomas!

@bahooha bahooha closed this as completed May 2, 2019
@tsteur
Copy link
Member

tsteur commented May 2, 2019

Awesome, glad you found it

@tsteur tsteur added the answered For when a question was asked and we referred to forum or answered it. label May 2, 2019
@tsteur tsteur added this to the 3.10.0 milestone May 2, 2019
@thelfensdrfer
Copy link

Just wanted to say that I had the exact same error. Did we disable the plugins ourselves or did it happen automatically?

@tsteur
Copy link
Member

tsteur commented May 11, 2019

Shouldn't have happened automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
3.10.0
Development

No branches or pull requests
3 participants
@tsteur @thelfensdrfer @bahooha