| Summary: | KATELLO_LOGGING is not working anymore with thin setup | ||
|---|---|---|---|
| Product: | [Retired] Katello | Reporter: | Lukas Zapletal <lzap> |
| Component: | Packaging | Assignee: | Lukas Zapletal <lzap> |
| Status: | CLOSED NOTABUG | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | jweiss |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-02 09:17:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Lukas Zapletal
2011-10-03 16:06:59 UTC
Jeff, KATELLO_LOGGING works for me. At least when I set it to "debug" or "warn" the number of log messages increases or decreases respectively. Therefore I recommend you to open up discussion about setting the default level to "warn" maybe if it bothers you or you think this could be an issue in the production. On top of that we have got (hopefully) working logrotate configuration. I just slightly extended it a bit with katello-jobs and thin related logs, but the production.log is already there and it should rotate it once a week. b7f6243 adding katello-job logrotate script I have opened a discussion on the list to use syslog facility rather than direct logging. I think it is much better for production deployment. |