Hi,
so while trying to move fedora magazine, I stumbled on a error, that resulted in "error 500", with a firm yet informative message telling me to go see the log file. While that's technically correct, it seems that I do not have access to that on staging (or prod for that matter).
I tried to look on log01.phx2.fedoraproject.org, and it seems that httpd logs are not forwarded for the moment.
I suspect the error 500 come either from network/firewall (always blame network first), but it work in http, so I suspect this come from not having mod_proxy_connect enabled on the proxy. I am going to take a wild guess and blindly test the 2nd hypothesis, but in the mean time, I suspect that sysadmin-web group people would greatly benefit from being able to read the logs of apache.
So, for the record, the error do not come from missing mod_proxy_connect
[root@proxy01 httpd][STG]# date ; cat fedoramagazine.org-error.log Fri Jul 26 16:51:53 UTC 2019 [Fri Jul 26 04:29:59.710932 2019] [proxy:error] [pid 32612:tid 140339574687488] (110)Connection timed out: AH00957: HTTP: attempt to connect to 66.226.72.133:80 (66.226.72.133) failed [Fri Jul 26 04:29:59.711013 2019] [proxy_http:error] [pid 32612:tid 140339574687488] [client 58.20.108.148:40606] AH01114: HTTP: failed to make connection to backend: 66.226.72.133 [Fri Jul 26 16:01:54.560362 2019] [ssl:error] [pid 6411:tid 140340082546432] [remote 35.197.52.145:443] AH01961: SSL Proxy requested for fedoramagazine.org:443 but not enabled [Hint: SSLProxyEngine] [Fri Jul 26 16:01:54.567414 2019] [proxy:error] [pid 6411:tid 140340082546432] AH00961: HTTPS: failed to enable ssl support for 35.197.52.145:443 (fedoramag.wpengine.com) [Fri Jul 26 16:26:57.191129 2019] [ssl:error] [pid 6411:tid 140340082546432] [remote 35.197.52.145:443] AH01961: SSL Proxy requested for fedoramagazine.org:443 but not enabled [Hint: SSLProxyEngine] [Fri Jul 26 16:26:57.191156 2019] [proxy:error] [pid 6411:tid 140340082546432] AH00961: HTTPS: failed to enable ssl support for 35.197.52.145:443 (fedoramag.wpengine.com) [Fri Jul 26 16:40:09.204030 2019] [ssl:error] [pid 16262:tid 140339864336128] [remote 35.197.52.145:443] AH01961: SSL Proxy requested for fedoramagazine.org:443 but not enabled [Hint: SSLProxyEngine] [Fri Jul 26 16:40:09.204058 2019] [proxy:error] [pid 16262:tid 140339864336128] AH00961: HTTPS: failed to enable ssl support for 35.197.52.145:443 (fedoramag.wpengine.com) [Fri Jul 26 16:40:12.107972 2019] [ssl:error] [pid 16264:tid 140340057368320] [remote 35.197.52.145:443] AH01961: SSL Proxy requested for fedoramagazine.org:443 but not enabled [Hint: SSLProxyEngine] [Fri Jul 26 16:40:12.107993 2019] [proxy:error] [pid 16264:tid 140340057368320] AH00961: HTTPS: failed to enable ssl support for 35.197.52.145:443 (fedoramag.wpengine.com) [Fri Jul 26 16:42:04.602356 2019] [ssl:error] [pid 16264:tid 140340057368320] [remote 35.197.52.145:443] AH01961: SSL Proxy requested for fedoramagazine.org:443 but not enabled [Hint: SSLProxyEngine] [Fri Jul 26 16:42:04.602445 2019] [proxy:error] [pid 16264:tid 140340057368320] AH00961: HTTPS: failed to enable ssl support for 35.197.52.145:443 (fedoramag.wpengine.com)
I will see if we can get sysadmin-web more access to the proxies.
httpd logs do not use rsyslogd so are local to the system until they are synced over every 24 hours
Metadata Update from @smooge: - Issue assigned to smooge
Ok, thanks to the info given by smooge, I did manage to finish the migration. Should I keep that ticket open for the generic log access requests for future ?
We have had that as something we have been looking at for a long time... I don't think having this open will help any. :(
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.