Using a browser to go there I got a message telling that it is not allowed to read the page.
I have also some other directories, one of them
Alias /milweb/ "/home/henk/milweb/"
<Directory "/home/henk/milweb">
...
Those were (and are) readable and shown by the browser.
Investigation in srv/www/htdocs showed that index.html was renamed index.html.rpmnew and the r-bit for group and others were removed. Reversing this made everything working again as expected.
As I understand it during a package update a file that is due to be overwritten can be kept and the new file is created with th same name and the suffix .rpmnew added. But in this case index.html was not kept, but renamed (the contents was OK) and r-bits removed.
BTW the same was done to favicon.ico.
It is repaired now, but I wonder if some bug report would be applicable or if I am wrong here in my assessment. Anybody experiencing the same or similar.
boven:~ # zypper se -f /srv/www/htdocs/index.html
Loading repository data...
Reading installed packages...
No matching items found.
Note: For an extended search including not yet activated remote resources please use 'zypper
search-packages'.
boven:~ # zypper se -f /srv/www/htdocs
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+------------+-----------------------------------------------+--------
i | filesystem | Basic Directory Layout | package
i | info2html | Program to Convert Info Pages into HTML Pages | package
| nextcloud | File hosting service | package
Note: For an extended search including not yet activated remote resources please use 'zypper
search-packages'.
boven:~ #
So it does not seem to be installed at all, but created by the web manager long ago.
That does not make it better understood by me why this upgrade touched it.
There is simply not enough information to guess. The file /etc/www/htdocs/index.html was likely provided by some package before upgrade and so was removed during upgrade. The .rpmnew file may have been there for a long time, you did not show timestamp. There is no evidence that this file has been created during upgrade.
That is partly because the very upgrade destroyed a lot of evidence.
The file index.html definitely contains itâs contents since at least 2019-03-01 as the list from the backup (the backup is from 2024-10-22) shows. As I am also the web master, I am pretty sure that I created that file myself and I did not change it for years (it may even be older, but 2019-03-01 may be the date of a fresh installation).
And BTW, that contents is still unchanged (see the sizes of the file in Post #1 and the size in the backup). Thus it was NOT removed and a new .rpmnew file with a new contents created. mv the file to the correct name and setting r-permission restored the web siteâs functionality.
The .rpmfile is NOT in the backup. I can of course fire up the backup system again and post a complete ls -l of the backed up /srv/www/htdocs directory, but I did it this morning (when I copied/pasted the ls -l index.html of post #4).
Of course I can not prove it and you have to take my word (or not ) that thew web site functioned until the upgrade. The upgrade itself took me less then an hour. After that, testing if all things were OK, I found this.
And I agree that there probably is not enough information to guess what happened. That is why I posted here. Maybe others are smarter then I am.
Do you really have a Leap 15.5 with LAMP running that you upgraded using the online method to 15.6?
I doubt very much. The system is now upgraded 15.5 > 15.6 (what produced the problem). I do not think it is easy to revert the system to the 15.5 situation. In other words, downgrading is not supported. And I have no other 15.5 system with a running Apache.
I have one other system that I upgraded a few weeks ago, but it hasnât a LAMP sever and /srv/www/htdocs is empty there.
But I either do not understand you, or you misread what is the problem.
The problem is NOT that on installation of Apache (which was done by me many, many years ago for the first time and done again on the last time I did a fresh new installation, also some years ago) index.html is not provided (what should it contain?). The index.html as available on the system now, was created by me when I created the web site. And wasnât changed since at least 2019-03-01 which was then in Leap 15.0. It survived all upgrade steps > 15.1 > 15.2 > 15.3 > 15.4 > 15.5 unharmed.
But now on the upgrade > 15.6 it was changed from
-rw-r----- 10 wappl www 872 Mar 1 2019 index.html
into
-rw------- 10 root root 872 Mar 1 2019 index.html.rpmnew
Same for favicon.ico
No other changes in the /srv/www/htdocs/ directory.
I am with @arvidjaar that there are almost no hints to what did this. The fact that (as you stressed) index.html is not part of apache2 or any other package makes it even more mysterious. And thus it will be very difficult to file a decent bug report.
PM. the second ls list above is from what I remember. I am not sure of the date, it could be that it was changed to 2024-10-28.
For what itâs worth, in answer to â(what should it contain?)â â hereâs an example simple HTML5 âindex.htmlâ â
<!DOCTYPE html>
<html lang="de">
<head>
<meta charset="UTF-8">
<!-- The Browser's Tab Title -->
<title>???.fritz.box</title>
<link rel="stylesheet" href="style.css">
</head>
<body>
<main>
<!-- Page content -->
<h1>PrĂźfen ob âŚ</h1>
</main>
</body>
</html>
And, an example simple Style Sheet â
/* style.css */
body {
color: black;
background-color: aqua;
}
Other distributions do include a default âindex.htmlâ â openSUSE doesnât âŚ
If, weâre wanting to be ânew user friendlyâ then, we could at least provide some example file content for a simple âdoes it workâ scenario âŚ
Taking a look at the scripts which are part of the apache2 RPM packages â
One of the things which the âapache2â package does, is the removal of the âwwwadminâ group â
postinstall scriptlet (using /bin/sh):
# wwwadmin group existed in past remove after openSUSE-13.2 out of support scope
if grep -q "^wwwadmin:" /etc/group; then
groupmod -n www wwwadmin 2>/dev/null ||:
usermod -g www wwwrun 2>/dev/null ||:
usermod -s /bin/false wwwrun 2>/dev/null ||:
fi
But, nothing related to the â/srv/www/htdocs/â directory content â the âfilesystemâ package also doesnât touch that directory.
Therefore, it seems that, an upgraded package on your system has a post-install script which touches the files in the â/srv/www/htdocs/â directory â
OK, it only confirms that it is not obvious which package does do this. Or which action.
And that makes it more unlikely that I will be able to create a system exactly as it was before the upgrade, because it is very unknown which aspect is to be get special attention to re-create it exactly as it was.
# 2024-10-28 14:41:11 apache2-2.4.58-150600.5.26.1.x86_64.rpm installed ok
# Additional rpm output:
# Please check /etc/permissions.local for settings of /usr/sbin/suexec .
# Updating /etc/sysconfig/apache2 ...
# warning: /srv/www/htdocs/index.html saved as /srv/www/htdocs/index.html.rpmsave
# warning: /srv/www/htdocs/favicon.ico saved as /srv/www/htdocs/favicon.ico.rpmsave
# Requesting apache restart (all instances)
#
But now, why would anybody want to do this?
This is normally done to configuration files, but then a new file is installed and the old file is saved. But here there is no new file at all.
Apart from the fact that replacing a websites main entrance page is a bit rude to say it friendly.
I think this is enough stuff to start a bug report. Will do that tomorrow and report here.