Ticket #788 (closed maintenance: fixed)

Opened 2 years ago

Last modified 2 years ago

New BOA-2.3.3 Stable Edition available

Reported by: chris Owned by: chris
Priority: major Milestone: Maintenance
Component: Live server Keywords:
Cc: ed, ben, sam, paul, annesley Estimated Number of Hours: 0.0
Add Hours to Ticket: 0 Billable?: yes
Total Hours: 0.53

Description

Changelog: http://bit.ly/boa-changes

### Stable BOA-2.3.1 Release - Full Edition
### Date: Sun Sep 14 15:53:25 SGT 2014
### Includes Aegir 2.1 with improvements
### Latest hotfix added on: Mon Sep 15 05:30:37 SGT 2014

# Release Notes:

  This major BOA Edition introduces many new features, changes and fixes.

  You should carefully read about some caveats further below **before** running
  this major upgrade on your system. Please secure a fresh system backup first.

  If you haven't run full barracuda+octopus upgrade to latest BOA Stable
  Edition yet, don't use any partial/system upgrade modes.

  Once new BOA Stable is released, you must run *full* upgrades with commands:

  $ cd;wget -q -U iCab http://files.aegir.cc/BOA.sh.txt;bash BOA.sh.txt
  $ barracuda up-stable
  $ octopus up-stable all both

  @=> Key new features:

  * BOA-2.3.1 comes with shiny Aegir 2.1 stable version, finally!
  * Support for Drupal sites in subdirectories is enabled by default
  * Solr 4 cores can be added/updated/deleted via site level INI settings
  * Super-easy to use New Relic support with per Octopus license key
  * Ability to add new Octopus instances with new, simple command syntax

  @=> Aegir control panel new features:

  * The list of sites is searchable by name or installation profile
  * You can schedule tasks against filtered sites in batches
  * Scheduling tasks in batches is available also on the platform view
  * Scheduling tasks in batches is available also on the profile view
  * Each site has its own tasks list available from the site view tab
  * You can schedule tasks also against platforms in batches
  * You can safely apply db updates via 'Run db updates' task on any site
  * It is now possible to choose any existing alias or the main site name
    as a redirect target, but without the need to rename the site --
    it will just re-verify the site and create new vhost automatically

  @=> Other important changes:

  * Support for PHP 5.2 has been officially deprecated
  * The www53 PHP-FPM pool has been switched from port to default socket mode
  * All existing vhosts must use wildcard in the Nginx 'listen' directive
  * Legacy mode for Install and Upgrade moves to 2.2.x branch
  * DB credentials are no longer in settings.php, only in drushrc.php
  * Latest Drush 6 version is used in the Aegir backend by default

  But what if you are not ready for this major upgrade and you would like
  to have more time for testing, but still be able to run system upgrades,
  thus effectively still using previous version 2.2.9 ?

#-### Legacy mode for Install and Upgrade moves to 2.2.x branch

  From now on, the 'legacy' install and upgrade mode available in all meta-
  installers will utilize branch 2.2.x instead of deprecated 2.1.x series.

  This means that starting with meta installers updated to use BOA-2.3.1
  version you can use commands like shown below to update Barracuda, Octopus
  and also to install more Octopus instances, while still using version 2.2.9:

  $ boa in-legacy public server.mydomain.org my@email o1
  $ barracuda up-legacy system
  $ octopus up-legacy o1
  $ boa in-legacy public server.mydomain.org my@email o2 mini
  etc.

  Remember to update your meta-installers first!

  $ cd;wget -q -U iCab http://files.aegir.cc/BOA.sh.txt;bash BOA.sh.txt

  Note also that if you will upgrade to current 'stable', it is not possible
  to downgrade back to the 'old stable' with 'legacy' mode, so please proceed
  with care!

  Remember also that current legacy version will not receive any further
  updates, even for security issues (besides those provided as packages by
  your OS vendor - Debian or Ubuntu, which will still work), because it is
  already different enough from current 2.3.1 stable, so we can't reliably
  maintain both with working upgrade path.

#-### Caveats: This upgrade will force wildcard in the Nginx 'listen' directive

  If you have old enough BOA system which still uses legacy IP mode and not
  a wildcard in the Nginx 'listen' directive, which is both Aegir and BOA
  standard for a long time already, this upgrade will fix the problem and
  update directives only in vhosts known and controlled by BOA.

  If you have any other vhosts, located in standard or non-standard Nginx/BOA
  directories for vhosts, you have to update them manually after upgrade to
  BOA-2.3.0 or newer, or they will take over all other vhosts on the system
  and cause redirects to /install.php which results with Nginx error 403 or 404,
  depending on the prior configuration.

  It will happen because IP based 'listen' directive in Nginx has higher
  priority, and will mess things horribly if there are vhosts using wildcard
  and some using the main system IP address.

  What and how to replace? Here are commands you need to run as root:

    $ sed -i "s/.*listen.*:80;/  listen  \*:80;/g" /path/to/vhost.file
    $ sed -i "s/.*listen.*:443/  listen  \*:443/g" /path/to/vhost.file
    $ service nginx reload

  Note: this **doesn't** affect special vhosts for SSL enabled sites, if used,
  because they are designed to use IP based 'listen' directives to provide
  separation between SSL enabled IPs and their associated certificates,
  while their associated 'upstream' block may even point to either local or
  remote IP address, so there is no wildcard to use in this case, and it will
  not conflict with all other vhosts managed by Aegir, because all SSL enabled
  vhosts listen on other IP addresses than the main system IP, which is
  by default used by all vhosts with wildcard in the 'listen' directive.

  The problem may happen only when you have vhosts using wildcard and also
  some vhosts using **main** system IP address in the 'listen' directive,
  which may happen also unintentionally during upgrade to BOA-2.3.0 or never,
  if there are either vhosts BOA doesn't control, or there are ghost vhosts
  not yet purged if you didn't upgrade to BOA-2.2.9 before, or there are
  some disabled sites, so their vhosts will not be re-created by Aegir
  during this major upgrade (because only active sites can be re-verified).

  While BOA will fix also any such ghost vhosts anyway, it will not be able
  to detect and fix vhosts outside of the standard directories managed by Aegir.

#-### Ability to add new Octopus instances with new, simple command syntax

  It is now possible to add stable Octopus instances w/o forcing Barracuda
  upgrade, plus optionally with no platforms added by default -- usage:

    $ boa {in-octopus} {email} {o2} {mini|max|none}

#-### The www53 PHP-FPM pool has been switched from port to default socket mode.

  Note that we are breaking backward compatibility here, so it will cause
  downtime on upgrade from any too old BOA version, until you will upgrade also
  Octopus instance(s) and update any other non-standard vhosts or includes
  still using legacy port mode for 'fastcgi_pass' Nginx directive.

  If you have 'fastcgi_pass 127.0.0.1:9090;' in any custom vhost or Nginx
  include file on the Octopus instance, you should replace it with:

    fastcgi_pass unix:/var/run/o1.fpm.socket;

  where 'o1' is your corresponding Octopus system username.

  Note that if you have custom vhosts or includes in the Aegir Master Instance,
  you should instead replace 'fastcgi_pass 127.0.0.1:9090;' with:

    fastcgi_pass unix:/var/run/www53.fpm.socket;

  where '53' is related to PHP version defined via _PHP_FPM_VERSION in your
  /root/.barracuda.cnf file. Note that while variable has a dot, the socket
  name doesn't.

#-### Support for PHP 5.2 has been officially deprecated

  While Barracuda 2.3.1 can continue to run and even upgrade if needed also
  the very old PHP 5.2 version, only Octopus instances running at least PHP 5.3
  or newer in both FPM and CLI mode can be upgraded to Octopus 2.3.1 Edition.

  If you are still using PHP 5.2 in your Octopus instance, you will not
  receive Aegir nor Drupal Platforms upgrade, but the Barracuda part of your
  system will receive upgrade to 2.3.1 anyway, so it will be ready to support
  your outdated Octopus instance upgrade as soon as you will switch it to
  modern and secure PHP version -- which is easy!

  Let's quote the original how-to for reference:

#-### Support for PHP FPM/CLI version safe switch per Octopus instance

  This allows to easily switch PHP version by the instance owner w/o system
  admin (root) help. All you need to do is to create ~/static/control/fpm.info
  and ~/static/control/cli.info file with a single line telling the system
  which available PHP version should be used (if installed): 5.5 or 5.4 or 5.3

  Only one of them can be set, but you can use separate versions for web access
  (fpm.info) and the Aegir backend (cli.info). The system will switch versions
  defined via these control files in 5 minutes or less. We use external control
  files and not any option in the Aegir interface to make sure you will never
  lock yourself by switching to version which may cause unexpected problems.

#-### Support for New Relic monitoring with per Octopus instance license key

  This new feature will disable global New Relic monitoring by deactivating
  server-level license key, so it can safely auto-enable or auto-disable it
  every 5 minutes, but per Octopus instance -- for all sites hosted on
  the given instance -- when a valid license key is present in the special
  new ~/static/control/newrelic.info control file.

  Please note that valid license key is a 40-character hexadecimal string
  that New Relic provides when you sign up for an account.

  To disable New Relic monitoring for the Octopus instance, simply delete
  its ~/static/control/newrelic.info control file and wait a few minutes.

  Please note that on a self-hosted BOA you still need to add your valid
  license key as _NEWRELIC_KEY in the /root/.barracuda.cnf file and run
  system upgrade with at least 'barracuda up-stable' first. This step is
  not required on Omega8.cc hosted service, where New Relic agent is already
  pre-installed for you.

#-### Solr 4 cores can be added/updated/deleted via site level INI settings

;;
;;  This option allows to activate Solr 4 core configuration for the site.
;;
;;  Only Solr 4 powered by Jetty server is available. Supported integration
;;  modules are limited to latest versions of either search_api_solr (D7 only)
;;  or apachesolr (will use Drupal core specific version automatically).
;;
;;  Currently used versions are listed below:
;;
;;    http://ftp.drupal.org/files/projects/search_api_solr-7.x-1.6.tar.gz
;;    http://ftp.drupal.org/files/projects/apachesolr-7.x-1.7.tar.gz
;;    http://ftp.drupal.org/files/projects/apachesolr-6.x-3.0-rc2.tar.gz
;;
;;  Note that you still need to add preferred integration module along with
;;  any its dependencies in your codebase since this feature doesn't modify
;;  your platform or site - it only creates Solr core with configuration
;;  files provided by integration module: schema.xml and solrconfig.xml
;;
;;  This setting affects only the running daily maintenance system behaviour,
;;  so you need to wait until next morning to be able to use new Solr 4 core.
;;
;;  Once the Solr core is ready to use, you will find a special file in your
;;  site directory: sites/foo.com/solr.php with details on how to access
;;  your new Solr core with correct credentials.
;;
;;  The site with enabled Solr core can be safely migrated between platforms,
;;  integration module can be moved within your codebase and even upgraded,
;;  as long as it is using compatible schema.xml and solrconfig.xml files.
;;
;;  Supported values for the solr_integration_module variable:
;;
;;    apachesolr
;;    search_api_solr
;;
;;  To delete existing Solr core simply comment out this line.
;;  The system will cleanly delete existing Solr core next morning.
;;
;solr_integration_module = NO

;;
;;  This option allows to auto-update your Solr 4 core configuration files:
;;
;;    schema.xml
;;    solrconfig.xml
;;
;;  If there is new release for either apachesolr or search_api_solr, your
;;  Solr core will not be automatically upgraded to use newer schema.xml and
;;  solrconfig.xml, unless allowed by switching solr_update_config to YES.
;;
;;  This option will be ignored if you will set solr_custom_config to YES.
;;
;solr_update_config = NO

;;
;;  This option allows to protect custom Solr 4 core configuration files:
;;
;;    schema.xml
;;    solrconfig.xml
;;
;;  To use customized version of either schema.xml or solrconfig.xml, you need
;;  to switch solr_custom_config to YES below and if you are using hosted
;;  Aegir service, submit a support ticket to get these files updated with
;;  your custom versions. On self-hosted BOA simply update these files directly.
;;
;;  Please remember to use Solr 4 compatible config files.
;;
;solr_custom_config = NO


# Updated Octopus platforms:

  aGov 1.4 --------------------- https://drupal.org/project/agov
  Guardr 1.12 ------------------ https://drupal.org/project/guardr
  Open Academy 1.1 ------------- https://drupal.org/project/openacademy
  Restaurant 1.0-b9 ------------ https://drupal.org/project/restaurant
  Ubercart 3.7 ----------------- https://drupal.org/project/ubercart

# New features and enhancements in this release:

  * Ability to add new Octopus instances with new, simple command syntax
  * Add default aggressive php-fpm monitoring + /root/.no.fpm.cpu.limit.cnf
  * Allow to define always disabled modules via _MODULES_FORCE variable.
  * Better wait limits on connection testing for slow network / long distance.
  * Issue #1927522 - Add support for easy Solr cores self-management.
  * Issue #362 - Add imageapi_optimize binaries via IMG in _XTRAS_LIST
  * Issue #376 - Add New Relic support with per Octopus instance license key.
  * Make firewall management faster with randomized schedule.
  * Procs monitor runs every 3 seconds.
  * Run mysql_proc_control every 5 seconds for better results.
  * You can safely apply db updates via 'Run db updates' task on any site.

# Changes in this release:

  * DB credentials are no longer visible in settings.php, only in drushrc.php
  * Delete default profiles in the hostmaster platform.
  * Disable _DEBUG_MODE if not enabled on the fly.
  * Disable newrelic-sysmond unless /root/.enable.newrelic.sysmond.cnf exists.
  * Drush: Upgrade command line version 6 to mini-6-14-09-2014
  * Nginx: Remove deprecated code - _HTTP_WILDCARD is already used by default.
  * Nginx: Use limit_conn protection only for known dynamic requests.
  * Redis Integration Module (cache_backport): Update to version 6.x-1.0-rc2
  * Redis Integration Module: Update to version mod-12-09-2014
  * Remove _ALLOW_UNSUPPORTED legacy and no longer working properly feature.
  * Remove dependency on Update Manager globally.
  * Remove deprecated multi-instance labels in the New Relic configuration.
  * Replace old hosting_civicrm_cron with newer hosting_civicrm module.
  * Set hosting_default_profile to 'minimal' to improve Ubercart 3 visibility.
  * The www53 PHP-FPM pool has been switched from port to default socket mode.
  * Use Provision CiviCRM boa-2.3.1-dev

# System upgrades in this release:

  * cURL 7.38.0 (if installed from sources)
  * Git 2.1.0 (if installed from sources)
  * Jetty 7.6.16.v20140903
  * Jetty 8.1.16.v20140903
  * Jetty 9.2.3.v20140905
  * PHP 5.3.29 EOL! Please read: http://php.net/archive/2014.php#id2014-08-14-1
  * PHP 5.4.32
  * PHP 5.5.16
  * Redis 2.8.14

# Fixes in this release:

  * Add cleanup for _GIT_FORCE_REINSTALL if added in .barracuda.cnf
  * Add missing drush cache-clear drush to improve upgrade path.
  * Add new features in the README.txt
  * Add wheezy to the exceptions list where required.
  * Allow to clear drush cache without directory restrictions.
  * Always set correct TMP path for supported users.
  * Cleanup for cron pid files in user specific .tmp dirs.
  * Count properly also symlinked files directories (improved).
  * D6 colorbox module requires old 1.3.18 library.
  * Delete drush_make leftovers.
  * Delete duplicate menu items on upgrade.
  * Do not allow to install SSH from sources on Trusty to avoid problems.
  * Do not skip daily.sh during barracuda system only update.
  * Eldir theme: Use max width for buttons, if possible.
  * Explain why installing RVM may take longer than expected.
  * Fix cleanup for drush aliases in sub-accounts.
  * Fix daily cleanup for user specific .tmp directories.
  * Fix docs/HINTS.txt
  * Fix for broken mariadb.list
  * Fix for broken, way too aggressive PHP-FPM monitoring.
  * Fix for ghost dirs cleanup.
  * Fix for ghost vhosts cleanup.
  * Fix for missing symlinks to existing platforms.
  * Fix for not working protection from blocking local IPs on multi-IP systems.
  * Fix for subdirs_support universal check.
  * Fix for unreliable _IS_OLD check on Octopus instances upgrade.
  * Fix for warning "Could not create directory ." on Hostmaster site Verify.
  * Fix the fields order in the site edit form.
  * Fix the regex to not whitelist unexpected IP ranges inadvertently.
  * Force cURL rebuild if installed with outdated OpenSSL version.
  * Guard against destructive or insecure tasks run on the hostmaster site.
  * Improve cleanup for empty platforms directories.
  * Improve monitoring to protect against convert trying to overload the system.
  * Issue #2330781 - Use Drush dt() wrapper instead of not always available t()
  * Issue #357 - Fix the logic for Git (re)install from sources.
  * Issue #360 - Exclude special --CDN vhosts from daily cleanup.
  * Issue #361 - Update and improve docs/FAQ.txt
  * Issue #369 - Automatically download and fix /bin/websh if missing.
  * Issue #369 - Restore classic /bin/sh symlink automatically if needed.
  * Issue #373 - Set correct TMP, TEMP, TMPDIR env variables in limited shell.
  * Issue #373 - Too restrictive lshell forbidden list breaks drush sql-sync.
  * Issue #380 - Nameserver / pdnsd problem -- Fixes also Issue #2007990.
  * Issue #381 - Zend OPcache forced adds useless noise in the log.
  * Issue #388 - Version 6.x-2.x of provision_civicrm requires hosting_civicrm
  * Issue #389 - hosting_civicrm breaks site install form with confusing error.
  * Issue #390 - Duplicate platforms nodes are created after upgrade to 2.3.0
  * Issue #395 - Validate username isn't reserved before running install script.
  * Issue #396 - Locale isn't getting set properly.
  * Issue #397 - Not actually prompted for platforms during installation.
  * Issue #398 - Make locales setup/fix for Debian always OS compatible.
  * Issue #399 - The hitimes gem needs to be pre-installed to support Omega4.
  * Issue #400 - CiviCRM is not installed on 2.3.0
  * Issue #401 - Create sites/all/* subdirs in Hostmaster early enough.
  * Issue #402 - Fix for ghost or disabled vhosts which still listen on IP.
  * Issue #405 - Installer hangs due to yes/no dialog - "Untrusted packages"
  * Issue #406 - Force keyring reinstall also upon 'GPG error'.
  * Issue #407 - Fix for 'username is already taken' error on a local VM install
  * Issue #408 - Fix for multiple funny typos. Thanks ar-jan!
  * Make it clear that subdomain and subdirectory name must be identical.
  * Make sure that keys subdirectory exists to avoid active platforms cleanup.
  * Make the PHP-FPM processes monitor less aggressive by default.
  * Nginx: Add config symlinks only on legacy instances.
  * Nginx: Add cron access support for subdir sites.
  * Nginx: Convert all vhosts to wildcard mode on Barracuda upgrade.
  * Nginx: Disable monitoring for POST requests related to cart/checkout URI.
  * Nginx: Do not touch nginx_wild_ssl.conf during this upgrade.
  * Nginx: Improve wildcard conversion procedure on some really old instances.
  * Nginx: Remove deprecated code and config templates.
  * Nginx: Sanitize aliases in vhost_disabled.tpl.php to avoid warnings.
  * Nginx: Update config includes to match optional BOA features improvements.
  * Nginx: Update unified configuration templates in Provision to unfork BOA.
  * Nginx: Update vhosts templates to match BOA improvements.
  * PHP: Avoid unintended duplicate rebuilds.
  * PHP: Sync disable_functions list.
  * Protect sites/all/drush
  * Provision: Backport provision_hosting_feature_enabled()
  * Provision: Remove legacy subdir code and update checks.
  * Redis config should sync with PHP-CLI, not PHP-FPM.
  * Remove legacy procs monitoring code.
  * Remove no longer needed limreq global fixes.
  * Remove no longer needed/used contrib updates.
  * Remove redundant file_exists() if is_readable() is also used.
  * Replace old hosting_civicrm_cron with newer hosting_civicrm module.
  * Restart pdnsd before running barracuda upgrade.
  * Restore BOA formatting for tasks log to improve readability.
  * Restore BOA naming convention and docs in Hostmaster.
  * Restore BOA naming convention for Installation profiles in Hostmaster.
  * Restore BOA strict _hosting_valid_fqdn* testing procedures in Hostmaster.
  * Restore BOA weight defaults in the form in Hostmaster.
  * Restore punycode in Hostmaster.
  * Restore tasks sort to always show tasks scheduled and running at the top.
  * Sanitize cli.info and fpm.info
  * Set _PLATFORMS_LIST properly.
  * Silence early sed replacements to avoid confusion.
  * Simplify colorbox-1.3.18 download.
  * Simplify colorbox-1.5.13 download.
  * Switch branch on the fly and add support for Aegir vanilla mode.
  * Sync /tmp access restrictions.
  * The hosting_civicrm_cron is now a submodule and should be also auto-enabled.
  * The wildcard transition **doesn't** affect vhosts for SSL enabled sites.
  * There is no need to force backend clone from GitHub on initial upgrade.
  * Update for the Hostmaster welcome page.
  * Update FPM monitoring settings.
  * Use as short labels on the site node as possible.
  * Use control files properly to not run redundant Jetty/Solr upgrade.
  * Use correct paths to platform level drushrc.php file.
  * Use correct Provision version on initial upgrade to 2.3.0
  * Use Drush6 with @hostmaster.
  * Use is_dir() instead of file_exists() when checking directory existence.
  * Use is_file() and is_link() instead of file_exists() before trying unlink()
  * Use is_readable() and file_exists() instead of file_exists() for backup.
  * Use is_readable() check instead of insufficient file_exists() for includes.
  * Use is_readable() instead of file_exists() when checking alias existence.
  * Install latest Git even if not specified via _XTRAS_LIST but previous
    version built from sources is detected.
  * Issue #2278847 - Derivatives can't be created on install with Drush and
    Aegir or when no vhost is available yet (Drupal Commons)

Having read through the above it is good to see the switch to use sockets rather than TCP/IP for php-fpm, not sure if there are any other changes that would effect us. I'll do the upgrade one evening this week.

Change History

comment:1 Changed 2 years ago by chris

  • Summary changed from New BOA-2.3.1 Stable Edition available to New BOA-2.3.2 Stable Edition available

There is another new version out, I didn't get around to doing the BOA-2.3.1 update last week, I'll try to get this one done this week, from the https://raw.githubusercontent.com/omega8cc/boa/master/CHANGELOG.txt :

### Stable BOA-2.3.2 Release - Full Edition
### Date: Thu Sep 18 15:16:33 PDT 2014
### Includes Aegir 2.1 with improvements
### Latest hotfix added on: Sun Sep 21 05:41:48 PDT 2014

# Release Notes:

  This BOA Edition includes important fixes to address some issues discovered
  after BOA-2.3.1 release. Please read also the release notes for BOA-2.3.1
  further below before running the upgrade!

#-### Important details on CiviCRM versions compatibility and profiles support

  * All BOA-2.3.x Editions fully support latest CiviCRM 4.5.0 for Drupal 7.
  * CiviCRM for Drupal 6 is not supported, but we are working on it.
  * CiviCRM support for Drupal 7 works great when added in sites/all/modules
  * CiviCRM support for Drupal 7 also works when added in profiles/foo/modules
    but no CiviCRM cron is currently managed until this known issue is fixed,
    therefore BOA-2.3.2 will check all platforms on the Octopus instance and if
    it will detect any with CiviCRM added in the installation profile directory
    tree, it will refuse to upgrade such instance to not break things for those
    using currently not fully supported CiviCRM codebase structure.

# New Octopus platforms:

  OpenChurch 2.0-b1 ------------ https://drupal.org/project/openchurch

# Updated Octopus platforms:

  Open Outreach 1.11 ----------- https://drupal.org/project/openoutreach
  OpenChurch 1.14 -------------- https://drupal.org/project/openchurch
  OpenScholar 3.15.1 ----------- http://theopenscholar.org

# New features and enhancements in this release:

  * Add makefiles for CiviCRM 4.4.7
  * Add makefiles for CiviCRM 4.5.0

# System upgrades in this release:

  * Drush: Upgrade command line version 6 to mini-6-18-09-2014
  * Nginx 1.7.5
  * PHPRedis: master-02-09-2014
  * Redis 2.8.17

# Fixes in this release:

  * Add extra cleanup for Drush related caches.
  * Do not allow system only upgrades if Master Instance is still on 2.2.x
  * Fix for broken pdnsd configuration if wrong IPs are detected.
  * Fix for insufficient permissions on files/civicrm/ConfigAndLog
  * Fix for insufficient permissions on files/civicrm/custom
  * Fix for insufficient permissions on files/civicrm/dynamic
  * Force problematic gems install to add them on accounts with enabled RVM.
  * Hardcode files.aegir.cc DNS entry.
  * Improve docs/ctrl/system.ctrl readability.
  * Issue #411 - Unable to update Octopus Instance - Reports PHP on 5.2
  * Make sure that lsb-release is installed properly.
  * New Relic not enabled if no custom ~/static/control/{fpm|cli}.info exists.
  * Nginx: Auto-Switch to wildcard all vhosts existing in the Master Instance.
  * Nginx: Convert all Octopus vhosts to wildcard mode on Barracuda upgrade.
  * Nginx: Convert config to use PHP 5.2 if the instance still depends on it.
  * Nginx: Delete ghost, outdated or broken config includes in all instances.
  * Nginx: Delete ghost, outdated or broken vhosts in all instances.
  * Nginx: Do not touch nginx_wild_ssl.conf during this upgrade.
  * Nginx: Improve wildcard conversion procedure on some really old instances.
  * Purge all ghost delete tasks before running hostmaster-migrate / upgrade.
  * Purge Drush related caches cleanly when needed.
  * Run check_civicrm_compatibility only on upgrade.
  * Update contrib in Open Atrium D7 to maintain upgrade path.
  * Use strict regex in vhosts listen mode conversion to not break ports.

comment:2 Changed 2 years ago by chris

  • Summary changed from New BOA-2.3.2 Stable Edition available to New BOA-2.3.3 Stable Edition available

Sorry this update hasn't been done yet, I'm going to try to get it completed before the end of the month, in the meantime another version of BOA has come out, BOA-2.3.3.

I have no idea why BOA will now restart ssh every hour, nothing else in this list strikes me as directly impacting us, but seeing as there have been so many update fixes it might well be a good thing that we didn't upgrade straight away.

### Stable BOA-2.3.3 Release - Full Edition
### Date: Sat Sep 27 01:25:46 PDT 2014
### Includes Aegir 2.1 with improvements

# Release Notes:

  This BOA Edition includes important fixes to address some issues discovered
  after BOA-2.3.1 release. Please read also the release notes for BOA-2.3.1
  further below before running the upgrade!

#-### Important details on CiviCRM versions compatibility and profiles support

  * All BOA-2.3.x Editions fully support latest CiviCRM 4.5.0 for Drupal 7.
  * CiviCRM for Drupal 6 is not supported because of known CiviCRM issues.
  * CiviCRM support for Drupal 7 works great when added in sites/all/modules
  * CiviCRM support for Drupal 7 also works when added in profiles/foo/modules
    but no CiviCRM cron is currently managed until this known issue is fixed,
    therefore BOA-2.3.3 will check all platforms on the Octopus instance and if
    it will detect any with CiviCRM added in the installation profile directory
    tree, it will refuse to upgrade such instance to not break things for those
    using currently not fully supported CiviCRM codebase structure.

# New Octopus platforms:

  OpenChurch 2.0-b1 ------------ https://drupal.org/project/openchurch

# Updated Octopus platforms:

  ERPAL 2.0 -------------------- https://drupal.org/project/erpal
  Guardr 1.13 ------------------ https://drupal.org/project/guardr
  Open Outreach 1.11 ----------- https://drupal.org/project/openoutreach
  OpenChurch 1.14 -------------- https://drupal.org/project/openchurch
  OpenPublic 1.0-rc5 ----------- https://drupal.org/project/openpublic
  OpenScholar 3.15.1 ----------- http://theopenscholar.org

# New features and enhancements in this release:

  * Add makefiles for CiviCRM 4.4.7
  * Add makefiles for CiviCRM 4.5.0

# Changes in this release:

  * Drush: Upgrade command line version 6 to mini-6-27-09-2014
  * Restart SSH hourly.
  * The INI variable redis_flush_forced_mode is now disabled by default.
  * Use aegir_custom_settings-6.x-3.12
  * Use Provision CiviCRM boa-2.3.3-dev

# System upgrades in this release:

  * MariaDB 10.0.14
  * Nginx 1.7.5
  * PHP 5.4.33
  * PHP 5.5.17
  * PHPRedis: master-02-09-2014
  * Redis 2.8.17

# Fixes in this release:

  * Add extra cleanup for Drush related caches.
  * Always respect _SSH_PORT if set.
  * Always start cron before aborting on error.
  * Do not add duplicate cron entry for runner.sh
  * Do not allow system only upgrades if Master Instance is still on 2.2.x
  * Do not disable _DNS_SETUP_TEST
  * Enable path_alias_cache by default also in the hostmaster site.
  * Fix for broken pdnsd configuration if wrong IPs are detected.
  * Fix for insufficient permissions on files/civicrm/ConfigAndLog
  * Fix for insufficient permissions on files/civicrm/custom
  * Fix for insufficient permissions on files/civicrm/dynamic
  * Fix for missing cron entry for Scout, if _SCOUT_KEY is not empty.
  * Fix the not working procedure to revert hostmaster features.
  * Force problematic gems install to add them on accounts with enabled RVM.
  * Fox for Java version for Jetty 9 on newer systems.
  * Hardcode files.aegir.cc DNS entry.
  * Improve docs/ctrl/system.ctrl readability.
  * Install openjdk on CI instances by default.
  * Issue #411 - Unable to update Octopus Instance - Reports PHP on 5.2
  * Issue #423 - Make sure that innodb_buffer_pool_size is not smaller than 64M
  * Issue #424 - Update mysqltuner.pl to support MariaDB 10.0
  * Make sure that lsb-release is installed properly.
  * Make the check_civicrm_compatibility more reliable to avoid false alarms.
  * New Relic not enabled if no custom ~/static/control/{fpm|cli}.info exists.
  * Nginx: Auto-Switch to wildcard all vhosts existing in the Master Instance.
  * Nginx: Avoid any downtime on upgrade by using www53.fpm.socket temporarily.
  * Nginx: Convert all config templates to wildcard mode in legacy instances.
  * Nginx: Convert all Octopus vhosts to wildcard mode on Barracuda upgrade.
  * Nginx: Convert config to use PHP 5.2 if the instance still depends on it.
  * Nginx: Delete ghost, outdated or broken config includes in all instances.
  * Nginx: Delete ghost, outdated or broken vhosts in all instances.
  * Nginx: Force special vhosts access rules rebuild hourly.
  * Nginx: Improve wildcard conversion procedure on some really old instances.
  * Purge all ghost delete tasks before running hostmaster-migrate / upgrade.
  * Purge Drush related caches cleanly when needed.
  * Recreate possibly broken vhosts.
  * Remove duplicate cron entry for runner.sh to avoid critical system load.
  * Remove legacy replacement to not convert config symlinks into regular files.
  * Run check_civicrm_compatibility only on upgrade.
  * Single feature revert may not be enough.
  * Update contrib in Open Atrium D7 to maintain upgrade path.
  * Update cron defaults and remove legacy code.
  * Update default SSL Wildcard Nginx Proxy to use wildcard listen mode.
  * Use strict regex in vhosts listen mode conversion to not break ports.


### Stable BOA-2.3.2 Release - Full Edition
### Date: Thu Sep 18 15:16:33 PDT 2014
### Includes Aegir 2.1 with improvements

  Release Notes and changelog for BOA-2.3.2 has been merged into BOA-2.3.3
  above after several hotfixes and various updates have been added shortly
  after 2.3.2 release to address all identified post-release issues.

comment:3 Changed 2 years ago by chris

I'm going to run the upgrade now.

comment:4 Changed 2 years ago by chris

  • Add Hours to Ticket changed from 0.0 to 0.53
  • Status changed from new to closed
  • Resolution set to fixed
  • Total Hours changed from 0.0 to 0.53

Following PuffinServer#UpgradingBOA

sudo -i
screen
cd
wget -q -U iCab http://files.aegir.cc/BOA.sh.txt
bash BOA.sh.txt

BOA Meta Installer setup completed
Please check INSTALL.txt and UPGRADE.txt at http://bit.ly/boa-docs for how-to
Bye

barracuda up-stable ; octopus up-stable all both


Barracuda [Mon Sep 29 20:16:28 BST 2014] ==> BOA Skynet welcomes you aboard!

Barracuda [Mon Sep 29 20:16:32 BST 2014] ==> INFO: UPGRADE
Barracuda [Mon Sep 29 20:16:32 BST 2014] ==> INFO: Reading your /root/.barracuda.cnf config file
Barracuda [Mon Sep 29 20:16:33 BST 2014] ==> NOTE! Please review all config options displayed below
Barracuda [Mon Sep 29 20:16:33 BST 2014] ==> NOTE! It will *override* all settings in the Barracuda script
Barracuda [Mon Sep 29 20:16:33 BST 2014] ==> Legacy PHP-CLI 5.2 is not used on this system
Barracuda [Mon Sep 29 20:16:33 BST 2014] ==> Legacy PHP-FPM 5.2 is not used on this system

###
### Configuration created on 121215-1545
### with Barracuda version BOA-2.0.4
###
### NOTE: the group of settings displayed bellow will *not* be overriden
### on upgrade by the Barracuda script nor by this configuration file.
### They can be defined only on initial Barracuda install.
###
_MY_OWNIP="81.95.52.103"
#_MY_OWNIP=""
_MY_HOSTN="puffin.webarch.net"
#_MY_HOSTN=""
_MY_FRONT="master.puffin.webarch.net"
_THIS_DB_HOST=localhost
#_THIS_DB_HOST=FQDN
_SMTP_RELAY_TEST=YES
_SMTP_RELAY_HOST=""
_LOCAL_NETWORK_IP=""
_LOCAL_NETWORK_HN=""
###
### NOTE: the group of settings displayed bellow
### will *override* all listed settings in the Barracuda script,
### both on initial install and upgrade.
###
_MY_EMAIL="chris@webarchitects.co.uk"
_XTRAS_LIST="PDS CSF CHV"
_AUTOPILOT=NO
_DEBUG_MODE=NO
_DB_SERVER=MariaDB
_SSH_PORT=22
_LOCAL_DEBIAN_MIRROR="ftp.debian.org"
_LOCAL_UBUNTU_MIRROR="archive.ubuntu.com"
_FORCE_GIT_MIRROR=""
_DNS_SETUP_TEST=YES
_NGINX_EXTRA_CONF=""
_NGINX_WORKERS=AUTO
_PHP_FPM_WORKERS=AUTO
_PHP_FPM_VERSION=5.3
_PHP_CLI_VERSION=5.3
_CUSTOM_CONFIG_CSF=YES
#_CUSTOM_CONFIG_SQL=NO
_CUSTOM_CONFIG_SQL=YES
_CUSTOM_CONFIG_REDIS=NO
_CUSTOM_CONFIG_PHP_5_2=NO
_CUSTOM_CONFIG_PHP_5_3=NO
#_CUSTOM_CONFIG_PHP_5_3=YES
_SPEED_VALID_MAX=3600
_NGINX_DOS_LIMIT=300
#_SYSTEM_UPGRADE_ONLY=YES
_SYSTEM_UPGRADE_ONLY=NO
_NEWRELIC_KEY=
###
### Configuration created on 121215-1545
### with Barracuda version BOA-2.0.4
###
_EXTRA_PACKAGES=
_PHP_EXTRA_CONF=""
_STRONG_PASSWORDS=YES
_DB_BINARY_LOG=NO
_DB_ENGINE=InnoDB
_NGINX_LDAP=NO
_PHP_GEOS=NO
_PHP_MONGODB=NO
_AEGIR_UPGRADE_ONLY=NO
### Squeeze to Wheezy upgrade config
### See /trac/ticket/535
#_SQUEEZE_TO_WHEEZY=YES
_SQUEEZE_TO_WHEEZY=NO
_NGINX_FORWARD_SECRECY=YES
_NGINX_SPDY=YES
_NGINX_NAXSI=NO
_PERMISSIONS_FIX=YES
_MODULES_FIX=YES
_MODULES_SKIP=""
_SSL_FROM_SOURCES=NO
_SSH_FROM_SOURCES=NO
_RESERVED_RAM=0
_PHP_MULTI_INSTALL="5.3"
_CUSTOM_CONFIG_LSHELL=NO
_CUSTOM_CONFIG_PHP55=NO
_CUSTOM_CONFIG_PHP54=NO
_CUSTOM_CONFIG_PHP53=NO
_CUSTOM_CONFIG_PHP52=NO
_CPU_SPIDER_RATIO=3
_CPU_MAX_RATIO=6
_CPU_CRIT_RATIO=9
_PHP_FPM_DENY=""
_REDIS_LISTEN_MODE=PORT
_STRICT_BIN_PERMISSIONS=NO
_DB_SERIES=5.5
_SCOUT_KEY=
_INNODB_LOG_FILE_SIZE=AUTO

Do you want to proceed with the upgrade? [Y/n] Y
Barracuda [Mon Sep 29 20:17:43 BST 2014] ==> INFO: Checking your system version...
 
Barracuda [Mon Sep 29 20:17:43 BST 2014] ==> Aegir on Debian/wheezy - Skynet Agent v.BOA-2.3.3
 
Barracuda [Mon Sep 29 20:17:45 BST 2014] ==> INFO: Updating packages sources list...
Barracuda [Mon Sep 29 20:17:45 BST 2014] ==> INFO: We will use Debian mirror ftp.debian.org
Barracuda [Mon Sep 29 20:17:55 BST 2014] ==> INFO: Downloading little helpers...
Barracuda [Mon Sep 29 20:17:58 BST 2014] ==> INFO: Checking BARRACUDA version...
Barracuda [Mon Sep 29 20:17:58 BST 2014] ==> INFO: BARRACUDA version test: OK
 
Barracuda [Mon Sep 29 20:17:58 BST 2014] ==> UPGRADE START -> checkpoint: 

  * Your e-mail address appears to be chris@webarchitects.co.uk - is that correct?
  * Your server hostname is puffin.webarch.net.
  * Your Aegir control panel is/will be available at https://master.puffin.webarch.net.

 
Do you want to proceed with the upgrade? [Y/n] Y
Barracuda [Mon Sep 29 20:18:12 BST 2014] ==> INFO: Cleaning up temp files in /var/opt/
Barracuda [Mon Sep 29 20:18:12 BST 2014] ==> INFO: Installing extra Drush versions
Barracuda [Mon Sep 29 20:18:12 BST 2014] ==> INFO: Drush mini-4-26-08-2014 installation complete
Barracuda [Mon Sep 29 20:18:13 BST 2014] ==> INFO: Drush mini-6-27-09-2014 installation complete
Barracuda [Mon Sep 29 20:18:14 BST 2014] ==> INFO: Running aptitude update...
Barracuda [Mon Sep 29 20:19:07 BST 2014] ==> INFO: Upgrading required libraries and tools
Barracuda [Mon Sep 29 20:19:07 BST 2014] ==> NOTE! This step may take a few minutes, please wait...
Barracuda [Mon Sep 29 20:20:01 BST 2014] ==> INFO: Testing Nginx version...
Barracuda [Mon Sep 29 20:20:01 BST 2014] ==> INFO: Installed Nginx version nginx/1.7.4, upgrade required
Barracuda [Mon Sep 29 20:20:02 BST 2014] ==> INFO: Upgrading Nginx...

Barracuda [Mon Sep 29 20:21:32 BST 2014] ==> INFO: Running aptitude full-upgrade, please wait...
Barracuda [Mon Sep 29 20:22:07 BST 2014] ==> INFO: Testing Nginx version...
Barracuda [Mon Sep 29 20:22:07 BST 2014] ==> INFO: Installed Nginx version nginx/1.7.5, OK
Barracuda [Mon Sep 29 20:22:07 BST 2014] ==> INFO: Installing MySecureShell 1.33...
Barracuda [Mon Sep 29 20:22:34 BST 2014] ==> INFO: Checking SMTP connections...
Barracuda [Mon Sep 29 20:22:34 BST 2014] ==> INFO: Upgrading a few more tools...
Barracuda [Mon Sep 29 20:22:41 BST 2014] ==> INFO: Checking if PHP upgrade is available
Barracuda [Mon Sep 29 20:22:48 BST 2014] ==> INFO: PHP EXTRA is --with-ldap --with-gmp --with-xpm-dir=/usr
Barracuda [Mon Sep 29 20:22:48 BST 2014] ==> INFO: Installed PHP version 5.3.29, OK
Barracuda [Mon Sep 29 20:22:48 BST 2014] ==> INFO: Installing PhpRedis upgrade for PHP-FPM 5.3.29...
Barracuda [Mon Sep 29 20:23:12 BST 2014] ==> INFO: Installed Redis version 2.8.14, upgrade required
Barracuda [Mon Sep 29 20:23:12 BST 2014] ==> INFO: Installing Redis update for Debian/wheezy...
Barracuda [Mon Sep 29 20:24:25 BST 2014] ==> INFO: Generating random password for Redis server
Barracuda [Mon Sep 29 20:24:25 BST 2014] ==> INFO: Updating MariaDB and PHP configuration
Barracuda [Mon Sep 29 20:24:27 BST 2014] ==> INFO: OS and services upgrade completed
 
Barracuda [Mon Sep 29 20:24:27 BST 2014] ==> INFO: Restarting MariaDB server, please wait...
Barracuda [Mon Sep 29 20:24:46 BST 2014] ==> INFO: Upgrading MariaDB tables if necessary, please wait a minute...
 
Do you want to upgrade Aegir Master Instance? [Y/n] Y
Barracuda [Mon Sep 29 20:26:24 BST 2014] ==> INFO: Running Aegir Master Instance upgrade
Barracuda [Mon Sep 29 20:26:26 BST 2014] ==> INFO: Syncing provision backend db_passwd...
Barracuda [Mon Sep 29 20:26:38 BST 2014] ==> INFO: Running hosting-dispatch (1/3)...
Barracuda [Mon Sep 29 20:26:48 BST 2014] ==> INFO: Running hosting-dispatch (2/3)...
Barracuda [Mon Sep 29 20:26:57 BST 2014] ==> INFO: Running hosting-dispatch (3/3)...
Barracuda [Mon Sep 29 20:27:00 BST 2014] ==> INFO: Syncing hostmaster frontend db_passwd...
Barracuda [Mon Sep 29 20:27:00 BST 2014] ==> INFO: Testing previous install...
Barracuda [Mon Sep 29 20:27:00 BST 2014] ==> INFO: Test OK, we can proceed with Hostmaster upgrade
Barracuda [Mon Sep 29 20:27:00 BST 2014] ==> INFO: Moving old directories
Barracuda [Mon Sep 29 20:27:00 BST 2014] ==> INFO: Downloading drush...
Barracuda [Mon Sep 29 20:27:02 BST 2014] ==> INFO: Drush seems to be functioning properly
Barracuda [Mon Sep 29 20:27:03 BST 2014] ==> INFO: Installing provision backend in /var/aegir/.drush
Barracuda [Mon Sep 29 20:27:03 BST 2014] ==> INFO: Downloading Drush and Provision extensions...
Barracuda [Mon Sep 29 20:27:03 BST 2014] ==> INFO: Running hostmaster-migrate, please wait...
Barracuda [Mon Sep 29 20:28:35 BST 2014] ==> INFO: Syncing hostmaster frontend db_passwd...
Barracuda [Mon Sep 29 20:29:47 BST 2014] ==> INFO: Aegir Master Instance upgrade completed
 
 
Do you want to install Chive MariaDB Manager? [Y/n] Y
Barracuda [Mon Sep 29 20:29:58 BST 2014] ==> INFO: Installing Chive MariaDB Manager...
Barracuda [Mon Sep 29 20:30:01 BST 2014] ==> INFO: Chive MariaDB Manager installation completed
Barracuda [Mon Sep 29 20:30:01 BST 2014] ==> INFO: _PHP_CN set to www53 for Chive MariaDB Manager
Barracuda [Mon Sep 29 20:30:07 BST 2014] ==> INFO: _PHP_CN set to www53 for Collectd Graph Panel
Barracuda [Mon Sep 29 20:30:12 BST 2014] ==> INFO: Restarting Redis, PHP-FPM and Nginx
Barracuda [Mon Sep 29 20:30:20 BST 2014] ==> INFO: Restarting MariaDB server
Barracuda [Mon Sep 29 20:30:32 BST 2014] ==> INFO: New secure random password for MariaDB generated and updated
Barracuda [Mon Sep 29 20:30:32 BST 2014] ==> INFO: New entry added to /var/log/barracuda_log.txt
Barracuda [Mon Sep 29 20:30:32 BST 2014] ==> INFO: Cleaning up system swap, it may take a moment, please wait...
 
Barracuda [Mon Sep 29 20:30:37 BST 2014] ==> CARD: Now charging your credit card for this auto-upgrade magic...
Barracuda [Mon Sep 29 20:30:43 BST 2014] ==> JOKE: Just kidding! Enjoy your Aegir Hosting System :)
 
Barracuda [Mon Sep 29 20:30:43 BST 2014] ==> Final post-upgrade cleaning, please wait a moment...
Barracuda [Mon Sep 29 20:33:36 BST 2014] ==> BYE!

BARRACUDA upgrade completed
Bye

load is 12 while maxload is 600
Octopus upgrade for User /data/disk/tn
Waiting 3 seconds...
 
Octopus [Mon Sep 29 20:33:47 BST 2014] ==> BOA Skynet welcomes you aboard!
 
Octopus [Mon Sep 29 20:33:50 BST 2014] ==> INFO: Reading your /root/.tn.octopus.cnf config file
Octopus [Mon Sep 29 20:33:51 BST 2014] ==> NOTE! Please review all config options displayed below
 
###
### Configuration created on 121215-1617 with
### Octopus version BOA-2.0.4
###
### NOTE: the group of settings displayed bellow
### will *override* all listed settings in the Octopus script.
###
_USER="tn"
_MY_EMAIL="chris@webarchitects.co.uk"
_PLATFORMS_LIST="D7P OA7"
_AUTOPILOT=YES
_HM_ONLY=NO
_O_CONTRIB_UP=YES
_DEBUG_MODE=NO
_MY_OWNIP=
_FORCE_GIT_MIRROR=""
_THIS_DB_HOST=localhost
_DNS_SETUP_TEST=NO
_HOT_SAUCE=NO
_USE_CURRENT=YES
_REMOTE_CACHE_IP=127.0.0.1
_LOCAL_NETWORK_IP=
_PHP_FPM_VERSION=5.3
_PHP_CLI_VERSION=5.3
###
### NOTE: the group of settings displayed bellow will be *overriden*
### by config files stored in the /data/disk/tn/log/ directory,
### but only on upgrade.
###
_DOMAIN="tn.puffin.webarch.net"
_CLIENT_EMAIL="chris@webarchitects.co.uk"
_CLIENT_OPTION="SSD"
_CLIENT_SUBSCR="Y"
_CLIENT_CORES="14"
###
### Configuration created on 121215-1617 with
### Octopus version BOA-2.0.4
###
_STRONG_PASSWORDS=NO
_DEL_OLD_EMPTY_PLATFORMS=90
_SQL_CONVERT=NO
_DEL_OLD_BACKUPS=0
_DEL_OLD_TMP=0
_PHP_FPM_WORKERS=AUTO
_PHP_FPM_TIMEOUT=AUTO
_PHP_FPM_DENY=""
_RESERVED_RAM=0
 
Octopus [Mon Sep 29 20:33:56 BST 2014] ==> UPGRADE in progress...
 
Octopus [Mon Sep 29 20:33:57 BST 2014] ==> START -> checkpoint: 

  * Your Aegir control panel for this instance is available at https://tn.puffin.webarch.net
  * Your Aegir system user for this instance is tn
  * This Octopus will use PHP-CLI 5.3 for all sites
  * This Octopus will use PHP-FPM 5.3 both for D6 and D7 sites
  * This Octopus includes platforms: D7P OA7
  * This Octopus options are listed as SSD / Y / 14 C

 
Octopus [Mon Sep 29 20:33:57 BST 2014] ==> 8s before we will continue...
Octopus [Mon Sep 29 20:34:12 BST 2014] ==> UPGRADE A: Aegir automated install script part A
Octopus [Mon Sep 29 20:34:12 BST 2014] ==> UPGRADE A: Checking OCTOPUS version...
Octopus [Mon Sep 29 20:34:12 BST 2014] ==> UPGRADE A: OCTOPUS version test: OK
Octopus [Mon Sep 29 20:34:12 BST 2014] ==> UPGRADE A: Shared platforms code v.008 (latest available) will be used
Octopus [Mon Sep 29 20:34:12 BST 2014] ==> UPGRADE A: Creating directories with correct permissions...
Octopus [Mon Sep 29 20:34:12 BST 2014] ==> UPGRADE A: Syncing provision backend db_passwd...
Octopus [Mon Sep 29 20:34:21 BST 2014] ==> UPGRADE A: Running hosting-dispatch (1/3)...
Octopus [Mon Sep 29 20:34:30 BST 2014] ==> UPGRADE A: Running hosting-dispatch (2/3)...
Octopus [Mon Sep 29 20:34:39 BST 2014] ==> UPGRADE A: Running hosting-dispatch (3/3)...
 
Octopus [Mon Sep 29 20:34:43 BST 2014] ==> UPGRADE A: Syncing hostmaster frontend db_passwd...
Octopus [Mon Sep 29 20:34:43 BST 2014] ==> UPGRADE A: Switching user and running AegirSetupB...
Octopus [Mon Sep 29 20:34:43 BST 2014] ==> UPGRADE B: Aegir automated install script part B
Octopus [Mon Sep 29 20:34:43 BST 2014] ==> UPGRADE B: Creating directories with correct permissions
Octopus [Mon Sep 29 20:34:43 BST 2014] ==> UPGRADE B: Running standard installer
Octopus [Mon Sep 29 20:34:43 BST 2014] ==> UPGRADE B: Downloading drush...
Octopus [Mon Sep 29 20:34:46 BST 2014] ==> UPGRADE B: Drush seems to be functioning properly
Octopus [Mon Sep 29 20:34:46 BST 2014] ==> UPGRADE B: Installing provision backend in /data/disk/tn/.drush
Octopus [Mon Sep 29 20:34:46 BST 2014] ==> UPGRADE B: Downloading Drush and Provision extensions...
Octopus [Mon Sep 29 20:34:47 BST 2014] ==> UPGRADE B: Testing previous install...
Octopus [Mon Sep 29 20:35:03 BST 2014] ==> UPGRADE B: Hostmaster STATUS: upgrade start
Octopus [Mon Sep 29 20:35:03 BST 2014] ==> UPGRADE B: Running hostmaster-migrate, please wait...
Octopus [Mon Sep 29 20:36:46 BST 2014] ==> UPGRADE B: Hostmaster STATUS: upgrade completed
Octopus [Mon Sep 29 20:36:46 BST 2014] ==> UPGRADE B: Simple check if Aegir upgrade is successful
Octopus [Mon Sep 29 20:36:46 BST 2014] ==> UPGRADE B: Aegir upgrade test result: OK
Octopus [Mon Sep 29 20:36:46 BST 2014] ==> UPGRADE B: Enhancing Aegir UI, please wait...
Octopus [Mon Sep 29 20:39:18 BST 2014] ==> UPGRADE A: Syncing hostmaster frontend db_passwd...
Octopus [Mon Sep 29 20:39:19 BST 2014] ==> UPGRADE A: Aegir Satellite Instance upgrade completed
 
Octopus [Mon Sep 29 20:39:40 BST 2014] ==> UPGRADE A: Creating shared directories...
Octopus [Mon Sep 29 20:39:41 BST 2014] ==> UPGRADE A: Running o_contrib modules check and upgrade...
Octopus [Mon Sep 29 20:40:22 BST 2014] ==> UPGRADE A: Switching user and running Platforms build
Octopus [Mon Sep 29 20:40:22 BST 2014] ==> UPGRADE C: Aegir automated install script part C
Octopus [Mon Sep 29 20:40:22 BST 2014] ==> UPGRADE C: Shared platforms code v.008 (latest available) will be used
 
Octopus [Mon Sep 29 20:40:22 BST 2014] ==> UPGRADE C: Removing some unused core files...
Octopus [Mon Sep 29 20:40:22 BST 2014] ==> UPGRADE C: Running Platforms Save & Verify tasks, please wait...
Octopus [Mon Sep 29 20:40:22 BST 2014] ==> UPGRADE A: Platforms installation completed
Octopus [Mon Sep 29 20:40:22 BST 2014] ==> UPGRADE A: Cleaning up various dot files...
Octopus [Mon Sep 29 20:40:27 BST 2014] ==> UPGRADE A: Creating ftp symlinks
Octopus [Mon Sep 29 20:40:27 BST 2014] ==> UPGRADE A: Preparing setupmail.txt
Octopus [Mon Sep 29 20:40:27 BST 2014] ==> UPGRADE A: Resending setup e-mail on upgrade...
Octopus [Mon Sep 29 20:40:27 BST 2014] ==> UPGRADE A: New entry added to /data/disk/tn/log/octopus_log.txt
Octopus [Mon Sep 29 20:40:27 BST 2014] ==> UPGRADE A: Final cleaning, please wait a moment...
Octopus [Mon Sep 29 20:42:09 BST 2014] ==> UPGRADE A: Starting the cron now
Octopus [Mon Sep 29 20:42:09 BST 2014] ==> UPGRADE A: All done!
Octopus [Mon Sep 29 20:42:09 BST 2014] ==> BYE!
Waiting 7 seconds...
Done for /data/disk/tn



OCTOPUS upgrade completed
Bye

While the above was running the PuffinServer#Muninconfigchanges and PuffinServer#nginxconfigchanges were applied and the site was tested and everything appears to be working.

Note: See TracTickets for help on using tickets.