We would like to apologize for problems with Wikidot sites that all our users experienced earlier today. The problem persisted from about 06:34 to 07:24 UTC. It is now solved. There was no data loss.
Problem started at 06:34 when database engine (PostgreSQL) tried to acquire another segment of shared memory (SHM) from Linux kernel1. Kernel was not able to allocate it because it reached the limit set for this kind of memory. This resulted in database stopping serving data and other processes not being able to request SHM. This caused the server not reachable in usual ways (like SSH shells), so we had to reboot it remotely.
A few moments later (when the machine booted up) we discovered what the problem was, raised the limits for SHM memory, started database and checked its integrity. When we verified no damage was done to users data at 07:24 we enabled the access to the database and Wikidot started to work again.
I was sleeping ;-) thanks for the update
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
Shane… it was around 5 o'clock EST in the afternoon yesterday.
Kenneth Tsang (@jxeeno)
Kenneth, Wikidot was down, so Shane decided to take a nap. Perfectly logical.
Piotr Gabryjeluk
visit my blog
Gabrys has it right! ;-)
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
me too …im glad nothing messed up tho because ive been working so hard on my site
CEO of Icon Deposit
Take a look at me via Twitter, Dribbble, and Google +
Good job on fixing it. It sounds to me like this can/will happen again. So, can it?
graphmastur: shouldn't happen again unless the database volume unexpectedly grows 1000 times (but this will trigger no-more-disk-space error first).
Piotr Gabryjeluk
visit my blog
Did we just have another drop-out at around 15:00 GMT? It was really slow with many failures and CSS not being loaded. A problem on wdfiles?