Annoying real world migration between platforms situation [#1917324]

Hi,

Often have this kind of situation:

Have Octopus platform with lets say drupal 7.14 with some live sites on it. Lets assume, that not much ~5. Now I create a new, custom platform with the newest possible Drupal core (7.19), prepare it for Aegir, copy all the modules form old platform and etc.

When I clone/migrate to it a site (-s) - everything works just fine.

But:

When I prepare shiny new platform and also update outdated module files - this task 90% of the time gives WSOD. Of course if there is just 1 site, I can do it manually: migrate site to new platform, overwrite all the modules, run update.php - it gives no errors, lets assume, that there are just minor module updates, no database schema change. Usually everything works fine after this action

Question:

What to do, if there are more, much more than 1 site and want to migrate to another platform WITH all the updated modules. Is it possible at all? With Drush? How to avoid WSOD?

p.s. Writing this in Octopus issue, as there are too many different speedbooster and similar stuff which specific configuration can cause WSOD itself. If it is 100% aegir - I will post it in aegir queue.

Comments

Comment #1

omega8cc CreditAttribution: omega8cc commented 18 February 2013 at 19:49

Status:

Active

» Postponed (maintainer needs more info)

I don't see anything BOA specific here, so far, because you don't provide any details, like failed task log, so it i impossible to determine if this is because of, say, Redis, or maybe APC or maybe just lack of proper upgrade path in some contrib modules, which triggers Drush panic, thus broken and reverted tasks in Aegir. Please provide more details, so we could try to determine where this request belongs. Thanks.

Comment #2

PlayfulWolf CreditAttribution: PlayfulWolf commented 18 February 2013 at 20:06

BOA 2.0.5 with more or less default options, there is nothing to post about logs - no errors, aegir shows everything is just fine, I can shorten the situation:
1. Create new platform with 10+ updated modules
2. Migrate/clone site to the new platform ("safe" situation with clone, then migrate, or migrate to new platform at the same time - does not matter)

Most likely the site will get WSOD even if the module updates are minor, no db scheme changed.

If I migrate/clone site to new platform with old modules, then overwrite with new module files and run update.php - everything is just fine. It is not a problem, if there is 1 site, but if there are 5+ sites everything is too much time consuming.

My question: does it look like it is Aegir or BOA related? I do not have separate linux server with similar config to test Aegir with more classic config (apache, mod-php). I am not looking for the exact solution at this point - my knowledge in Aegir or BOA is not that deep, for the beginning to find the approximate cause of the problem is ok.

Comment #3

omega8cc CreditAttribution: omega8cc commented 18 February 2013 at 20:12

What is displayed as the reason of the WSOD when you access the migrated site via dev/devel alias? Does it go away when you append ?noredis=1 at the end of URL?, etc. It is explained in detail at: http://omega8.cc/how-to-debug-wsod-and-other-errors-238