Red Hat Bugzilla – Bug 1292736
running virt-who in big vmware environments results in to fast growing logfiles
Last modified: 2016-11-30 19:36:01 EST
We need this fix also in rhel7.
This is already fixed upstream and will be resolved by rebase.
Fixed in virt-who-0.17-1.el7.
*** Bug 1355624 has been marked as a duplicate of this bug. ***
verified with virt-who-0.17-6.el7
disable DEBUG option, there is no host/guests json info in rhsm.log
enable DEBUG option, will print the json info
Deepannagaraj, it is possible to do a hotfix for this bug. Please follow official hotfix process and propose this bug for z-stream.
virt-who logs to the /var/log/rhsm/rhsm.log file. If something in /var/log/foreman/ is growing too fast, I would guess it is a different issue. But it would be best if someone can analyze the big file for log entries that are filling it. Only that way we can be sure what is the problem there.
(In reply to Radek Novacek from comment #18)
> virt-who logs to the /var/log/rhsm/rhsm.log file. If something in
> /var/log/foreman/ is growing too fast, I would guess it is a different
> issue. But it would be best if someone can analyze the big file for log
> entries that are filling it. Only that way we can be sure what is the
> problem there.
virt-who submits data to Candlepin via Foreman/Katello.
Sadly Foreman will log the whole request (incl the full JSON) to production log. So thats the reason for foreman/production.log to grow.
Same happens in Candlepin, see c11 for a workaround.
does the customer use filter_hosts/exclude_hosts options to run virt-who only against systems that do run Red Hat servers? If not, you might suggest it to them, I think it would both reduce the load and generate less logs.
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.