CMK version:
2.2.0p29.cre OS version:
Ubuntu 22.04.4
Error message:
[Wed Jul 10 00:00:02.531519 2024] [mpm_prefork:notice] [pid 1232] AH00171: Graceful restart requested, doing restart
apache2: Syntax error on line 126 of /omd/sites/vrf105/etc/apache/apache.conf: Cannot load /omd/sites/vrf105/lib/apache/modules/mod_headers.so into server: /omd/sites/vrf105/lib/apache/modules/mod_headers.so: undefined symbol: ap_set_content_type_ex
Today around 5 from 10 instances from our distributed setup were not available because the apache service was not started anymore. Manually starting the services with âomd start SITEâ worked without further error.
Iâve checked every instance and all throw the same error message in $SITE/var/log/apache/error.log . Could this be a bug in this version?
Updates installed today, now over 50 instances are not accessible via https on my side, however the Monitoring core still runs and Monitoring is working on the customer site.
Basically logrotate will only do a reload and with the update changing that function in mod_headers it fails.
A good long-term fix could be to do a graceful restart instead. (-k graceful or something like that)
Note you have to check that your âapachectlâ doesnât point at the systemd wrapper, because they left out the feature.
Hi All. Do we have a permanent âFixâ yet for this issue? I realise that manually running a âsudo omd startâ on all our VMs / Servers gets things running again, but would like to know the issue is âfixedâ and not coming back âŠ
Same issue on our customer sites, there was an update of apache2 from 2.4.51-35.51.1 to 2.4.51-35.54.1 the day before and all apache on omd stopped working at midnight.
Why is not starting by themself if it goes down?
It did happen this weekend with check-mk-enterprise-2.2.0p29-sles12sp5-38.x86_64 on a sles12sp5.
Is there a solution for a guaranteed availabilty?
[Sat Jul 20 00:00:02.057148 2024] [mpm_prefork:notice] [pid 26230] AH00171: Graceful restart requested, doing restart
httpd2-prefork: Syntax error on line 126 of /omd/sites/âŠ/etc/apache/apache.conf: Cannot load /omd/sites/âŠ/lib/apache/modules/mod_headers.so into server: /omd/sites/âŠ/lib/apache/modules/mod_headers.so: undefined symbol: ap_set_content_type_ex
Looks like this problem is related to httpd bynaries compatibility issues. Do you use any httpd docker image and based on that install any other httpd module using apt? If so, httpd docker image has its own bynaries manually installed. And when trying to install a httpd module using apt, it will install apache2-bin package (which is already installed in another version, but apt donât know that). Because of that, the system will mix httpd bynaries of different versions, leading to error like that.
Today, I encountered the same issue on OEL 9.4 (CEE 2.2p20) and Rocky Linux 8.10 (RAW 2.3p12) after applying the latest Linux patches. Interestingly, the problem occurred at midnight when checkmk checks the Apache configuration using the command /usr/sbin/httpd -f /omd/sites/SITE_NAME/etc/apache/apache.conf:
httpd: Syntax error on line 236 of /omd/sites/SITE_NAME/etc/apache/apache.conf: Syntax error on line 2 of /omd/sites/SITE_NAME/etc/apache/conf.d/01_wsgi.conf: Cannot load /omd/sites/SITE_NAME/lib/apache/modules/mod_wsgi.so into server: libpython3.12.so.1.0: cannot open shared object file: No such file or directory
The solution was to install the newer Python libraries, for example, by running dnf install python3.12-libs. After this, the command /usr/sbin/httpd -f /omd/sites/SITE_NAME/etc/apache/apache.conf executed without any problems.