Engine Yard Release Notes- March 2017

Engine Yard Stack Release Notes for March 29th, 2017

Minor: Engine Yard Gentoo 2016 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2016 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2016 stack. You can access it by using the Stack select field in the Environment UI: stable-v5-3.0.24

It's best practice to upgrade your Engine Yard Gentoo 2016 (stable-v5) stack regularly for the latest security and product updates. This week's updates:

• Sets up cron jobs for Passenger monitoring that automatically kills workers above a memory threshold.
• Adds the Logentries custom chef recipe
• Upgrades Ruby 2.2.x to 2.2.6 and 2.3.x to 2.3.3

Note: currently running Ruby processes will continue to run on the existing version of ruby. To update these processes, redeploy your app, and restart any background ruby processes. If using passenger, run /etc/init.d/nginx upgrade on each app instance to restart passenger and its workers on the new version.

• Adds availability of Node.js version 4.7.3 and 6.9.5. These are the new default versions for Node.js 4 and Node.js 6, respectively.

Note: currently running Node.js processes will continue to run on the existing version of ruby. To update these processes, redeploy your app.

For more information on Engine Yard Gentoo 2016, see the Engine Yard Gentoo 2016 docs.

Engine Yard Stack Release Notes for March 16th, 2017

Minor: Engine Yard Gentoo 12.11 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 12.11 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 12.11 stack. You can access it by using the Stack select field in the Environment UI:stable-v4-2.0.120

It's best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates.

• Adds filesystem consistnecy healthcheck to collectd monitoring.
• Modifies database mounts to use noatime instead of relative.
• Remove DES and 3DES from the default cipher list.
• Corrects an issue where MySQL versions lower than 5.6.24 won't start when booting from snapshot due to show_old_temporals in the config file.
• Updates Passenger 4 gem for CVE-2015-7519
• Upgrade Ruby 2.2.x to 2.2.6 and 2.3.x to 2.3.3 on instances using OpenSSL 1.0.1 (default). Note: currently running Ruby processes will continue to run on the existing version of ruby. To update these processes, redeploy your app, and restart any background ruby processes. If using passenger, run /etc/init.d/nginx upgrade on each app instance to restart passenger and its workers on the new version.

For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.

Minor: Engine Yard Gentoo 2016 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2016 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2016 stack. You can access it by using the Stack select field in the Environment UI: stable-v5-3.0.23

It's best practice to upgrade your Engine Yard Gentoo 2016 (stable-v5) stack regularly for the latest security and product updates. This week's updates:

• Removes DES and 3DES from the default cipher list
• Updates haproxy to version 1.6
• Corrects the chef process identifying the full local MySQL version, and moves the EBS mount process earlier in the MySQL cookbook.
• Fixes the Sidekiq recipe to address broken pipe errors encountered with newer versions of the Sidekiq gem
• Updates the Elasticsearch and Solr recipes to use the latest IcedTea JDK that patches recent security vulnerabilities
• Adds initial support for yarn and pm2

For more information on Engine Yard Gentoo 2016, see the Engine Yard Gentoo 2016 docs.

Engine Yard Stack Release Notes for March 1st, 2017

Minor: Engine Yard Gentoo 2016 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2016 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2016 stack. You can access it by using the Stack select field in the Environment UI:

It's best practice to upgrade your Engine Yard Gentoo 2016 (stable-v5) stack regularly for the latest security and product updates. This week's updates:

• Adds the eyrestore tool for safe and simple database restores between environments.
• Adds filesystem consistency healthcheck to collectd monitoring.
• Adds the resque-scheduler custom chef recipe.
• Modifies database mounts to use noatime instead of relatime.
• Updates documentation for custom chef recipes.
• Updates the Redis recipe to support slave replication.
• Updates the Elasticsearch recipe with correct download URL.
• Fixes incorrectly setting postgres temp_tablespaces.
• Fixes a bug wherein chef fails to complete with puma and an ssl certificate assigned.
• Fixes a passenger 5 bug caused by multiple domain names.
• Fixes a bug on the Sidekiq recipe to allow it to handle queue names containing punctuations.

For more information on Engine Yard Gentoo 2016, see the Engine Yard Gentoo 2016 docs.