Description of problem: When refreshing the features on Satellite 6.9.3 the apache logs '/var/log/httpd/foreman-ssl_access_ssl.log' show the following API call: ~~~ XXX.XXX.XXX.XXX - - [12/Jul/2021:10:04:50 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:11:05:04 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:12:04:38 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:13:05:00 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:14:04:57 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:15:04:59 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:16:04:56 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:16:21:27 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:16:21:28 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:16:21:28 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" XXX.XXX.XXX.XXX - - [12/Jul/2021:16:21:28 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" ~~~ And the following errors on '/var/log/httpd/foreman-ssl_error_ssl.log' apache logs. ~~~ [Fri Jul 09 08:39:50.627665 2021] [proxy:error] [pid 11308] AH00959: ap_proxy_connect_backend disabling worker for (pulpcore-api) for 60s [Fri Jul 09 08:39:50.627668 2021] [proxy_http:error] [pid 11308] [client XXX.XXX.XXX.XXX:36230] AH01114: HTTP: failed to make connection to backend: httpd-UDS [Fri Jul 09 08:39:50.786779 2021] [ssl:warn] [pid 62365] [client XXX.XXX.XXX.XXX:36236] AH02227: Failed to set r->user to 'SSL_CLIENT_S_DN_CN' [Fri Jul 09 08:39:50.787018 2021] [proxy:error] [pid 62365] (2)No such file or directory: AH02454: HTTP: attempt to connect to Unix domain socket /run/pulpcore-api.sock (pulpcore-api) failed [Fri Jul 09 08:39:50.787030 2021] [proxy:error] [pid 62365] AH00959: ap_proxy_connect_backend disabling worker for (pulpcore-api) for 60s [Fri Jul 09 08:39:50.787033 2021] [proxy_http:error] [pid 62365] [client XXX.XXX.XXX.XXX:36236] AH01114: HTTP: failed to make connection to backend: httpd-UDS [Fri Jul 09 08:39:50.885699 2021] [ssl:warn] [pid 11016] [client XXX.XXX.XXX.XXX:36240] AH02227: Failed to set r->user to 'SSL_CLIENT_S_DN_CN' [Fri Jul 09 08:39:50.885919 2021] [proxy:error] [pid 11016] (2)No such file or directory: AH02454: HTTP: attempt to connect to Unix domain socket /run/pulpcore-api.sock (pulpcore-api) failed [Fri Jul 09 08:39:50.885930 2021] [proxy:error] [pid 11016] AH00959: ap_proxy_connect_backend disabling worker for (pulpcore-api) for 60s [Fri Jul 09 08:39:50.885933 2021] [proxy_http:error] [pid 11016] [client XXX.XXX.XXX.XXX:36240] AH01114: HTTP: failed to make connection to backend: httpd-UDS ~~~ Version-Release number of selected component (if applicable): Satellite 6.9.3 How reproducible: Go to the Satellite WebUI, Infrastructure > Capsules > Click on the Satellite Host > Actions > Refresh Steps to Reproduce: 1. Go to the Satellite WebUI 2. Click on "Infrastructure > Capsules > Click on the Satellite Host > Actions > Refresh" 3. Check the logs '/var/log/httpd/foreman-ssl_error_ssl.log' and '/var/log/httpd/foreman-ssl_access_ssl.log' Actual results: Customers are seeing errors on the apache logs. ~~~ ==> /var/log/httpd/foreman-ssl_access_ssl.log <== 2620:52:0:ab0:6a11:d248:3bfc:a04f - - [12/Jul/2021:13:45:13 -0400] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby" ==> /var/log/httpd/foreman-ssl_error_ssl.log <== [Mon Jul 12 13:45:13.928693 2021] [ssl:warn] [pid 12341] [client 2620:52:0:ab0:6a11:d248:3bfc:a04f:40690] AH02227: Failed to set r->user to 'SSL_CLIENT_S_DN_CN' [Mon Jul 12 13:45:13.928988 2021] [proxy:error] [pid 12341] (2)No such file or directory: AH02454: HTTP: attempt to connect to Unix domain socket /run/pulpcore-api.sock (pulpcore-api) failed [Mon Jul 12 13:45:13.929006 2021] [proxy:error] [pid 12341] AH00959: ap_proxy_connect_backend disabling worker for (pulpcore-api) for 60s [Mon Jul 12 13:45:13.929009 2021] [proxy_http:error] [pid 12341] [client 2620:52:0:ab0:6a11:d248:3bfc:a04f:40690] AH01114: HTTP: failed to make connection to backend: httpd-UDS ~~~ Expected results: Additional info:
Are you running `content prepare` commands to migrate from pulp 2 to pulp 3? Just trying to understand why it is expected for pulp 3 to run.
One theory is that potentially there should be no calls to pulp3 on 6.9 while working with capsules. Moving to Katello for the initial investigation. Thanks.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:4702
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days