-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wiki extremely slow #1687
Comments
I believe that this was a flooding attack, at least this is what happened to sandbox and the reason why I took it off-line during the night. |
Indeed this is a flooding attack by IP 62.210.78.104. The server load is currently at 60 while an acceptable max is at about 3 for the two cores we have. |
With acceptable max I mean a max which will go unnoticed by the users. It's a rough estimate which may vary, so 4 may still be cool too. Just issue |
Things like this one should go to this place in the future. |
Always trouble with the tribbels, however it seems to be over. |
Would it help to return a custom 404 page instead and let users know that servers are currently unavailable? |
I guess this would make sense in connection with Apache's "mod_reqtimeout". But also adding "mod_qos" and "mod_security" make sense in this connection though these are add-ons which I have to investigate further in the sense of how to handle these best. |
I'm noticing that the SMW wiki is currently extremely slow. Takes over 10 seconds for something to load... not sure what is going on.
The text was updated successfully, but these errors were encountered: