Strange Apache error file missing on httpd start

[verdonv]

Hello,

When httpd starts, I see the following error in my logs

Code: Select all

httpd: Syntax error on line 223 of /etc/apache2/conf/httpd.conf: Syntax error on line 32 of /etc/apache2/conf.d/modsec2.conf: Syntax error on line 55 of /etc/apache2/conf.d/modsec/modsec2.cpanel.conf: Could not open configuration file /etc/apache2/conf.d/modsec_vendor_configs/configserver/00_configserver.conf: No such file or directory

and yet, the file '/etc/apache2/conf.d/modsec_vendor_configs/configserver/00_configserver.conf' is definitely there, owned by root, and chmod 644

Any idea why I am getting that error? Would I be better to ask this at cPanel forums?

Thanks,
v

[johnjohn]

Same problem .. any update on this thread ? Thanks

[verdonv]

I think I tracked this down. If I recall, it was a permission error on /etc/apache2/conf.d/modsec_vendor_configs/configserver/. I think it was set to rwx------ (700) and needed to be set to rwxr-xr-x (755). Have a look and see if that is the case for you.

[bestau]

I got the same issue.
Checked folder permission, all good.
Any idea? Thanks.

[verdonv]

You're right and I was wrong. I thought it was folder permissions, and service httpd configtest reported OK when I made that change, but in the startup log from last night, when httpd failed and restarted on me, I can see the same error there again.

httpd: Syntax error on line 229 of /etc/apache2/conf/httpd.conf: Syntax error on line 32 of /etc/apache2/conf.d/modsec2.conf: Syntax error on line 55 of /etc/apache2/conf.d/modsec/modsec2.cpanel.conf: Could not open configuration file /etc/apache2/conf.d/modsec_vendor_configs/configserver/00_configserver.conf: No such file or directory

[ForumAdmin]

This is nothing to do with cmc.

This is an issue with cPanel's ModSecurity vendor implementation when updating the ConfigServer cxs vendor rules. You need to take the issue up with cPanel as it is their update mechanism that is causing this during upcp, not the cxs rules. I believe that they are aware of the issue, so will hopefully be fixing it.