Description of problem: We recently set up a Satellite 6.3.1 with one capsule. When we go to the capsule status page in the Satellite, the status page shows ERF50-5345, and it looks like the capsule is returning a 400. The proxy.log shows the following: E, [2018-06-06T16:22:17.884203 ] ERROR -- : "\xFC" from ASCII-8BIT to UTF-8 I, [2018-06-06T16:22:17.884587 ] INFO -- : 172.19.129.210 - - [06/Jun/2018:16:22:17 -0500] "GET /logs/?from_timestamp=0 HTTP/1.1" 400 31 0.0341 Version-Release number of selected component (if applicable): 6.3.1 I am not sure how to reproduce this, we set up a satellite with one capsule and then synced repos into it. The \xFC might be a ü, its possible something pushed that character into the log buffer. The Satellite and capsule both had UTF8 as their locale fwiw, checked via localectl.
It should match the `/var/log/foreman-proxy/proxy.log`. I tried to simulate adding 'ü' to the buffer, but the server was handling this properly. I guess there was some binary data logged into the log, that caused the trouble: the log file should help us identify what the data were and act accordingly.
How do you get that issue (given I have that to-be-uploaded broken "/var/log/foreman-proxy/proxy.log")? I have tried to access: https://sat640snap7.example.com/logs but it says "The page you were looking for doesn't exist.", adding port ":8008" gives me "Secure Connection Failed".
Using the details of the proxy.log I was able to reproduce the issue: 1. enable http port on proxy (gets enabled when using the templates plugin) - in /etc/foreman-proxy/settings.yml uncomment `:http_port: 8000` and restart foreman-proxy 2. curl -k --cert /etc/foreman-proxy/foreman_ssl_cert.pem --key /etc/foreman-proxy/foreman_ssl_key.pem https://localhost:8000 - note using https with http port 3. go to the capsule details in UI and in the logs tab This produces ASCII-8BIT to UTF-8 errors in /var/log/foreman-proxy/proxy.log.
Upstream bug assigned to inecas
*** This bug has been marked as a duplicate of bug 1615439 ***