Fatal error in CRON

  • Here is a stack trace of VP blowing up in cron; PHP 7.3.3 (cli)
    Our CRON is run via WP-CLI
    wp cron event run --due-now

    Fatal error: Uncaught Error: Cannot use object of type VP_FileScan as array in /srv/users/<redacted>/apps/<redacted>/public/wp-content/plugins/vaultpress/cron-tasks.php:111
Stack trace:
#0 /srv/users/<redacted>/apps/<redacted>/public/wp-includes/class-wp-hook.php(286): VP_Site_Scanner->_scan_batch()
#1 /srv/users/<redacted>/apps/<redacted>/public/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array)
#2 /srv/users/<redacted>/apps/<redacted>/public/wp-includes/plugin.php(531): WP_Hook->do_action(Array)
#3 phar:///opt/sp/bin/wp-cli.phar/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(288): do_action_ref_array('vp_scan_next_ba...', Array)
#4 phar:///opt/sp/bin/wp-cli.phar/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(259): Cron_Event_Command::run_event(Object(stdClass))
#5 [internal function]: Cron_Event_Command->run(Array, Array)
#6 phar:///opt/sp/bin/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(93): call_user_func(Array, Array, Array)
#7 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(A in /srv/users/<redacted>/apps/<redacted>/public/wp-content/plugins/vaultpress/cron-tasks.php on line 111
Viewing 8 replies - 1 through 8 (of 8 total)

  • Just came here to report the same thing.

    I’m running the nightly core build with the beta tester plugin. I got the recovery email after it crashed overnight (it works!). I suspect it happened after an auto-update to JP to the version released yesterday. 

    Error Details 
============= 
An error of type E_ERROR was caused in line 111 of the file /wp-content/plugins/vaultpress/cron-tasks.php. Error message: Uncaught Error: Cannot use object of type VP_FileScan as array in /wp-content/plugins/vaultpress/cron-tasks.php:111 
Stack trace: 
#0 /wp-includes/class-wp-hook.php(286): VP_Site_Scanner->_scan_batch() 
#1 /wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array) 
#2 /wp-includes/plugin.php(531): WP_Hook->do_action(Array) 
#3 /wp-cron.php(133): do_action_ref_array('vp_scan_next_ba...', Array) 
#4 {main} 
thrown

    Hi there, thanks for reporting this, and sorry for the trouble.

    We have checked with our developers in regards to this error and this seems to happen when the security scanner uses a cached result stored in the options table. Any time this happen, it usually only happens once, then continues on as normal.

    With that being said, could you please keep monitoring your site to see if this error happens more than once?

    I’ll pass the info right away to our developers and we’ll take it from there then.

    Thanks for helping sort this out with us ??

    Thread Starter Danny Froberg

    (@dfroberg)

    Hi Stef,
    It’s happening every 5 minutes.

    Hey Danny,

    Thanks for the quick follow up. I’ll pass that info to our developers who are already working on that.

    We hope to share some good news soon; in the meantime if you notice something new worth a mention, please share it right away.

    Thanks!

    Yep, same here. Mine trips up again the next time the cron runs if I exit recovery mode.

    While our developers are deploying a definitive fix, what you all could try to do is to update to 1.9.9 (if you haven’t done it already), and the click on the “Delete all VaultPress Settings” button.

    This will delete the ‘_vp_current_scan’ row from the options table that triggers the PHP fatal.

    Please let us know how it goes and if you’re still getting these PHP fatals after all this ?? Thanks a lot!

    Thanks all for the report and the updating status! We’re currently testing a fix for this – we’ll let you know about that as soon as the update and the fix are stable.

    We appreciate your patience!

    Hi there! Just following up on this as the team fixed this issue.
    VaultPress 1.9.10 is now out so you can update the plugin, and the issue should go away.

    Thanks for reporting it and thank you also for your patience while we tracked it down ::)

    If we can help with anything else, please let us know!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Fatal error in CRON’ is closed to new replies.