Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I get the following error message during octopus o1 upgrade (up-stable) from BOA-2.0.5 to BOA-2.0.6:
Do you want to install some latest, ready to use platforms? [Y/n] n
Octopus [Tue Apr 2 22:45:05 BST 2013] ==> UPGRADE A: No new platforms added this time
Octopus [Tue Apr 2 22:45:07 BST 2013] ==> UPGRADE A: Cleaning up various dot files, please wait...
/opt/tmp/nginx-for-drupal/aegir/scripts/AegirSetupA.sh.txt: line 1168: cd: /data/all/004: No such file or directory
touch: cannot touch `/data/all/004/dot-files-ctrl-BOA-2.0.6': No such file or directory
Octopus [Tue Apr 2 22:45:12 BST 2013] ==> UPGRADE A: Adding symlink to the system clean_missing_modules
Octopus [Tue Apr 2 22:45:14 BST 2013] ==> UPGRADE A: Adding symlink to the system drush_ecl
ln: creating symbolic link `/home/o1.ftp/platforms/004/keys': No such file or directory
touch: cannot touch `/data/all/004/javascript_aggregator.out.txt': No such file or directory
Octopus [Tue Apr 2 22:45:16 BST 2013] ==> UPGRADE A: Preparing setupmail.txt
Comment | File | Size | Author |
---|---|---|---|
#12 | barracuda_1.log_.txt | 178.54 KB | aanjaneyam |
#12 | octopus_1.log_.txt | 190.47 KB | aanjaneyam |
#8 | octopus.txt | 55.77 KB | aanjaneyam |
Comments
Comment #1
omega8cc CreditAttribution: omega8cc commentedComment #2
aanjaneyam CreditAttribution: aanjaneyam commentedThe error doesn't seem or appear to affect the operation of BOA. But created the issue as there was no such warning/error in earlier upgrades:
The warning lies in the following lines (included above)
/opt/tmp/nginx-for-drupal/aegir/scripts/AegirSetupA.sh.txt: line 1168: cd: /data/all/004: No such file or directory
touch: cannot touch `/data/all/004/dot-files-ctrl-BOA-2.0.6': No such file or directory
ln: creating symbolic link `/home/o1.ftp/platforms/004/keys': No such file or directory
touch: cannot touch `/data/all/004/javascript_aggregator.out.txt': No such file or directory
Comment #3
omega8cc CreditAttribution: omega8cc commentedBy "maintainer needs more info" I mean following (always) the guidelines.
You shouldn't see such errors, because it is a sign of something broken, like missing directories or out-of-sync settings etc.
Comment #4
aanjaneyam CreditAttribution: aanjaneyam commentedComment #5
aanjaneyam CreditAttribution: aanjaneyam commentedI upgraded octopus today using BOA2.0.7 and the following errors appeared while upgrading (I have already provided the requested info above):
Comment #6
omega8cc CreditAttribution: omega8cc commentedPlease:
1. Enable debugging, as explained in the guidelines.
2. Attach *complete* log, not just a snippet.
3. Provide a result of commands listed below:
ls -l /data/all/
ls -l /data/all/*/ | grep o_contrib
ls -l /data/disk/o1/distro/
ls -l /home/o1.ftp/platforms/
ls -l /data/disk/o1/platforms/ | grep pressflow
Comment #7
aanjaneyam CreditAttribution: aanjaneyam commentedWell after enabling _DEBUG_MODE=YES and forcing the the aegir and platform upgrade the content of cat /data/disk/o1/log/octopus_log.txt remains the same. Also the I was unable to install Panopoly-rc4a in the first attempt during upgrade- it complained about panopoly related stuff not found in /data/all/004 etc. During second attempt -force upgrade with _DEBUG_MODE=YES- it did not even ask for panapoly install, see below:
The verification task log for panopoly-rc4a is:
Apart from above I was not able to detect any error during the forced upgrade (with _DEBUG_MODE=YES
The output of your commands in #6 are
Since there is nothing in
/data/disk/o1/log/octopus_log.txt
/var/aegir/config/includes/barracuda_log.txt
Is there some where else I can look for logs.
Comment #8
aanjaneyam CreditAttribution: aanjaneyam commentedI am attaching the visible part of the terminal output during the last (forced and DEBUG_MODE=YES) upgrade. It is not complete but it is about 90% of it.
Comment #9
omega8cc CreditAttribution: omega8cc commentedThanks, but, well, if you have said
n
to all questions, no new structure has been created there, hence these weird errors, because it is not intended to be "used" that way (by skipping all platforms). Why do you fire up adding platforms at all if you skip them all? You should just set_HM_ONLY=YES
in the/root/.o1.octopus.cnf
and never see these questions. Or you are giving us confusing logs instead of those with errors.As for the Panopoly issue - if you see something like
provision-save '@' --backend
then something is already terribly wrong with this Aegir instance and I have no idea how to help further without checking the system personally, but we don't have anyone available for such investigation in the next few days.Comment #10
omega8cc CreditAttribution: omega8cc commentedA quick hint:
1. Delete
/data/disk/o1/distro/004/panopoly-7.x-1.0-rc4-7.22.1
directory **and** corresponding failed node in Aegir.2. Delete
/data/all/004/panopoly-7.x-1.0-rc4-7.21.2
directory (if exists)3. Run upgrade again.
Comment #11
omega8cc CreditAttribution: omega8cc commentedNote that Panopoly is build from makefile and if Drupal.org is terribly slow or crashes as it did today, the build will fail.
Comment #12
aanjaneyam CreditAttribution: aanjaneyam commentedSince the installation was on a virtualbox vm (as was testing upgrade) I restored the the VM (using snapshot) to the pre-BOA2.0.6 (state) and ran the upgrade again. This time I have captured the entire barracuda and octopus intall terminal messages (with _DEBUG_MODE=YES). In octopus_.log.txt you can see that it is only panopoly-rc4a distro which fails to install (and will subsequently give verify errors -pertaining to @ provision-verify). There may be other errors in the attached files. You can see that in above posts I have mentioned errors regarding /data/disk/all/004 directory.
I think I did nothing else on this aegir instance except experimenting with building custom panopoly platform from git, adding modules to it and then trying to install sites on it. Installing customisted site with new modules was always a faliure. I think panopoly is a very picky/choosy/sensitive distro which is either not suitable for drush 4 (in vanilla state downloaded directly and not patched) or it doesn't like customisation without involving extensive developer level patching.
Complete files attached.
Comment #13
omega8cc CreditAttribution: omega8cc commentedWe have tested this many times on various systems, on upgrades and clean installs, even on major upgrade from some old Lenny VM image with almost two year old install and it just works, so it seems like something specific to your system, because we couldn't reproduce this. Please try on a clean install, since maybe there are some mods you did and are not aware of etc.
Note, that this has nothing to do with Panopoly being 'fragile' itself, as installing the platform just works, and BOA of course uses Drush 5 for this task.
Comment #14
aanjaneyam CreditAttribution: aanjaneyam commentedThe error mentioned in #1 above is appearing again in a rackspace live server upon upgrade to BOA2.0.8. This time I have not installed any platforms. If I would have tried to install any new platform it would have given panopoly error. Please not that the server used in this post (#14) is a different server than used in #12 above but is same as #1 above. Both complain of platform files in 004 (confusing)
Since this is a live server some hints on fixing this would be very welcome. Can I do something similar to #10 above like deleting 004 files/directory and upgrading again.
Just to clarify that server in #1 (the live server) is different than server in #12 (virtualbox vm) an posts other than #1. After the error mention in #1 occurred ,I did not try platform upgrade on live server and went on to do the testing in a similar virtualbox local vm (which also gave similar errors). I feared spoiling my live server to so tested it in VM. Both these servers were upgraded from BOA-2.0.5. The error in #1 or #12 only occurs in upgrades from BOA-2.0.5. I freshly installed a server from BOA-2.0.6 and the upgraded to 2.0.7 and then to 2.0.8 and there were no errors.