error in file - failure updating octopus up-stable both [#2125937]

The links in the file /data/disk/o1/aegir/distro/002/6.x seem to be no longer valid:

They need pub/drupal/ added to the download and url links and http:// changed to ftp://
as in: "ftp://ftp.drupal.org/pub/drupal/files/projects"

for them to be valid, don't they?

Additionally I am getting many "unable to determine project type" and "non-existant project type" error messages re this same file.

Here's (uploaded) my modified version of this file with the links replaced as above, but there's still many errors on attempted upgrades: mostly with other modules, and the only change on the userprotect module my modified version of the file 6.x made was to remove the first error (unable to determine project type). The second error non-existent project type persists.

Furthermore
The upgrade process fails trying to create an 003 distro

002 is currently being used.

This was just after performing a barracuda up-stable which appeared to work fine.

I attach the pertinent terminal screen output.

There's nothing unusual in my slightly modified my.cnf and Php.ini files - just adding a little ram here and there.

***Note: after successfully running a platform only upgrade, an aegir upgrade still failed with the attached Part1.txt error log.

I am running Wheezy 7.2 after latest barracuda up-stable

Regards,

Comment	File	Size	Author
#4	Part 1.txt	47.98 KB	Anonymous (not verified)
#1	6.x.txt	8.04 KB	Anonymous (not verified)
	fast1.octopus.txt	1006 bytes	Anonymous (not verified)
	barracuda.txt	1.58 KB	Anonymous (not verified)
	terminal-copy-nov-2-1330.txt	18.08 KB	Anonymous (not verified)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Anonymous (not verified) CreditAttribution: Anonymous commented 2 November 2013 at 14:05

Issue summary:

View changes

File	Size
6.x.txt	8.04 KB

Comment #2

Anonymous (not verified) CreditAttribution: Anonymous commented 2 November 2013 at 14:30

It's just the aegir upgrade that isn't working, of course, I successfully did a platform upgrade on 003 just now.

Comment #3

omega8cc CreditAttribution: omega8cc commented 2 November 2013 at 14:37

It also breaks drush makefiles in general. That is why we are moving away from dependency on drupal.org in general. Previous and latest fixes for these issues have been committed in HEAD, but are available at the moment only when you use _FORCE_GIT_MIRROR="gitorious". It should go into stable release this weekend.

Comment #4

Anonymous (not verified) CreditAttribution: Anonymous commented 2 November 2013 at 14:40

Issue summary:

View changes

File	Size
Part 1.txt	47.98 KB

Comment #5

omega8cc CreditAttribution: omega8cc commented 2 November 2013 at 14:44

These URLs emitted by meta files on d.o are obviously wrong and are a total mess, by the way:

$ curl -I http://ftp.drupal.org/pub/drupal/files/projects/userprotect-6.x-1.5.tar.gz
HTTP/1.1 404 Not Found
Date: Sat, 02 Nov 2013 14:40:43 GMT
Server: Apache
Content-Type: text/html; charset=iso-8859-1

It should be, as before:

$ curl -I http://ftp.drupal.org/files/projects/userprotect-6.x-1.5.tar.gz
HTTP/1.1 200 OK
Date: Sat, 02 Nov 2013 14:41:52 GMT
Server: Apache
Last-Modified: Thu, 06 Jan 2011 18:43:02 GMT
ETag: "e9265-6371-49931df153980"
Accept-Ranges: bytes
Content-Length: 25457
Content-Type: application/x-gzip

Comment #6

omega8cc CreditAttribution: omega8cc commented 2 November 2013 at 14:47

Well, if you are using _USE_MEMCACHED=YES you are using legacy and no longer supported (for a long time) feature. I would suggest to disable it, since BOA doesn't use memcache for anything.

Comment #7

timlie CreditAttribution: timlie commented 3 November 2013 at 11:31

I performed an upgrade with barracuda up-stable followed by octopus up-stable o1

I got following errors and after this my websites are "offline":

Octopus [Sun Nov 3 11:16:28 UTC 2013] ==> UPGRADE B: FATAL ERROR: Required file /data/disk/01/aegir/distro/003/sites/01.myserver.com/settings.php does not exist
Octopus [Sun Nov 3 11:16:28 UTC 2013] ==> UPGRADE B: FATAL ERROR: Aborting AegirSetupB installer NOW!
Octopus [Sun Nov 3 11:16:28 UTC 2013] ==> UPGRADE A: FATAL ERROR: AegirSetupB installer failed
Octopus [Sun Nov 3 11:16:28 UTC 2013] ==> UPGRADE A: FATAL ERROR: Aborting AegirSetupA installer NOW!
Octopus [Sun Nov 3 11:16:28 UTC 2013] ==> FATAL ERROR: AegirSetupA installer failed
Octopus [Sun Nov 3 11:16:28 UTC 2013] ==> FATAL ERROR: Aborting Octopus installer NOW!

How can I solve this?