Bug 1286684
Summary: | running virt-who in big vmware environments results in to fast growing logfiles - candlepin + foreman | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Marcel Gazdík <mgazdik> | |
Component: | Candlepin | Assignee: | satellite6-bugs <satellite6-bugs> | |
Status: | CLOSED ERRATA | QA Contact: | Jan Hutař <jhutar> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.1.5 | CC: | ahuchcha, bbuckingham, bcourt, bkearney, chorn, csnyder, cwelton, jentrena, jhutar, mgazdik, oshtaier | |
Target Milestone: | Unspecified | Keywords: | Triaged | |
Target Release: | Unused | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1313036 (view as bug list) | Environment: | ||
Last Closed: | 2018-02-21 17:11:41 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1313036, 1503573 | |||
Bug Blocks: | 1296845 |
Description
Marcel Gazdík
2015-11-30 13:47:58 UTC
No changes with 6.1.4. Any ideas to improve this? One way to reduce the log output of candlepin would be to add the following lines to your /etc/candlepin/candlepin.conf file: """ log4j.logger.org.candlepin.resource.ConsumerResource.checkForGuestsUpdate=WARN log4j.logger.org.candlepin.resource.HypervisorResource=WARN """ Please note this will stop not only the undesirable log messages but the vast majority of log messages coming from ConsumerResource and HypervisorResource. Also note that this configuration file might get changed by Katello. With ConsumerResource=WARN in place, one virt-who commit is only causing these messages: 2015-12-16 10:26:53,967 [req=316948b0-2b97-4f4b-a38b-cf5227f89ea6, org=] INFO org.candlepin.common.filter.LoggingFilter - Request: verb=POST, uri=/candlepin/hypervisors?owner=Vodafone&env=Development/cv-VF-All_Locations-Capsule-RHEL7-Essentials 2015-12-16 10:28:02,794 [req=316948b0-2b97-4f4b-a38b-cf5227f89ea6, org=Vodafone] INFO org.candlepin.common.filter.LoggingFilter - Response: status=200, content-type="application/json", time=68835 ...but we would actually appreciate to see if the action succeeded. * Setting the following two values in /etc/candlepin/candlepin.conf makes candlepin.log be more readable and not growing as much as before: log4j.logger.org.candlepin.resource.ConsumerResource=WARN log4j.logger.org.candlepin.resource.HypervisorResource=WARN * After the logging change we miss out on statistics of the update, as we only see that the request was processed OK. We think the following would be best: - the current messages like "org.candlepin.resource.ConsumerResource - Updating 1 guest IDs." is what should be belonging to DEBUG level. Suggestion: change the level these are logged to from INFO to DEBUG. - We could then set loglevel to INFO instead of WARN. We would nontheless want to see if things break horribly, so "updated X hypervisors and Y consumers" messages could be output to INFO. With these 2 changes, we could run INFO loglevel, and would have the amount down to reasonable level. This has been fixed upstream in Candlepin 2.0.11-1 which is targetted for Sat 6.3 Note: Candlepin's counterpart of this bug is bug 1313036 which references this commit: https://github.com/candlepin/candlepin/commit/edcd7ba0ae95edd77bacc6cc6e6c420e1383fcc5 For Foremanf part, this issue, linked in the case, is probably relevant: http://projects.theforeman.org/issues/13499 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-2018:0336 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-2018:0336 |