ModSec POSIX Error?

Portal Home > Knowledgebase > Articles Database > ModSec POSIX Error?

Posted by fshagan, 12-28-2011, 10:34 AM
After updating EasyApache to the new version, I had a problem with Apache not starting. Mike at MDDHosting straightened that out, and there's no problem as long as mod_security is not running with any rules (i.e., "no configuration"). However, I get this error message when trying to use the "Default configuration" (the cPanel rules): I checked, and even recompiled using EasyApache, and POSIX is selected and built. Any ideas?
Posted by fshagan, 12-28-2011, 12:27 PM
Well, I didn't figure out why the default cPanel rules wouldn't work, but could get the GotRoot rules to work using PuntaPirate's simplified instructions here: http://puntapirata.com/How-to-Install-ModSec-Rules.php Apache is taking quite a bit more memory now, so I'll need to tune some things!
Posted by TenqHosting, 12-28-2011, 09:06 PM
I get the above error when I try to restart httpd using WHM. Can anyone help me please ?
Posted by fshagan, 12-28-2011, 09:24 PM
Any other error message, such as a problem with modsec2.user.conf? Rename that file to something like modsec2.user.conf.bak if so ("mv modsec2.user.conf modsec2.user.conf.bak") and try restarting Apache (Mike at MDDHosting solved my initial problem with Apache refusing to start that way).
Posted by TenqHosting, 12-28-2011, 09:35 PM
Thanks , but I have got this error : What I have to do ? My sites are offline. I need your help right now. Thanks in special.
Posted by fshagan, 12-28-2011, 09:46 PM
If they were online before, rename modsec2.user.conf.bak back to modsec2.user.conf and restart Apache. If they were offline before, can you still access WHM? If you can, disable mod_security (go to WHM > Plugins > Mod_Security, click the "Edit Config" button and then click the "No Configuration" link and ... most importantly ... scroll down and click the "Save" button). If the plugin isn't enabled yet, in WHM go to Cpanel > Plugins > Mod-security and enable it.
Posted by TenqHosting, 12-29-2011, 02:27 AM
Hi , Special Thanks to "fshaghan" :x I just rebuilded easyapache and the problem solved.
Posted by fshagan, 12-29-2011, 10:34 AM
Not sure I deserve the thanks; your solution was probably easier than mine!
Posted by MikeDVB, 12-29-2011, 04:03 PM
It's all fairly simple if you have the right error message to go off of . Now figuring out why your rules that did seem to be working caused issues is another task. When the EasyApache build fails it gives you the option to open a ticket with cPanel - in the future I would suggest doing so and they can look into the error and resolve it if it's a bug or advise you if it's not.
Posted by fshagan, 12-29-2011, 08:03 PM
It did give me that option; I should have availed myself of it. cPanel is usually pretty responsive with support. The Atomic Corp (GotRoot) rules work, but Apache takes too much memory. When the last of my customers are off the server, I'll reduce memory usage by eliminating unnecessary services (using skip-innodb and stopping MailMan, for instance).