When I set my cron queue under hosting in Aegir to 12 hours, the next day it is always reset to 88 weeks. It is really a mystery to me why this is happening. I also tried to run Elysia cron but cron runs never happened. Probably the same reason. Any ideas why this is happening and how I can solve it?

Thanks!

Screenshot cron queue

CommentFileSizeAuthor
#2 Screen Shot 2013-03-08 at 7.18.27 PM.png33.36 KBDonaldd
#1 ocean-hm.jpg102.84 KBomega8cc
Screen Shot 2013-03-07 at 5.55.56 PM.png47.82 KBDonaldd
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

omega8cc’s picture

omega8cc CreditAttribution: omega8cc commented
Status: Active » Postponed (maintainer needs more info)
FileSize
ocean-hm.jpg102.84 KB

1. We force this only on every Satellite Octopus Instance, to prevent double crons when advanced cron is enabled.
2. Your screenshot doesn't look like Octopus instance.
3. Default Master Instance settings look like below:

o2

Before we will ask more questions and answer any questions, please follow bug/support submission guidelines.

Donaldd’s picture

Donaldd CreditAttribution: Donaldd commented
FileSize
Screen Shot 2013-03-08 at 7.18.27 PM.png33.36 KB

My bad, found out that it was indeed the ocopus instance where I changed the cron settings. I checked my main barracuda instance and realized that the cron queue wasn't even enabled, so did that and now it is running there. However I still am not seeing the cron running on my websites. Screen Shot 2013-03-08 at 7.18.27 PM.png
(I left it set to 88 weeks on my octopus instance)

Thank you!

omega8cc’s picture

omega8cc CreditAttribution: omega8cc commented
Project: Barracuda » Octopus
Component: Aegir Master Instance » Aegir Hostmaster
Status: Postponed (maintainer needs more info) » Closed (works as designed)

You have disabled advanced cron module in your Octopus Instance, while it is required, please don't modify the setup that way or it will stop processing the cron for sites.

Donaldd’s picture

Donaldd CreditAttribution: Donaldd commented

Thanks for your quick responses. Apparently the only thing I needed to do was update my Octopus instance that solved it.
I hadn't properly updated it in a very long time and that was probably the cause of the problem.

But thank you for your help and this incredible contribution!