Hi,
we experience an error upgrading our site to the newer version 2.0.
When we upgrade it, the site simply doesn’t work - WATO error, Services error, no possibility to take action or to modify it.
Anyone had these kind of problems?
Which logs do you need?
Yes, we upgrade from 1.6p30 to 2.0 last version.
After the upgrade, we have “[Error running automation call try-inventory (exit code 1)]” in every services and every host.
If we create a new site, no errors at all.
We resolve the error present in the /omd/sites/infonet/etc/check_mk/conf.d/wato/ and then we update the site successfully.
After a reboot of the server, the httpd crash and we are unable to start it again.
The error is this:
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since ven 2022-11-11 09:53:31 CET; 32s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 9469 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 9469 (code=exited, status=1/FAILURE)
nov 11 09:53:31 checkmk-tst systemd[1]: Starting The Apache HTTP Server…
nov 11 09:53:31 checkmk-tst httpd[9469]: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 15 of /etc/httpd/conf.d/zzz_omd.conf: Syntax error on line 1 o…e or directory
nov 11 09:53:31 checkmk-tst systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
nov 11 09:53:31 checkmk-tst systemd[1]: Failed to start The Apache HTTP Server.
nov 11 09:53:31 checkmk-tst systemd[1]: Unit httpd.service entered failed state.
nov 11 09:53:31 checkmk-tst systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
on the Syntax error on line 15 of /etc/httpd/conf.d/zzz_omd.conf we have this output:
<IfModule !mod_authz_core.c>
# Apache < 2.4
Include /omd/apache/*.conf
We upgrade the apache config via omd update-apache-config and then after the restart the apache.service is unable to start it up (service degraded) and of course the web interface is unreachable.
How we can resolve it?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.