RHSA-2013:1136

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)

Before applying this update, make sure all previously released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258 Manual action is required for this update to take effect. In order for the updated passenger packages to be loaded by Ruby applications in the PaaS, the applications must be restarted with oo-admin-ctl-gears. One way to accomplish this is by running the following command, as a single line without the line break, on all OpenShift Nodes: for rubyapp in `ls -d /var/lib/openshift/*/ruby | cut -f5 -d/`; do oo-admin-ctl-gears restartgear $rubyapp; done If there are no Ruby applications on a Node it will simply fail with the message "No such file or directory". Another option is to run the following on all OpenShift Nodes; however, it will result in non-Ruby applications also being restarted: oo-admin-ctl-gears restartall (Note that without the manual action, if a user attempts to restart their Ruby application via the rhc command line, it will fail to start with a "Passenger could not be initialized..." error.)