- Table of Contents
- Updates for Cloud Customers
- Updates For On-Premise Customers
- How to Find Your Currently Installed Versions
- Operating System Updates
- Update Prerequisites
- Update Procedure
- Version-Specific Steps
Updates for Cloud Customers
We update the majority of our Cloud Customers about once a month. The updates typically occur in the first few business days of the month.
Updates For On-Premise Customers
On-Premise customers can either ask GreenArrow technical support to perform updates for them or perform updates on their end by following the instructions in this document.
How to Find Your Currently Installed Versions
Recent GreenArrow installations make their version numbers available in the web interface.
GreenArrow Engine’s version number is shown in the footer of each Engine web page, next to the copyright statement. For example, this system is running Engine 4.1.223:
Copyright © 2012–2018 DRH Internet Inc. | Version 4.1.223
To view GreenArrow Studio’s version number, navigate to “Admin” => “System” and view the “Version Number” field:
If you’re running an older GreenArrow installation which does not show versions in the web interface or just prefer to use the command line, then you can also SSH into your server and run the following command to view GreenArrow’s versions:
rpm -q greenarrow-engine greenarrow-studio 2> /dev/null || dpkg -l greenarrow-engine greenarrow-studio
The exact format of the above command’s output will vary, depending on what Linux distribution you’re using. As an example, here’s what the output will look like in CentOS:
The above indicates that GreenArrow Engine 4.1.210-0 and GreenArrow Studio 4.103.5-0 are installed.
Operating System Updates
We recommend keeping non-GreenArrow packages up-to-date. When updating both GreenArrow and non-GreenArrow packages, the safest approach is to perform non-GreenArrow package updates first.
The GreenArrow update procedure has the following prerequisites:
An experienced Linux systems administrator who can execute the update procedure.
/var/hvmail/bin/greenarrow_blockersfile must exist, and when executed, it must output text telling you that it’s safe to proceed with the update. This is described in more detail in step 2 of the update procedure below.
Verify that you’ve met all of the prerequisites listed above before proceeding.
This section describes how to update both GreenArrow Engine and Studio.
GreenArrow Engine and Studio have some shared code, so don’t be alarmed if you’re a GreenArrow Engine only customer, and see references to GreenArrow Studio in the output of the commands you run during the update.
GreenArrow has a lot of moving parts, so we recommend reading through the entire update procedure before proceeding, and considering whether the update should be scheduled. Depending on how old your current GreenArrow version is, what hardware is in use, and how much data is present, you can expect anywhere from a few seconds to a few minutes of downtime during most updates.
SSH into the GreenArrow server as the
rootuser, or a user with equivalent permissions.
Check if it’s safe to proceed with the update, and only proceed if the
greenarrow_blockerscommand outputs text telling you that it’s safe to proceed:
Stop here if
greenarrow_blockersreturns anything other than this:
It is safe to upgrade this system by following the instructions at: http://docs.drh.net/greenarrow-engine/Server-Management-and-Backups/GreenArrow-Updates
Check what version of GreenArrow Engine is installed:
rpm -q greenarrow-engine 2> /dev/null || dpkg -l greenarrow-engine
Read through the Version-Specific Steps section for any extra manual steps which are needed as part of the update process. Complete them at the time indicated.
Update GreenArrow’s packages.
On Red Hat-based Linux distributions, such as CentOS, run:
yum --enablerepo=greenarrow update 'greenarrow-*'
On Debian-based Linux distributions, such as Ubuntu:
Enable GreenArrow’s package repository:
sed -e '/greenarrow main/ s/^#*//' -i /etc/apt/sources.list.d/greenarrow.list
Install the updated packages:
apt-get update && apt-get --only-upgrade install 'greenarrow-*'
Disable GreenArrow’s package repository to prevent accidental updates in the future:
sed -e '/greenarrow main/ s/^#*/#/' -i /etc/apt/sources.list.d/greenarrow.list
Run migrations. This step normally takes anywhere from a few seconds to a few minutes to complete:
Complete any post-update steps that you noted after reading through the the Version-Specific Steps section.
Verify that some common misconfigurations are not present. Each test gets a simple pass/fail result:
Verify that all services are running normally. Any services with an abnormal state are shown in red:
Send yourself a test email (replacing [email protected] with your actual email address):
date | /var/hvmail/bin/mailsubj "GreenArrow Test Message" [email protected]
That’s it! You’re now running the latest GreenArrow releases.
The following table is in ascending chronological order. Please begin reading through it at the first release listed which comes after your currently installed version and work your down. Here are two examples:
If you have GreenArrow Engine 4.1.233-0 or later installed, then there are no version-specific steps to complete.
If you have GreenArrow Engine 4.1.217-0 installed, then you would begin with the upgrade instructions for 4.1.226-0.
All steps in this table should be completed before updating GreenArrow’s packages unless otherwise indicated:
April 18, 2018
This update introduces the greenarrow.conf configuration file. If GreenArrow’s Apache or PostgreSQL installation has a customized configuration, then one or more configuration directives may need to be moved into
For this update, please:
August 16, 2018
Starting with this update, the contents of the
Before performing this update, please review the contents of your
If the new behavior presents a problem, then instead of defining VirtualHosts in
August 31, 2018
This release lowers the dynamic defaults for apache_max_clients and passenger_max_requests_in_queue, reducing overall memory utilization to be closer to what it was before the April 2018 release of Engine 4.1.216.
If you’re running Engine 4.1.215 or earlier, then your release predates dynamic defaults, so no extra steps are required.
If you’re running Engine 4.1.216 or later, then we recommend the following:
The new dynamic defaults are calculated as follows:
All systems start with the following:
If the system has more than 4GB of RAM and at least 4 CPU cores, those numbers are increased:
September 18, 2018
Before installing this update, please check if the
If the directory does exist, then you’re using the old command line DKIM configuration system that was replaced in this release. You’ll need to convert any DKIM keys in that directory to a Web or API based DKIM configurations before the upgrade or the new command line system after the upgrade.
If the directory does not exist, then no additional steps are required.
October 17, 2018