Cron job failing - no error message to be found

Ever since this morning, our archive cron job has been failing with the following error:

$ /usr/bin/php5 /srv/www/ core:archive --url=

1 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[=“…”]] [–force-idsites[=“…”]] [–force-periods[=“…”]] [–force-date-last-n=“…”] [–force-date-range[=“…”]] [–concurrent-requests-per-website[=“…”]] [–disable-scheduled-tasks] [–accept-invalid-ssl-certificate] [–xhprof]

There are no errors logged to the syslog (which is PHP’s error_log setting) or the Apache error logs. I’ve even tried adding

log_writers = “file”
to the config.ini.php file and nothing is logged there either. Any ideas how I can fix this error? Currently running Piwik 2.11.1.

Could you run console core:archive with the “-v” option (verbose). It will show more log information.

$ /usr/bin/php5 /srv/www/ core:archive --url=  -v

I don’t understand why no log is showing here because clearly it should, even without the verbose option… Or maybe the error happened so early in the process that nothing got logged prior to that.

FYI nothing is logged to file when running with the console, the reason for that is simply that all log gets sent to the output, so putting it into the file would be redundant and just pollute the log file with information you already have.

Well in your case you don’t have that information :slight_smile: but that’s not the normal behavior…

OK, running with -v gives the following exception:

Exception trace:
 () at /srv/www/
 Piwik\CronArchive->logFatalError() at /srv/www/
 Piwik\Plugins\CoreConsole\Commands\CoreArchiver->execute() at /srv/www/
 Symfony\Component\Console\Command\Command->run() at /srv/www/
 Symfony\Component\Console\Application->doRunCommand() at /srv/www/
 Symfony\Component\Console\Application->doRun() at n/a:n/a
 call_user_func() at /srv/www/
 Piwik\Console->Piwik\{closure}() at /srv/www/
 Piwik\Access::doAsSuperUser() at /srv/www/
 Piwik\Console->doRun() at /srv/www/
 Symfony\Component\Console\Application->run() at /srv/www/

Does that help pinpoint the issue at all?

Nope :frowning:

You really have no other output before this? Are you running the command manually in a terminal or is it a cron job?

If you really can’t solve it you could try editing the core/CronArchive.php file at line 828 (see the line on GitHub: You could change the function to this:

    public function log($m)
        $this->output .= $m . "\n";
        echo $m . "\n";

That way at least the messages should show on the output and it will help you debug.

OK, changing the log method got the error to appear:

Error: Got invalid response from API request: Response was 'task,output Piwik\Plugins\UserCountry\GeoIPAutoUpdater.update,ERROR: GeoIPAutoUpdater: failed to download '' to '/srv/www/': Error while creating the file: /srv/www/'

It appears that the web server couldn’t write the GeoIP files to the “misc” directory, so I’ve changed the permissions on it to allow that (after ensuring PHP was disabled in that dir). After changing the permissions the cron job runs without an error. Interestingly, the “misc” directory didn’t come up in the list of directories requiring write access when I ran the system test from the admin area.

Still unsure why the logger isn’t outputting anything. I had the same output (or lack of it) whether it was running from cron or the command line.

Ah I didn’t think of that sooner but now the logger is in a plugin (just for the sake of organizing the code better). But maybe when you updated the plugin’s file were not installed (random updater failures happen sometimes), or maybe for whatever reason the plugin is not enabled…

Try running this command:

./console plugin:activate Monolog

You should see “The plugin is already activated”. If you see something else, that should tell you if it wasn’t activated (that means a 2.11 upgrade was not executed correctly) or if the plugin wasn’t installed correctly during the update.

It looks like the plugin wasn’t activated, enabling the Monolog plugin seems to have fixed the log output. There’s a possibility that I forgot to set the permissions on config.ini.php when doing the upgrade to 2.11, so that might have been the cause. I’ll make sure I don’t forget that in future updates…

Thanks for your help!

I’m happy to finally know the source of the problem :slight_smile: