No, I noticed this (someone mentioned it on IRC earlier). It hasn't come back yet it seems - I'll login and have Hetzner try a reboot of the server. To my knowledge, this is the first time we've had a problem with lambda (so far).
However, on a similar note to the other admins - we should really move community/lambda *now* rather than later; I spent this morning patching CVE-2014-6271 on our existing boxes. But lambda/lun are still an old, outdated nightmare. They need to be decomissioned ASAP. On Wed, Sep 24, 2014 at 4:34 PM, Paul Heinlein <[email protected]> wrote: > Were lambda and lun (aka community, aka code) shut down on purpose? > They are currently unreachable. > > If not, I'll see about spinning them up again. > > -- > Paul Heinlein Galois, Inc. > Systems Administrator 421 SW Sixth Avenue, Suite 300 > [email protected] Portland, Oregon 97204 > +1 503 626-6616 x140 http://galois.com/ > _______________________________________________ > haskell-infrastructure mailing list > [email protected] > http://community.galois.com/mailman/listinfo/haskell-infrastructure -- Regards, Austin - PGP: 4096R/0x91384671 _______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
