Apache Full of Reading Request | 0 idle workers

Chirag Aggarwal

• January 19, 2018 07:02

Hello, Since few days, there have been multiple downtimes due to no idle worker left for Apache Current Max Workers are 150 which worked fine before 150 requests currently being processed, 0 idle workers RRRRRRRRRRRRRRRRWKRRRRRRRRRRRRKRRKRKRKRRRRRRRRRRRRWRRRRRRKRRRRRR RRRRKRRRRRRRRRKRCRRRRRKRRRRKCWRRRRKRRKRCRRRRRWKRKRRRRKWRRRRRRRRR RRRRRRRWRRRKRRRRRRWRRR
This seems to be Slow HTTP attack which no method has worked for me. I'd appreciate some suggestions regarding it.

• 

  Chirag Aggarwal

  • January 19, 2018 13:12

  It turned out to be Modsecurity issue, no downtime after temporarily disabling it

  0
• 

  Tearabite

  • January 19, 2018 13:38

  Can you give a little more info on how you fixed this? We occasionally have this same issue and also use Mod_Security.

  0
• 

  cPanelMichael

  • January 19, 2018 17:01

  It turned out to be Modsecurity issue, no downtime after temporarily disabling it

  
  Hello, Would you mind sharing some more information about the particular issue with ModSecurity? Thank you.

  0
• 

  Chirag Aggarwal

  • January 20, 2018 06:37

  Hello, Would you mind sharing some more information about the particular issue with ModSecurity? Thank you.

  
  Hello, There were multiple hits on Modsec on multiple websites which was higher than before. It could have been an attack but to experiment, disabling ModSecurity worked for me. My assumption includes that possibly misconfiguration was causing many requests to not get through neither return any response. But I am still not clear of it. I'm still monitoring it if there's anything else bugging.

  0
• 

  Tearabite

  • January 20, 2018 13:27

  a DNSBL lookup rule in Mod_Security would cause this if the DNSBL is down/responding slowly.

  0

Please sign in to leave a comment.