Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After updating Barracuda successfully, get the following error when upgrading from BOA-2.0.5 using:
octopus up-stable all
ctopus [Tue Apr 2 13:19:30 UTC 2013] ==> UPGRADE B: Running hostmaster-migrate, please wait...
Octopus [Tue Apr 2 13:20:59 UTC 2013] ==> UPGRADE B: Hostmaster STATUS: upgrade completed
Octopus [Tue Apr 2 13:20:59 UTC 2013] ==> UPGRADE B: Simple check if Aegir upgrade is successful Octopus [Tue Apr 2 13:21:01 UTC 2013] ==> UPGRADE B: FATAL ERROR: Required file /data/disk/o1/aegir/distro/003/sites/o1.server.sizeshape.com/settings.php does not exist
Octopus [Tue Apr 2 13:21:01 UTC 2013] ==> UPGRADE B: FATAL ERROR: Aborting AegirSetupB installer NOW!
Octopus [Tue Apr 2 13:21:01 UTC 2013] ==> UPGRADE A: FATAL ERROR: AegirSetupB installer failed
Octopus [Tue Apr 2 13:21:01 UTC 2013] ==> UPGRADE A: FATAL ERROR: Aborting AegirSetupA installer NOW!
Octopus [Tue Apr 2 13:21:01 UTC 2013] ==> FATAL ERROR: AegirSetupA installer failed
Octopus [Tue Apr 2 13:21:01 UTC 2013] ==> FATAL ERROR: Aborting Octopus installer NOW!
Comment | File | Size | Author |
---|---|---|---|
#9 | patch_commit_4e87f87ea3ff.patch | 785 bytes | omega8cc |
#2 | Terminal log | 140.04 KB | D.Holmlund |
Comments
Comment #1
omega8cc CreditAttribution: omega8cc commentedPlease follow guidelines.
Comment #2
D.Holmlund CreditAttribution: D.Holmlund commentedI am having the exact same problem with
UPGRADE B: FATAL ERROR: Required file /data/disk/fub11/aegir/distro/004/sites/o1.XXXXXXX/settings.php does not exist
when runningoctopus up-stable
after upgrading to BOA-2.0.6 stable. I have tried removing incomplete 00x-directories and clearing/opt/tmp/
without any luck.The logs are also giving me the following errors (see the attached terminal log for more info):
UPDATE {hosting_ip_addresses} SET id=19 WHERE nid=4 AND ip_address='127.0.0.1' [40.11 sec, 18.01 MB]
UPDATE {hosting_ip_addresses} SET id=20 WHERE nid=4 AND ip_address='127.0.0.1' [40.11 sec, 18.01 MB]
Drush was not able to start (bootstrap) the Drupal database.
It has affected two separate servers after upgrading from 2.0.5 to 2.0.6 so it does not seem to be just a local problem.
Comment #3
omega8cc CreditAttribution: omega8cc commented@D.Holmlund - Thanks. The problem is shown here:
Basically,
hosting_server_update_6200
is trying to upgrade thehosting_ip_addresses
table, but it looks like for some reason you have had there duplicate entries for127.0.0.1
already, so it fails because there are new keys added, but not sure.Note that it looks like a duplicate of:
#1930670: Duplicate entry 0 for key PRIMARY in hosting_ip_addresses when installing / upgrading
#1932616: IPs deleted from hosting_ip_addresses table on server verify
At least the errors are the same, but with our version of
hosting_server_update_6200
, well tested on many servers already, it shouldn't happen.Could you post a result of this command?
Comment #4
omega8cc CreditAttribution: omega8cc commentedAlso:
su -s /bin/bash - aegir -c "drush @hostmaster sqlq \"SELECT * FROM hosting_ip_addresses\""
Comment #5
omega8cc CreditAttribution: omega8cc commentedAt any rate, it is critical.
Comment #6
D.Holmlund CreditAttribution: D.Holmlund commentedHere goes (1.1.1.1 is anonymized):
su -s /bin/bash - fub1 -c "drush @hostmaster sqlq \"SELECT * FROM hosting_ip_addresses\""
su -s /bin/bash - aegir -c "drush @hostmaster sqlq \"SELECT * FROM hosting_ip_addresses\""
Comment #7
omega8cc CreditAttribution: omega8cc commentedRight, so you have duplicate entries in both Master and Satellite instances already and this is what breaks the upgrade. I have never seen anything like that on any server we manage.
However, it should also break the Master instance (barracuda) upgrade, but it worked (?)
I guess we need to run some de-duplicate on this table as a part of the
hosting_server_update_6200
upgrade to avoid this edge case.Comment #8
omega8cc CreditAttribution: omega8cc commentedThis simple patch should do the trick, I guess.
I'm moving this to the correct upstream queue, btw.
Comment #9
omega8cc CreditAttribution: omega8cc commentedUploading the patch for review again.
Comment #10
D.Holmlund CreditAttribution: D.Holmlund commentedPatch works like a charm, thank you!
Comment #11
omega8cc CreditAttribution: omega8cc commentedThat patch alone is not enough. It "works" in BOA now only because we have added some hot-fix to avoid this issue, but the correct and complete patch still needs to be submitted for review.
Comment #12
omega8cc CreditAttribution: omega8cc commentedI'm closing this as an effective duplicate of:
#1930670: Duplicate entry 0 for key PRIMARY in hosting_ip_addresses when installing / upgrading
#1932616: IPs deleted from hosting_ip_addresses table on server verify
For reference: http://drupal.org/node/1930670#comment-7249422
Comment #13
linksync CreditAttribution: linksync commentedWorked for me also.
Sever has default setup: Debian squeeze and BOA-2.0.4, which was upgraded to BOA-2.0.5. No additional packages or customisation on the server.
Comment #14
omega8cc CreditAttribution: omega8cc commentedNote that BOA-2.0.6 now includes this as a tested and working hotfix.