Project

General

Profile

Actions

Bug #24028

closed

character conversion error when calling '/logs' on foreman-proxy

Added by Ivan Necas almost 6 years ago. Updated over 5 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

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.

E, [2018-06-06T16:22:17.884203 ] ERROR -- : "\xFC" from ASCII-8BIT to UTF-8
I, [2018-06-06T16:22:17.884587 ] INFO -- : 10.0.0.1 - - [06/Jun/2018:16:22:17 -0500] "GET /logs/?from_timestamp=0 HTTP/1.1" 400 31 0.0341


Related issues 1 (0 open1 closed)

Is duplicate of Smart Proxy - Bug #24364: Logs module unable to return non-ASCII charactersClosedLukas ZapletalActions
Actions #1

Updated by Ivan Necas over 5 years ago

  • Status changed from Assigned to Duplicate
Actions #2

Updated by Ivan Necas over 5 years ago

  • Is duplicate of Bug #24364: Logs module unable to return non-ASCII characters added
Actions

Also available in: Atom PDF