Having to Migrate Between Builds in Order to Edit/Create Nodes

Posted by Jo_Pa on February 3, 2012 at 4:57pm

Hello there!

We're currently running Aegir using Barracuda and then Octopus for our Aegir instances. We've been experiencing a regular issue when attempting to create or edit a Node: Once 'Save' is clicked, the page just refreshes back to the edit Node view, with no changes saved or new Node created. After a couple more attempts, a 500 server error comes up.

To resolve this we migrate between builds, the latest and next-to-latest, then back to the latest. We can go the whole day, though, with no problems. Come the next day and we have to migrate between builds again; it's become something of a morning ritual.

We're in active development right now, both with content and theming. This seems to be an issue with the site cache, specifically when it comes to administration. Any insight would be greatly appreciated, thank you.

Comments

This relates to the Cache

Posted by jamiet on February 3, 2012 at 6:10pm

This relates to the Cache Expiration module which is added to every platform and enabled by octopus scripts each morning. There are known issues with Drupal 7.10 and the expire module which causes this problem. There has been a patch to octopus scripts but I couldn't get it to fix the octopus instances (I suspect because there were no new platforms to install). Disable the purge and expire modules and uninstall them on your platforms. You will then need to login as root on your server and rm -rf the expire and purge directories in /data/all/xxx/o_contrib_seven/ directory where xxx is the revision number of the contrib folder that is being linked in your platforms (most likely the latest). There was some discussion somewhere on d.o but I cannot find it now.

HTH,

JamieT

A known bug fixed in HEAD:

Posted by omega8cc on February 3, 2012 at 7:36pm

A known bug fixed in HEAD: http://drupal.org/node/1416996

Thanks for the link - that

Posted by jamiet on February 3, 2012 at 9:08pm

Thanks for the link - that was the post I was thinking of. Out of interest this module was put into a stable release wasn't it? I keep my scripts downloading the stable releases - the fix is in head does that explain why I had to manually remove the modules?

TIA,

JamieT

It was in HEAD only. While

Posted by omega8cc on February 4, 2012 at 4:59am

It was in HEAD only. While stable includes extra logic for removing any stuff tested in HEAD at the end of the install/upgrade, it still downloaded Expire and Purge for D7 in the script C, but then runs script A again and it should remove them. It could fail to remove them only if you have used HEAD version for some upgrade in the meantime. For more details please use issue queue.

By the way, BOA-2.0.2 will

Posted by omega8cc on February 4, 2012 at 5:00am

By the way, BOA-2.0.2 will include now working support for Purge and Expire modules in all D7 platforms. It is already in HEAD.