If you have tried to edit large wiki pages on BT, you would realize that the server has a tendency to 'eat your edits and split it back out.'
This problem stemmed from the strange interaction between Lighttpd, PHP, and Mediawiki.
Well, guess what, you guys won't see this problem anymore. As a bonus, the server should be a lot faster now.
Weeeeee...
No more 'Mediawiki just ate my edit!' bug
Moderators: thelastguardian, Fringe Security Bureau, Senior Editors, Senior Translators, Alt. Language Translator/Editor, Executive Council, Project Translators, Project Editors
- thelastguardian
- Editor-in-Assistance
- Posts: 187
- Joined: Sun Nov 28, 2004 7:52 pm
- Favourite Light Novel:
-
- Kyonite - The Haruhi Pacifier
- Posts: 165
- Joined: Fri Jan 09, 2009 3:21 am
- Favourite Light Novel:
Re: No more 'Mediawiki just ate my edit!' bug
Can you be a bit more technically detailed? Like what arcane modification have you done to php.ini?
まず隗より始めよ。
- thelastguardian
- Editor-in-Assistance
- Posts: 187
- Joined: Sun Nov 28, 2004 7:52 pm
- Favourite Light Novel:
Re: No more 'Mediawiki just ate my edit!' bug
If I am correct in my guess, when Lighttpd splitted off the php process as fcgi, when the text is too large, for whatever reason the process became stuck. After a while Lighttpd timeout and throws back the 500 error. Of course, the process is still running, so the list of running fcgi threads pile up until Lighttpd/PHP clear them out.
The process only become stuck with codes from Mediawiki- other heavy lifting php pages are fine for some reason.
In other word, I have no idea why this happened.
The process only become stuck with codes from Mediawiki- other heavy lifting php pages are fine for some reason.
In other word, I have no idea why this happened.
- onizuka-gto
- Editor-in-Chief
- Posts: 4840
- Joined: Wed May 10, 2006 9:02 pm
- Favourite Light Novel: Suzumiya Haruhi
Mahouka koukou no Rettousei
No Game No Life
Mushoku Tensei
Mother of Learning - Location: N.E.E.T Federation
- Contact:
Re: No more 'Mediawiki just ate my edit!' bug
....but somehow the "mysterious" solution to this unknown problem fixed all our woes?thelastguardian wrote:If I am correct in my guess, when Lighttpd splitted off the php process as fcgi, when the text is too large....blahblahblahblahbbqsaucelolisteaklmaowtflolblahblahblah...
Well, I'm glad someone knows what they are doing around here......
thelastguardian wrote: ....In other word, I have no idea why this happened.
"Please note, we have added a consequence for failure.Any contact with the chamber floor will result in an unsatisfactory mark on your official test record, followed by death. Good luck."
@Onizukademongto
@Onizukademongto