Posted by aaronbauman on August 12, 2010 at 3:14pm
3 followers
Jump to:
| Project: | Hostmaster (Aegir) |
| Version: | 6.x-0.4-alpha3 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I'm up to the point of migrating, and this is the command I'm running:
$ drush hostmaster-migrate MYSITE.EXAMPLE.COM /var/aegir/hostmaster-0.4-alpha10 --debugAfter I solved #880660: Error during upgrade from 0.4-alpha9 to 0.4-alpha10, I ran into another issue:
The directory /var/aegir/hostmaster-0.4-alpha10 does not contain a valid Drupal installation [11.18 sec, 5.01 MB] [error]That seemed straightforward - I downloaded the latest Drupal to the specified directory.
Now, I have a Drupal install at the specified directory and the migrate script runs OK.
However, my crontab entry is still empty.
Did I do something terribly wrong?
I don't understand why I had to download Drupal manually.
Is there a quick fix to recreate the crontab, or do i need to re-migrate?
Comments
#1
Also: the alpha10 Drupal site that was "installed" via migrate returns a 404 for every page, including the home page.
#2
Re: #1
This was because the hostmaster profile was never downloaded, migrated, nor installed.
Therefore the site root, hosting/sites, was indeed 404'd.
Further, all of the hosting modules were disabled since they were unavailable.
JQuery Update, JQuery UI and Modal Frame were neither downloaded, migrated, nor installed.
#3
This was my fault it seems.
I have a new working alpha 11, but the workaround at the moment is :
http://groups.drupal.org/node/86354#comment-270489
that's what the migrate command is meant to be doing. The migrate command in alpha 10 didn't differentiate between pre-alpha 9 and post alpha 9 sites. Meaning it tried to do the intensive bootstrap process for the upgrade all over again.
#4
this is now fixed in head.
#5
I made an alpha 11 release that contains this fix : http://is.gd/eeXP5
#6
For the site that may already have been messed up, i need you to do the following.
1) find the backup used during the migrate. it will be in the /var/aegir/backups directory. do not continue on if you arent sure you have the right one
2) Find the alias name of the old platform. Grep in your ~/.drush directory. do not continue if you arent sure you have the right one
3) shell command:
crontab -r# just stop the dispatcher from running4) shell command:
drush @hostmaster provision-delete# this will delete the incorrectly migrated site5) shell command:
drush provision-save @hostmaster --platform='@platform_oldplatform'# set the platform back to the one found in step 2.6) shell command:
drush @hostmaster provision-deploy /var/aegir/mybackupfile.tar.gz# restore the backup from step 1The end result should be that you will have your system back to what it was before you hit the hostmaster-migrate command. IE: running alpha 9 on the alpha 9 platform.
Next, you should download the new alpha 11 release's provision and run the migrate command contained in it.
#7
adrian, thanks for the quick response and follow up support on this.
I followed the steps above with one change:
- in step 4: substituting "@server_master" -- the alias from step 2 -- for "@hostmaster"
I am now on alpha 11 - woot!
#8
Automatically closed -- issue fixed for 2 weeks with no activity.