I retested today, and the medium app server shared role is still using 2.6.16-xenU,
The problem is supposedly resolved by upgrading the kernel to 2.6.18 or higher. ( The original post said our instance was running 2.6.18, which wasn't accurate. We were running 2.6.16, but needed to upgrade to 2.6.18) 2.6.16 works fine on small instances but hangs apache in some strange circumstances on medium instances. We would like to begin using medium instances again, but don't want to risk the apache failure. Can you update the shared role at least? uname -a Linux ops-app-67-202-9-32 2.6.16-xenU #1 SMP Mon May 28 03:41:49 SAST 2007 i686 GNU/Linux On Jul 6, 10:30 pm, "Igor V. Savchenko (DicsyDel)" <[email protected]> wrote: > No, at the moment. We are going to include this feature to the next > release (within the next 4-6 weeks). > > On Jul 6, 9:42 pm, Joel Franusic <[email protected]> wrote: > > > > > Apache stopped working on one of our instances recently, according to > > these links, it would appear that this is due to our instance running > > kernel 2.6.18 on a medium instance: > > >http://solutions.amazonwebservices.com/connect/message.jspa?messageID... > > > This link describes how to manually upgrade the kernel via the aws > > tools: > > >http://www.vincestross.com/2009/04/upgrade-an-ec2-instance-to-2618-fr... > > > Is it possible to upgrade the kernel on our instances via the Scalr > > UI? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
