Cron won't run

Cron won't run

by Jason Martinez -
Number of replies: 11

When I try to run cron from the web interface or the CLI, I get the "moodle upgrade pending, cron execution suspended"

i have tried to put the site in and out of maintenance mode and run with no luck.  I also have purged all caches--no luck

I have not upgraded.  I only tried to install a plugin and it did not work and so I uninstalled it. (progress bar)

Both of the php.ini files (CLI and Apache2) have the serialized_precision = 17  in there correctly.

 

Any ideas out there?

 

Thanks

Jason

-It's the small things that make the difference

Average of ratings: -
In reply to Jason Martinez

Re: Cron won't run

by Guillermo Madero -

Hi Jason,

You don't mention anything about your setup. Anyway, please see:

https://tracker.moodle.org/browse/MDL-43314

In reply to Guillermo Madero

Re: Cron won't run

by Jason Martinez -

Sorry about that Guillermo.  My setup is:

moodle ver. 2.6.1 (Ububtu 12.04)

php5 ver. 5.3.10

apache2  ver. 2.2.22

MySql  ver. 5.5.34

I am using a theme called Saga ( I have tried changing to other themes and clearing theme caches as well)

I was able to run cron just fine from the web interface the past few months.  After trying to install that progress bar plugin update--updating the database--then un installing it--updating the database--then re installing the working progress bar plugin again--updating the database.  This is when I noticed moodle cron not running and displaying that message.

I have looked at that tracker and not found anything there that has worked.

I do have a dev site I test with (internal only)--so If you can point me to anything to try.

Thanks

Jason

-I'ts the small things that make the difference

 

In reply to Jason Martinez

Re: Cron won't run

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

What happens if you go to the Site administration > Notifications page?

Average of ratings: Useful (1)
In reply to Howard Miller

Re: Cron won't run

by Jason Martinez -

Howard,

If I go to Site Administration->Notifications

I get the page:

"No plugins require your attention now"

a "reload" link

and a box at the bottom saying "Upgrade Moodle database now"

 

Jason

-It's the small things that make the difference

In reply to Jason Martinez

Re: Cron won't run

by Bret Miller -
Picture of Particularly helpful Moodlers

Wouldn't "Upgrade Moodle database now" indicate that an upgrade is pending. You should probably click on the box and finish the upgrade...

In reply to Bret Miller

Re: Cron won't run

by Jason Martinez -

Thanks Brett.

When I try to "upgrade moodle database now"  I get:

!   Plugin "block/virtbkp" is defective or outdated, can not continue, sorry.

 

debug info:  Missing version.php file

Error code: detectedbrokenplugin

Stack trace:

-line 741 of /lib/upgradelib.php:plugin_defective_exception thrown

-line 397 of /lib/upgradelib.php:call to upgrade_plugins_blocks()

-line 1580 of /lib/upgradelib.php:call to upgrade_plugins()

-line 432 of /admin/index.php:call to upgrade_noncore()

        Continue

 

Thanks

Jason

-It's the small things that make the difference

In reply to Jason Martinez

Re: Cron won't run

by Christian Herman -

Delete the [moodle]/block/virtbkp directory, or at least remove it from the blocks directory if you don't want to delete it.

Average of ratings: Useful (3)
In reply to Christian Herman

Re: Cron won't run

by Jason Martinez -

Thanks Christian,

It looks like that worked. 

Jason

-I'ts the small things that make the difference

In reply to Jason Martinez

Re: Cron won't run

by Guillermo Madero -

Hi Jason,

According to the tracker, the problem has been fixed in that version, so you may have just found another bug. Maybe you would like to open an account and post at the tracker.

Regarding the problem, and given the install/uninstall issues, I would definitely restore a backup. If I were in the mood of trying to determine the cause, I would first make a database dump (if working with MySQL) and compare it with the one from the backup.