[01:00:53] Thanks 🥳 [02:23:59] I got everything I wanted to save 🙏 [02:25:08] 🙏 [17:35:05] > An unknown error occurred in storage backend "wikitide-swift". [17:35:08] hhhhhhhhhhhhhhh [17:36:29] @Site Reliability Engineers [17:37:18] Please see #announcements, until the Swift migration there is unfortunately nothing we can do [17:37:31] wrong server \:P [17:37:38] Oh whoops [17:37:43] give it a moment [17:37:43] swiftproxy1 went down [17:37:52] I can't ssh in either. [17:37:58] give it a moment [17:38:45] ah, I see [17:38:52] memcached on swiftproxy1 went down [17:39:03] why does swiftproxy need memcached? [17:39:25] For caching, but it could be a seperate server also. [17:39:58] can't we lump it into mem1? [17:40:28] working in two servers for similar services sure gets confusing huh lol [17:40:38] It would then be able to more easily cause issues on MW like right now instead of only Swift being down everything would be down. [17:41:09] how though? [17:41:18] swiftproxy1 hung because it ran out of RAM [17:41:58] Hmm... it should be configured to use less then, it must be configured to use more than it has. [17:42:10] I hope all the files I just uploaded didn't do that [17:42:19] Hopefully not too much longer, just waiting on the hardware for super-servers to get all set up and tidied. 🙂 [17:44:12] I gave swiftproxy1 10GBs of RAM [21:01:46] [1/2] I'm getting a person who wants to check out the wiki - and is blocked [21:01:46] [2/2] https://cdn.discordapp.com/attachments/1088870295970009221/1198009428230815924/image.webp?ex=65bd5839&is=65aae339&hm=dafc2deaf48e0acc3493ed7c0f3136ee2235c2017a40cb6f552ad962bc3b8259& [21:06:19] Please have them email cvt@wikitide.org or cvt@miraheze.org and provide their preferred username, email and which service they want their account on. [22:36:30] Hmm that screenshot shows a fragment of the old dbname (with the wikitide suffix) [22:37:34] (I.E it didn’t get updated when the suffix was changed) [22:48:28] It won't [22:48:47] I don't think