News for hackers. Stuff that matters.

tmornini

Re:A Sad Day (Layoffs in Engine Yard's Rubinius team) on Thursday November 20, 2008 @01:10AM (#370387)
Thanks for understanding, luckystrike.

I was the one that asked Ezra to keep an eye on Evan and Rubinius after RubyConf 2006. We really felt that the community would benefit from an industrial strength Ruby runtime, and still feel that way today.

We hired Evan more than 6 months before we received venture funding.

When we received our series A funding, we hired the best team we could get our hands on and hoped to push Rubinius through to 1.0, which we define as no apologies MRI parity, as quickly as possible.

Things are good here at Engine Yard. We have a growing customer base, and very interesting new products in the pipeline. As with all other business in these times, sharpening the budget just makes very good sense.

We did what we felt we must do to make certain we could continue funding Rubinius through to completion.

Re: Engine Yard experiencing serious downtimes on Sunday August 17, 2008 @01:04PM (#278450)
Hello there. Thought I'd follow up as we have some additional news from our vendor.

The fact that this "should not have happened" doesn't help our customers out, and doesn't make us feel particularly better about the incident we had on Friday.

Just one of our six clusters was affected, but it was a bad day for customers on that cluster, and for that I personally apologize to them.

We're working hard to make sure that this issue is entirely resolved on this, and our other clusters as well, providing Extreme with the core dumps they've requested.

Details below:

----------------------------------------------------------------------------------------------------------------------------

08/16/2008 03:53:58.16 <Noti:EPM.wd_warm_reset> Slot-1: Changing to watchdog warm reset mode

08/16/2008 03:09:42.05 <Warn:DM.Warning> Slot-2: Slot-3 FAILED (2) Error on Slot-3

08/16/2008 03:09:38.62 <Warn:DM.Warning> Slot-2: Slot-3 FAILED (1) Error on Slot-3

08/16/2008 03:09:29.23 <Warn:DM.Warning> Slot-1: Slot-3 FAILED (2) Conduit receive error encountered

08/16/2008 03:09:25.17 <Warn:DM.Warning> Slot-1: Slot-3 FAILED (1) Conduit receive error encountered

08/16/2008 03:09:25.17 <Warn:DM.Warning> Slot-1: System Error 0: Conduit receive error encountered

08/16/2008 03:08:22.29 <Warn:DM.Warning> Slot-1: Slot-4 FAILED (1)

08/16/2008 03:08:02.94 <Warn:DM.Warning> Slot-1: Slot-4 FAILED (1)

----------------------------------------------------------------------------------------------------------------------------

The above warning messages are caused by “System memory depletion” and “watchdog timer” triggered “restarting slot 3 and 4. After crashed, slot 3 and 4 created “core dump file”. We need that files for detail investigation.