Talk:Strange World Amnesia

can someone on the backend tell me what happened (;´Д`) --Agb001 (talk) 14:15, 3 December 2025 (UTC)

It was discussed in DevChat@Heyuri when it happened (read from bottom to top):

★ hachikuji◆naRqMpZoTs > since we've been updating koko a lot over the past week or so i was worried something slipped through and got so fucked it'd write +100GB of error logs (＾_＾；) (2025/11/30-17:58:38)
★ kuz◆AMERICAu.c > There's alot of things wrong with this server, its dusty and alot of things are broken on it, alot of old software, bad configs from 5 years ago that i've copied and pasted over and over again (2025/11/30-17:58:31)
★ anonwaha◆bGTvsQ3YBE > the errors i mean (2025/11/30-17:57:37)
★ anonwaha◆bGTvsQ3YBE > well, with nothing else changed it'll probably happen again (2025/11/30-17:57:26)
★ kuz◆AMERICAu.c > but that shouldnt have anything to do with this... (2025/11/30-17:57:07)
★ kuz◆AMERICAu.c > In full disclosure, about 20 minutes prior to this incident I did update our firewall rules to block two ports that were accidentally left open (2025/11/30-17:56:52)
★ kaguya◆V4Zyo2onG6 > yeah, even if it's on another partition or linux is curbing old lines, it would just keep writing such janku (2025/11/30-17:56:42)
★ kuz◆AMERICAu.c > But the log file with the errors in it is now lost (2025/11/30-17:56:11)
★ kaguya◆V4Zyo2onG6 > if therez a cure, just applying that would be nice but teh cause of such a huge sudden writeup is moar of an issue ^^; (2025/11/30-17:55:59)
★ kuz◆AMERICAu.c > I'd like to know what it was getting so hot and heavy about in the first place (2025/11/30-17:55:50)
★ anonwaha◆bGTvsQ3YBE > it seems crazy that it can just keep growing until the disk runs out of space (2025/11/30-17:55:47)
★ anonwaha◆bGTvsQ3YBE > is there anything that can be configured to cure nginx's error log inflation fetish? (2025/11/30-17:54:56)
★ anonwaha◆bGTvsQ3YBE > naisu (2025/11/30-17:53:31)
★ kuz◆AMERICAu.c > When we do the server renovation™ the /var will be on a seperate partition so that bloated logs do not cause issues (2025/11/30-17:52:03)
★ kuz◆AMERICAu.c > Well at least everyone can read my poem (2025/11/30-17:46:07)
★ kaguya◆V4Zyo2onG6 > i fixed that too but something I did failed to update, I'll redo while it's read-only (2025/11/30-17:45:21)
★ kaguya◆V4Zyo2onG6 > (not sw) (2025/11/30-17:44:47)
★ kaguya◆V4Zyo2onG6 > fixed (2025/11/30-17:44:44)
★ kaguya◆V4Zyo2onG6 > i am just restoring posts to start by 18978 instead of 1 (2025/11/30-17:40:03)
★ kuz◆AMERICAu.c > I just told kaguya that (2025/11/30-17:37:43)
★ kuz◆AMERICAu.c > I wont (2025/11/30-17:37:40)
★ kuz◆AMERICAu.c > ( ´ω`) (2025/11/30-17:37:31)
★ anonwaha◆bGTvsQ3YBE > the strange world logs use weird line endings, so plz don't throw anything away just cuz it sems a little b0rked (2025/11/30-17:37:12)
★ hachikuji◆naRqMpZoTs > :depression: (2025/11/30-17:36:06)
★ anonwaha◆bGTvsQ3YBE > :dark: (2025/11/30-17:35:31)
★ kuz◆AMERICAu.c > what about strange world? < its flatfile.. so it probably corrupted when trying to write to the file (2025/11/30-17:35:11)
★ hachikuji◆naRqMpZoTs > white page again, error log still exploding? (2025/11/30-17:34:50)
★ kaguya◆V4Zyo2onG6 > i'll change its directory for a second (2025/11/30-17:33:42)
★ kaguya◆V4Zyo2onG6 > I need to know last post's ID though (2025/11/30-17:33:12)
★ kaguya◆V4Zyo2onG6 > https://dis.heyuri.net/sw/bbs.php?c=08&m=g&f=202511.dat exists (2025/11/30-17:33:02)
★ hachikuji◆naRqMpZoTs > what about strange world? (2025/11/30-17:30:36)
★ kuz◆AMERICAu.c > so all i could see was corrupted data before kaguya deleted the file (2025/11/30-17:26:54)
★ kuz◆AMERICAu.c > the process was still trying to write whenever the disk ran out of space and it seems it corrupted the log itself (2025/11/30-17:26:38)
★ hachikuji◆naRqMpZoTs > ah alright (2025/11/30-17:26:37)
★ kuz◆AMERICAu.c > who knows what it was related to (2025/11/30-17:26:17)
★ kuz◆AMERICAu.c > which is also the php error log (2025/11/30-17:26:10)
★ kuz◆AMERICAu.c > it was the nginx error.log (2025/11/30-17:26:05)
★ hachikuji◆naRqMpZoTs > error aside, its been suggested before but we should definitely have some a line limit for error.log (if this was caused by the koko one, that is) (2025/11/30-17:23:59)
★ hachikuji◆naRqMpZoTs > wtf (2025/11/30-17:23:06)
★ kuz◆AMERICAu.c > caused by a 120gb+ error log file that ballooned out of nowhere (2025/11/30-17:22:17)
★ kuz◆AMERICAu.c > the disk was at 100% capacity (2025/11/30-17:21:46)
★ kuz◆AMERICAu.c > test (2025/11/30-17:21:36)
★ hachikuji◆naRqMpZoTs > viewing the live index gave an error, then started giving white pages. strange world seems to be effected too (2025/11/30-17:12:37)
★ kaguya◆V4Zyo2onG6 > I don't know what b0rk while I didn't do something, checking (2025/11/30-17:11:40)
★ hachikuji◆naRqMpZoTs > i get an error when trying to access the live frontend or rebuild (2025/11/30-16:51:48)

TL;DR: the server error log bloated up to 120+ GB (cause: unknown) which used up all the disk space, causing any files being written to get corrupted. --Anonwaha (talk) 23:51, 3 December 2025 (UTC)

---

>In reality all that happened is that the message logs dating back to 2022 were lost
The message log file (which was the one that got purged) only stores the last 5000 posts
It was always saving messages permanently to "Message Logs" files which are grouped monthly, and they are untouched & operational. 5000-posts file is like a "cache" used to display posts on front end --Kaguya (talk) 16:16, 5 December 2025 (UTC)