Koozali.org: home of the SME Server
Obsolete Releases => SME 8.x Contribs => Topic started by: Jazza on November 01, 2012, 10:30:34 AM
-
I run a MyBB forum on SME Server 8. When a thread has too many characters, when you try to access the thread, this error occurs:
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
The MyBB support forum has NO answer and NOTHING exists on Google (I've spent hours searching). I've also spent a lot of time searching for how to enable logging MySQL queries on SME server. I believe there is some kind of memory limit that I'm hitting.
There are NO errors in the "messages" log file in the SME server manager.
Can anyone please shed any light on this? Thank you.
-
Take a look at:
/var/log/httpd/error_log
/var/log/httpd/access_log
<any custom log created by MyBB>
-
are you using Chrome?
https://www.google.it/search?client=ubuntu&channel=fs&q=net%3A%3AERR_EMPTY_RESPONSE&ie=utf-8&oe=utf-8&redir_esc=&ei=b-ySUIPCCYjMswaItoCQBw (https://www.google.it/search?client=ubuntu&channel=fs&q=net%3A%3AERR_EMPTY_RESPONSE&ie=utf-8&oe=utf-8&redir_esc=&ei=b-ySUIPCCYjMswaItoCQBw)
-
MyBB forum is not a standard package - it is not included in SME8 ISO. Moving to Contribs section.
-
Take a look at:
/var/log/httpd/error_log
/var/log/httpd/access_log
<any custom log created by MyBB>
Thanks. I've found the following error whenever I refresh the page:
[notice] child pid 14898 exit signal Segmentation fault (11)
are you using Chrome?
https://www.google.it/search?client=ubuntu&channel=fs&q=net%3A%3AERR_EMPTY_RESPONSE&ie=utf-8&oe=utf-8&redir_esc=&ei=b-ySUIPCCYjMswaItoCQBw (https://www.google.it/search?client=ubuntu&channel=fs&q=net%3A%3AERR_EMPTY_RESPONSE&ie=utf-8&oe=utf-8&redir_esc=&ei=b-ySUIPCCYjMswaItoCQBw)
Yep Chrome is my primary browser, however it's been tested on other browsers and the result is the same. Not to mention I clear my cache every couple of days anyway (I'm a web developer).
MyBB forum is not a standard package - it is not included in SME8 ISO. Moving to Contribs section.
Okay well I've recently installed MediaWiki on the server so I'll test the wiki to see if it's a third party bug or a core bug. Hopefully the error I said earlier in this post will save me that time.
-
Okay well I've recently installed MediaWiki on the server so I'll test the wiki to see if it's a third party bug or a core bug. Hopefully the error I said earlier in this post will save me that time.
If you have evidence of a core bug, please open a ticket in Bugzilla.
Thanks.
-
Bump! Anyone help with that error I found?
-
Jazza
Some of the "NOTHING" google search results refer to incompatible modules (or wrong versions) installed for web apps.
Have you looked at that aspect or tried removing any add on modules for MyBB ?
Did you have any issues with MediaWiki ?
-
[notice] child pid 14898 exit signal Segmentation fault (11)
Can you discover what pid 14898 is? If you knew which program this was, you might be able to do some more directed googling...
Have you tried running the memory test on the SME install CD for 2 - 4 hours, or cloning your server to completely different hardware, in order to eliminate hardware as a possible source of the problem?
-
"Segmentation fault" means one of two things: a hardware problem (e.g. memory error) or a bug in a program. You should boot from the SME server CD and perform a memory test. Check your power supply and any cooling fans.
If it's a bug, it's most likely in PHP.
-
>>Segmentation fault (11)
Try your issue without ClamAV?
A long time ago (SME6?) that used to pop up.
ClamAV's issue went away eventually but I do
remember that the above was its fail code.
YMMV
-
Well. I've found the issue. I went through the forum functions to nut out where the error is and eventually found it in the message parser. It's trying to preg_replace with bad regex (or something). I disabled the regex in question and it worked.
I apologise for not giving more specific details about this. I'm just an apprentice to the actual sysadmin who's too busy to look into this. Thank you everyone for your help.
-
So it's a bug in PHP (although they point the finger at the pcre library):
https://bugs.php.net/bug.php?id=47376