How to diagnose errors from core:archive action?

@scottnonnenberg wrote:

Hi there. I've been getting errors from my core:archive runs lately, but I don't even know where to find the errors so I can start tracking down the problem!

Here's what I get from the actual core:archive action - it's not so useful:

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


Exception trace:
 () at /tools/piwik/core/CronArchive.php:410
 Piwik\CronArchive->logFatalError() at /tools/piwik/core/CronArchive.php:403
 Piwik\CronArchive->end() at /tools/piwik/core/CronArchive.php:262
 Piwik\CronArchive->Piwik\{closure}() at /tools/piwik/core/Access.php:456
 Piwik\Access::doAsSuperUser() at /tools/piwik/core/CronArchive.php:263
 Piwik\CronArchive->main() at /tools/piwik/plugins/CoreConsole/Commands/CoreArchiver.php:27
 Piwik\Plugins\CoreConsole\Commands\CoreArchiver->execute() at /tools/piwik/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:257
 Symfony\Component\Console\Command\Command->run() at /tools/piwik/vendor/symfony/console/Symfony/Component/Console/Application.php:874
 Symfony\Component\Console\Application->doRunCommand() at /tools/piwik/vendor/symfony/console/Symfony/Component/Console/Application.php:195
 Symfony\Component\Console\Application->doRun() at n/a:n/a
 call_user_func() at /tools/piwik/core/Console.php:79
 Piwik\Console->Piwik\{closure}() at /tools/piwik/core/Access.php:456
 Piwik\Access::doAsSuperUser() at /tools/piwik/core/Console.php:80
 Piwik\Console->doRun() at /tools/piwik/vendor/symfony/console/Symfony/Component/Console/Application.php:126
 Symfony\Component\Console\Application->run() at /tools/piwik/console:27

My first step was to check my php5-fpm logs on both piwik machines (since I'm running behind nginx, two load-balanced instances). Nothing, even though I've set catch_workers_output = yes in my www.conf file.

Then I checked out diagnostics, and things are looking good there. All green checks except for a LOAD DATA INFILE error under Database abilities and "not using one of the recommended providers" under Geolocation. So that doesn't seem to be the problem.

Finally I installed the LogViewer plugin and re-ran a few failing core:archive actions, but I'm still getting this error when I try to view the logs:

Specified path to log file does not exist: /tools/piwik/tmp/logs/piwik.log

I'm confused, because the tmp directory is there and I have the recommended defaults in my config.ini.php:

[log]
; Possible values are "screen" (default value), "file" and "database" (logs to tables logger_*)
log_writers[] = file
; Possible values are ERROR, WARN, INFO, DEBUG
log_level = WARN
; if configured to log to file, log entries will be written to this file
logger_file_path = tmp/logs/piwik.log

What's my next step? Is the LogViewer even the right thing to try to diagnose this? Is there an extra-verbose mode for the core:archive command that would give me more information?

PS: You may be wondering if these errors are real problems. Seems like they definitely are. I seem to be capturing all new visits, because they're hitting my Visitor Log, but very few other tables and charts show data. I've been using Piwik for almost three years now, and this is the only major failure I've run into on an upgrade. Would really appreciate some help!

Posts: 5

Participants: 2

Read full topic