Apache 404 "requested URL not found" after release Upgrade

Troubleshooting
1

CMK version:
2.2.0p26
OS version:
Ubuntu 22.04 (was 20.04)
Error message:
The requested URL was not found on this server.

After a Ubuntu release upgrade from 20.04 to 22.04 following this document: Linux-Upgrade auf dem Checkmk-Server we do get the above error message when accessing the site in browser.

Before doing this upgrade on our physical checkmk server we did the same upgrade in a VM with a copy of the machine. We did not have any issue in the test VM.

The site seems to be working, checks are executed and mails are sent.

omd status
Doing ‘status’ on site xyz:
agent-receiver: running
mkeventd: running
liveproxyd: running
mknotifyd: running
rrdcached: running
cmc: running
apache: running
dcd: running
redis: running
crontab: running
Overall state: running

There are no errors in apache error.log. in access log there is a 404 line for every access.

The apache default page is shown when accessing /

We accept unencrypted access on port 80, so SSL config error can be excluded.

Any ideas what to check or what to do?

Martin

2

that upgrade path never worked for me. (presumably my error(s))
I usually create a site backup, remove all omd components, perform os upgrade, reinstall omd and restore site.

3

Hi Martin,

i had a similar issue where all the apache configuration was deleted inside the the apache configuration folders.

Can you check, if the file zzz_omd.conf is present in /etc/apache2/conf-enabled ?

4

Hi.

Did you restart the apache2 service on the system after update?

Rg, christian

5

as mentioned no problems in virtual copy of the machine.
On physical we had a small issue with the network cards being renamed, so we had to renew the ip configuration.

I must confess i am not a linux expert, but for me it looks like everything is working fine, except the site in apache.

I did a complete site backup before the upgrade, but would like to keep the complete server install and site recovery as a last solution if we cannot get it to work otherwise.

6

I have done this successfully at least 20/30 times starting from Ubuntu 14.04 to 22.04.

7

we did restart the whole system after realease upgrade.
Then renewed IP configuration and restarted system again. Then we reinstalled checkmk and ran into the problem described.

8

That was the problem.
I don’t know how often i checked all apache files, but somehow i did not see this conf being disabled.

Thanks a lot.

2 Likes
9

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.