Description of problem: Openshift Router does not save haproxy logs. Version-Release number of selected component (if applicable): 3.x How reproducible: 100% Steps to Reproduce: 1. oc logs ROUTER Actual results: - No Haproxy logs Expected results: - Haproxy logs to be shown. Additional info: - Is there a workaround to get haproxy logs since it normally wants to log to rsyslog. UPSTREAM ISSUES: https://github.com/openshift/origin/issues/1871 https://github.com/openshift/origin/issues/7974
Here's an example repo to build a custom haproxy based template router image and run it and send haproxy logs to a syslog daemon. https://github.com/ramr/openshift-haproxy-custom-logs The gist is to take the current haproxy-config.template and add the appropriate log configuration and rebuild a router image and then use that image. You can use these instructions as a guide: https://docs.openshift.com/enterprise/3.1/install_config/install/deploy_router.html#deploying-a-customized-haproxy-router https://docs.openshift.com/enterprise/3.1/install_config/install/deploy_router.html#rebuilding-your-router Note: The logs are sent to a syslog address (default is 127.0.0.1 port 514) and uses udp. See: https://github.com/ramr/openshift-haproxy-custom-logs/blob/master/haproxy-config.template#L11 for more details on usage. You can pass this config in via environment variables: oc env dc/router HAPROXY_ROUTER_SYSLOG_ADDRESS=127.0.0.1 HAPROXY_ROUTER_LOG_LEVEL=debug
Adding an RFE tag - since this is newly requested functionality. The above workaround using a custom image is an interim solution for now.
*** Bug 975533 has been marked as a duplicate of this bug. ***
The PR to enable remote syslog has not merged. So it will be in 3.3 at the earliest. https://github.com/openshift/origin/pull/8332
https://github.com/openshift/origin/pull/8332 PR merged into origin. Waiting on documentation entries to merge https://github.com/openshift/openshift-docs/pull/1873
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, 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/RHBA-2016:1933
https://bugzilla.redhat.com/show_bug.cgi?id=1438482