http://bugzilla.suse.com/show_bug.cgi?id=1123726 http://bugzilla.suse.com/show_bug.cgi?id=1123726#c3 Philippe BIdault <philippe.bidault@getronics.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(philippe.bidault@ | |getronics.com) | --- Comment #3 from Philippe BIdault <philippe.bidault@getronics.com> --- Hi, Thanks for your reply !! Yes, indeed there are some 404 in the Apache proxy SSL log file. Here is the complete log following an "apt update" on the client : 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/InRelease HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/InRelease HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/InRelease HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/Release HTTP/1.1" 200 914 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/Release HTTP/1.1" 200 953 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/Release HTTP/1.1" 200 977 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/Release.gpg HTTP/1.1" 200 490 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/Release.gpg HTTP/1.1" 200 490 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/Release.gpg HTTP/1.1" 200 490 10.0.0.222 - - [01/Aug/2019:15:37:49 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/by-hash/SHA256/b78da06e87f1565010f76e0deec3913874eae6ce54db2e50810d49bcb238fc13 HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:49 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/Packages.gz HTTP/1.1" 200 20562304 10.0.0.222 - - [01/Aug/2019:15:37:50 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/by-hash/SHA256/4cbc1f114847c6366ce0ffcb8f8c85860e4ba3937a5ff5b41313361b69a514ba HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:50 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/by-hash/SHA256/a18527b826007191d7eb015ce4f6ceff405381463cc1ab59416052a8d3ea820b HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:50 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/Packages.gz HTTP/1.1" 200 70758 10.0.0.222 - - [01/Aug/2019:15:37:50 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/Packages.gz HTTP/1.1" 200 1673678 So in fact, the 404 are for the InRelease, I am using Release file in the Channel Repodata. [root@spacewalk debian-9]# pwd /var/cache/rhn/repodata/debian-9 [root@spacewalk debian-9]# ls -lrt total 38000 -rw-r--r--. 1 root root 38896249 Aug 1 15:38 Packages_debroot -rw-r--r-- 1 root root 0 Aug 1 15:38 Packages -rw-r--r--. 1 root root 20 Aug 1 15:38 Packages.gz -rw-r--r-- 1 root root 862 Aug 1 15:38 Release -rw-r--r-- 1 root root 490 Aug 1 15:38 Release.gpg Do you think that I should create the InRelease file to avoid this issue of regenerating the repository metadata ? Regards, Philippe. -- You are receiving this mail because: You are on the CC list for the bug.