As an update, the WWW server is severely limited on RAM and the cause of this problem was that the OOM killer hit the database. We're using InnoDB of course, so the crash should be safe. We also noticed that the machine has no swap partition.
I'll be taking new-www and adding RAM and swap to it, hopefully by the end of the night. I'll post to this list for any expected downtimes. I will probably double the RAM first for good measure and add swap after. On Mon, Jul 29, 2013 at 8:07 PM, Austin Seipp <[email protected]> wrote: > This is now fixed. The MySQL instance went down for some reason and I > kicked it. I'll investigate it more. > > On Mon, Jul 29, 2013 at 8:01 PM, Jason Dagit <[email protected]> wrote: >> Hello, >> >> It looks like the haskell wiki is down. >> >> http://www.haskell.org/haskellwiki/Haskell >> >> Gives this page: >> Sorry! This site is experiencing technical difficulties. >> >> Try waiting a few minutes and reloading. >> >> (Can't contact the database server: Can't connect to local MySQL server >> through socket '/var/run/mysqld/mysqld.sock' (2) (localhost)) >> >> You can try searching via Google in the meantime. >> Note that their indexes of our content may be out of date. >> >> >> Any idea what's wrong? >> >> Jason >> >> _______________________________________________ >> haskell-infrastructure mailing list >> [email protected] >> http://community.galois.com/mailman/listinfo/haskell-infrastructure >> > > > > -- > Regards, > Austin - PGP: 4096R/0x91384671 -- Regards, Austin - PGP: 4096R/0x91384671 _______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
