Description of problem: systemctl start httpd.service fails Sep 10 07:30:07 wb2.home.test httpd[4817]: AH00526: Syntax error on line 132 of /etc/httpd/conf/modsecurity.d/modsecurity_crs_50_o...d.conf: Sep 10 07:30:07 wb2.home.test httpd[4817]: Error parsing actions: Unknown action: \\ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. clean install Mageia-3-alpha1-x86_64-DVD.iso and apply all updates. 2. click up a terminal 3. su - root 4. systemctl start httpd.service 5. systemctl status httpd.service
Blocks: (none) => 6954Assignee: bugsquad => guillomovitch
I can't reproduce the issue: apache starts correctly after installing mod_security and mod_security core rules set.
Status: NEW => UNCONFIRMEDSummary: 3_a1: systemctl start httpd.service fails with Syntax error on line 132 => syntax error in mod_security core rules set default configuration filesEver confirmed: 1 => 0Source RPM: apache-mod_security-crs-2.2.5-1.mga3.src.rpm => apache-mod_security-crs
Changed Summary back to original error text so other people can find this bug so they will not open a duplicate. (In reply to comment #1) > I can't reproduce the issue: I uninstalled apache-mod_security-crs, installed apache-mod_security-crs-2.2.5-1.mga3.noarch.rpm and still get the failure. I changed RPM PACKAGE back to apache-mod_security-crs-2.2.5-1.mga3.src.rpm since that is the src rpm which appears to have the bad /etc/httpd/conf/modsecurity.d/modsecurity_crs_50_outbound.conf file. > apache starts correctly after installing mod_security and mod_security core rules set. I can not find those rpms. This install has all updates applied Sun Sep 16 08:31:18 CDT 2012
Summary: syntax error in mod_security core rules set default configuration files => 3_a1: systemctl start httpd.service fails with Syntax error on line 132Source RPM: apache-mod_security-crs => apache-mod_security-crs-2.2.5-1.mga3.src.rpm
I was finally able to update my virtual box guest and it does not have the problem. I'll wipe my test box and do another clean install and re-open this bug if the problem is still there.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => FIXED