Skip to content
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

Closed
JeroenDeDauw opened this issue Jun 22, 2016 · 8 comments
Closed

Wiki extremely slow #1687

JeroenDeDauw opened this issue Jun 22, 2016 · 8 comments

Comments

@JeroenDeDauw
Copy link
Member

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.

@kghbln
Copy link
Member

kghbln commented Jun 23, 2016

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.

@kghbln
Copy link
Member

kghbln commented Jun 23, 2016

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.

@JeroenDeDauw
Copy link
Member Author

Indeed this is a flooding attack by IP 62.210.78.104.

flood

The server load is currently at 60 while an acceptable max is at about 3 for the two cores we have.

How do you figure 3 is the max, and how can I see the load when I ssh into the box?

@kghbln
Copy link
Member

kghbln commented Jun 23, 2016

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 top when being on the sever which will also show you other data too.

@kghbln
Copy link
Member

kghbln commented Jun 23, 2016

Things like this one should go to this place in the future.

@kghbln
Copy link
Member

kghbln commented Jun 23, 2016

Always trouble with the tribbels, however it seems to be over.

@kghbln kghbln closed this as completed Jun 23, 2016
@mwjames
Copy link
Contributor

mwjames commented Jun 23, 2016

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?

@kghbln
Copy link
Member

kghbln commented Jun 23, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants