Engine Yard Developer Center

Engine Yard Release Notes- February 2016

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)

Engine Yard Release Notes for February 25th, 2016

Hotfix: Engine Yard Gentoo 12.11 stack upgrade

Action: We recommend you test this hotfix in your staging environment as soon as possible; then, when that is validated, click the Upgrade button for your production 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:

stack_stable-v4.png

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

  • Update to glibc to resolve vulnerability (CVE-2015-7547)
  • NOTE: For this to take effect, you will need to restart processes that are still using the old version. The easiest way is to reboot your instances, if you can handle a short period of downtime. Please follow the instructions here to complete the changes:
    • Wait for Upgrade to complete
    • Schedule a time where a short duration of downtime can be tolerated
    • Log into each instance and reboot: sudo shutdown -r now
    • Wait for the instance to reboot and confirm your app is working
    • If there are any issues after the reboot, click apply and re-deploy your app
    • Open a support ticket if you need further assistance
  • If you are sensitive to downtime, you can manually restart the processes listed in /tmp/processes_using_deleted_libraries on each instance, but this is only recommended if you are very familiar with Gentoo Linux.

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

 

Engine Yard Stack Release Notes for February 17th, 2016

Minor: Engine Yard Gentoo 2009 stack upgrade

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

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

stack_stable-v2.png

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

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


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:

stack_stable-v4.png

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

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


Engine Yard Release Notes for February 3rd, 2016

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:

stack_stable-v4.png

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

  • Updated timezone data package for recent timezone changes.
  • Added node.js 4.2.1-r1 to GA.
  • Updated PHP to use newer OpenSSL.

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

Minor: Engine Yard Gentoo 2009 stack upgrade

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

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

stack_stable-v2.png

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

  • Updated timezone data package for recent timezone changes.

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


If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.

Powered by Zendesk