Out of innodes because of mod_security

wanted4life

• May 25, 2015 05:32

If you ever encounted a problem with your server that you can't access webpages or login to cpanel/whm because of a 500 error, and you can't restart servicess because an error that its saying that you ran out of space... well this is because you ran out of free innodes. So you still have space, but you don't have space for innodes. What you should do is to go on /usr/local/apache/logs/modsec_audit/ and remove all the files. This problem appears because mod_security create so many empty files. HOW DO WE FIX THIS? How can we stop mod_security to keep creating these fils, but to keep the server secure?

• 

  wanted4life

  • May 25, 2015 10:36

  I went in whm at modsecurity configuration and selected "Do not log any transactions". and this appears to fix it. So to fix this, do that and you are good to go.

  0
• 

  madmanmachines

  • May 26, 2015 12:25

  If you ever encounted a problem with your server that you can't access webpages or login to cpanel/whm because of a 500 error, and you can't restart servicess because an error that its saying that you ran out of space... well this is because you ran out of free innodes. So you still have space, but you don't have space for innodes. What you should do is to go on /usr/local/apache/logs/modsec_audit/ and remove all the files. This problem appears because mod_security create so many empty files. HOW DO WE FIX THIS? How can we stop mod_security to keep creating these fils, but to keep the server secure?

  
  See case 169157:

  0
• 

  cPanelMichael

  • May 27, 2015 13:40

  Hello, Please keep in mind that 500 error messages don't always indicate a lack of available inodes. That being said, this is addressed in cPanel version 11.50 as mentioned in the previous post: Fixed case 169157: Rotate ModSecurity logs. Thank you.

  0

Please sign in to leave a comment.