Hide Forgot
On RHEL7 we should leverage journald sending all the logs there for: - foreman core app - plugins (katello, candlepin, pulp) - foreman proxies - cron jobs (using systemd-cat) When possible, we should send logging levels properly as well, so users are able to leverage fine-grained filtering system in journald (WARN, ERROR, DEBUG, TRACE). Let's also make sure that timestamps are correctly sent and we leverage all the journald goodies.
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
*** Bug 1196754 has been marked as a duplicate of this bug. ***
Upstream bug component is Packaging
Moving 6.2 bugs out to sat-backlog.
Lukas, Would you consider this BZ and https://bugzilla.redhat.com/show_bug.cgi?id=1305013 to be duplicates? If no, can you clarify the differences? If yes, can we keep the most appropriate one and close the other as a dupe.
Yeah, I renamed this one a bit, the goal is really to send this to (a logging) daemon avoiding own logrotating/rolling/restarting.
*** Bug 1305013 has been marked as a duplicate of this bug. ***
Upstream bug assigned to lzap
Closing, we implemented this in upstream but in Satellite we are going to document and go towards integrating with rsyslog rather than with journald for 3rd party logging. Good to have the feature for the future.
Patrick, this is just a tracker for 6.6 feature "improve common logging". I am going to slip it to ON_QA and assign Stephen here, I believe this is already VERIFIED. Details how to set things up are: https://github.com/lzap/foreman-elasticsearch
Hello lzap explained to me: by default foreman core (rails) writes to /var/log/foreman/production.log and smart proxy writes to /var/log/foreman-proxy/proxy.log to use journald, which will forward logs to rsyslog and then write to /var/log/messages, you need to run: satellite-installer --foreman-logging-level info --foreman-logging-type journald \ --foreman-logging-layout pattern --foreman-proxy-log JOURNAL systemctl restart httpd NOTE the `--foreman-logging-type journald` option installs foreman-journald but package foreman-proxy-journald was not installed, I expected --foreman-proxy-log JOURNAL to pull it in. We can document that, raise another bug. Before installing as above, I could hammer host list (to check foreman core) tail -f /var/log/foreman/production.log 019-08-07T15:09:05 [I|app|a0ce4328] Started GET "/api/hosts?page=1&per_page=1000" for 10.37.192.23 at 2019-08-07 15:09:05 +0200 2019-08-07T15:09:05 [I|app|a0ce4328] Processing by Api::V2::HostsController#index as JSON 2019-08-07T15:09:05 [I|app|a0ce4328] Parameters: {"page"=>"1", "per_page"=>"1000", "apiv"=>"v2", "host"=>{}} After installing as above I could: hammer host list (to check foreman core) journalctl --follow Aug 07 15:39:56 dell-r330-12.gsslab.brq.redhat.com foreman[21356]: Started GET "/api/hosts?page=1&per_page=1000" for 10.37.192.23 at 2019-08-07 15:39:56 +0200 Aug 07 15:39:56 dell-r330-12.gsslab.brq.redhat.com foreman[21356]: Processing by Api::V2::HostsController#index as JSON Aug 07 15:39:56 dell-r330-12.gsslab.brq.redhat.com foreman[21356]: Parameters: {"page"=>"1", "per_page"=>"1000", "apiv"=>"v2", "host"=>{}} I also set SyncIntervalSec=10 and then did systemctl daemon-reload to reduce the wait time. Thank you
Bug 1738784 - foreman-proxy-log JOURNAL option should install foreman-proxy-journald DocsBug Bug 1738850 - Logging to journald and rsyslog
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/RHSA-2019:3172