The updates described are either important (where you need to take action) or of interest (you might want to know about these changes but you don’t need to do anything).

Minor: Engine Yard stack update

January 30th, 2012

The following changes have been made to the Engine Yard stack:

• Upgraded Redis to 2.4.6.
• Added Collectd support for PostgreSQL alerts.

These changes are applied when you upgrade your environment.

 

 

Minor: Node.js upgrade

January 26th, 2012

Upgrade to Node.js 0.6.8 from Node.js 0.6.1.

Node.js is now installed from EY Portage and uninstalled from /opt/node.

(Node.js is an Engine Yard Labs feature.)

To take advantage of this upgrade, upgrade your environment.

 

 

Minor: Trinidad and JVM options are now configurable via env.custom

January 26th, 2012

If your environment runs on the Trinidad application server stack, you can now configure Trinidad and JVM options via the /data/app_name/shared/config/env.custom file.

This feature becomes available when you upgrade your environment.

 

 

Fixes: Engine Yard stack upgrade

January 26th, 2012

The following fixes have been made to the Engine Yard stack:

• A problem where ey-monitor got linked even when not installed.
• A problem where Trinidad did not start because the connection pool was too small.

These fixes are applied when you upgrade your environment.

 

 

Fix: Engine Yard stack upgrade

January 20th, 2012

Fixed an issue where MySQL alerts displayed in PostgreSQL environments.

This fix is applied when you upgrade your environment.

 

 

Minor: engineyard gem update

January 19th, 2012

Version 1.4.21 of the engineyard gem contains logout and login commands. Use these commands to change from one user account to another within the CLI. For more information, see Switching Engine Yard accounts.

 

Fix: Engine Yard stack upgrade

January 18th, 2012

Fixed an issue where utility instances were being incorrectly configured as application instances.

This fix is applied when you upgrade your environment.

 

 

Minor: Trinidad and JVM options are now configurable

January 17th, 2012

On January 26th, 2012, this feature was superseded by “Minor: Trinidad and JVM options are now configurable via env.custom” above.

If your environment runs on the Trinidad application server stack, you can now configure Trinidad and JVM options with a keep file.

 

 

Fix: Engine Yard stack upgrade

January 17th, 2012

The following fixes have been made to the Engine Yard stack:

• A problem with database backups in the US West (Oregon) and South America (Sao Paulo)
• A problem where PostgreSQL alerts displayed as MySQL alerts

These fixes are applied when you upgrade your environment.

 

 

Major: Engine Yard stack upgrades

January 6th, 2012

Security improvements related to hashing have been made for these Ruby versions:

• Ruby 1.8.7
• Ruby 1.8.6
• JRuby
• Ruby Enterprise Edition
• Rubinius

In addition, Java has been updated to 1.6u30 to address hashing issues related to CERT–2011–003.

Important! If you use any of the above Ruby versions or Java or Trinidad (which relies on Java), Engine Yard strongly recommends that you update your environments. See Upgrade an environment.

Note: Ruby 1.9.x is not affected.

For detailed information about the security issue, see:

• Our recent blog post
• Denial of service attack was found for Ruby’s Hash algorithm (CVE–2011–4815)
• Vulnerability Note VU#903934
• http://www.nruns.com/_downloads/advisory28122011.pdf

Fix: Engine Yard stack upgrades

January 3rd, 2012

The following fixes have been made to the Engine Yard stack:

• A problem where binary logs were not purged on a database slave with MySQL 5.5
• A problem where snapshots reported failure even though they succeeded

These fixes are applied when you upgrade your environment.