On Sun, 17 Nov 2013, Austin Seipp wrote: > The problem was not DDoS, I think. Our speculation is that it might > have been a software/hardware issue possibly (kernel panic, a total > OOM and grinding to a halt is also possible I suppose.)
My experience is that there are so many moving parts in the haskell.org web environment that testing for failure points is difficult. That said... My suspicion has been that there are a couple web-launched operations that consume massive memory (and perhaps i/o) resources, often enough to bring even well-behaved hardware like abbot to its knees. Speaking of abbot, please keep me in the loop concerning its future. There are some Galois-specific configuration bits I'll want to remove or replace prior to, say, a trip down to the Open Source Lab in Corvallis. -- Paul Heinlein Galois, Inc. Systems Administrator 421 SW Sixth Avenue, Suite 300 [email protected] Portland, Oregon 97204 +1 503 626-6616 x140 http://corp.galois.com/ _______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
