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 Gentoo 2009 stack upgrade
December 19th, 2014
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:
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:
- Resolves issue seen in Chrome browsers (versions before 38) when encountering HTTP status code 408
- Reduces the logging volume of stunnel to error level (previously debug level)
For more information on Engine Yard Gentoo 2009, see the Engine Yard Gentoo 2009 docs.
Minor: Engine Yard Gentoo 12.11 stack upgrade
December 19th, 2014
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:
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:
- Resolves issue seen in Chrome browsers (versions before 38) when encountering HTTP status code 408
- Reduces the logging volume of stunnel to error level (previously debug level)
-
Enables process monitoring for bloated and orphaned workers for Passenger 4
Note:
- By default, the worker size is 250MB, though it can be changed by making a request to support.
- As this monitoring is new for Passenger 4, it is more likely to find bloated or orphaned workers on its first use IF your app has been running a long time and prone to growing in size. This may result in a minor downtime while new workers are created to replace those terminated by the monitor.
- You can first check if your workers are over this threshold using
passenger-memory-statscommand on each app instance (this includes app_master and solo instances), and if so, you can preemptively restart your app, select a low-traffic time to perform your upgrade, or open a support ticket to increase your worker size (only recommended if your app is always larger than 250MB but not constantly growing).
For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.
Hotfix: Engine Yard Gentoo 2009 stack upgrade
December 12th, 2014
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 2009" 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 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:
- Address the error that is seen when clicking Apply after upgrading to the 2014-Dec-11 stack release
Minor: Engine Yard Gentoo 2009 stack upgrade
December 11th, 2014
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:
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:
- Replaces mini_httpd with nginx for serving instance metric graphs to the dashboard
- Ensures database backup cron task gets moved to another db replica (or master if no replica) when PostgreSQL replica containing the task is removed.
For more information on Engine Yard Gentoo 2009, see the Engine Yard Gentoo 2009 docs.
Minor: Engine Yard Gentoo 12.11 stack upgrade
December 11th, 2014
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:
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:
- Minor reduction in time taken when running chef (initial provisioning and when clicking Apply or Upgrade)
- Ensures database backup cron task gets moved to another db replica (or master if no replica) when PostgreSQL replica containing the task is removed.
For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.
Minor: Engine Yard Gentoo 2009 stack upgrade
December 2nd, 2014
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:
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:
- Bump MySQL 5.5 package to version 5.5.40
- Bump MySQL 5.6 package to version 5.6.21
- Backups and snapshots are now staggered, instead of occurring at the top of the hour they're scheduled to take place. They will occur at the same frequency, but may be done at a slightly different time. This helps Engine Yard to assure snapshots and backups all successfully occur without overloading our systems at the same time for all customers. You can see the time(s) your backups and snapshots occur by running
sudo crontab -lon your instances.
For more information on Engine Yard Gentoo 2009, see the Engine Yard Gentoo 2009 docs.
Minor: Engine Yard Gentoo 12.11 stack upgrade
December 2nd, 2014
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:
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:
- Bump MySQL 5.5 package to version 5.5.40
- Bump MySQL 5.6 package to version 5.6.21
- Backups and snapshots are now staggered, instead of occurring at the top of the hour they're scheduled to take place. They will occur at the same frequency, but may be done at a slightly different time. This helps Engine Yard to assure snapshots and backups all successfully occur without overloading our systems at the same time for all customers. You can see the time(s) your backups and snapshots occur by running
sudo crontab -lon your instances. - Resolved the non-fatal FastCGI error that shows up in log file when not using New Relic Add-on with PHP environments
For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 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.
Comments
Article is closed for comments.