Bug 1241157
| Summary: | Remove uses of gf_log/gf_msg before logging init | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Raghavendra Talur <rtalur> |
| Component: | core | Assignee: | Raghavendra Talur <rtalur> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | bugs, rkavunga |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-08-29 03:54:18 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: | |||
Lot of time since no activity on this bug. We have either fixed it already or it is mostly not critical anymore! Please re-open the bug if the issue is burning for you, or you want to take the bug to closure with fixes. |
Description of problem: When logging is not inited using gf_log or gf_msg gives an illusion that message is being logged but it isn't. Print all the critical info to stdout/stderr and don't use gf_log or gf_msg before logging_init. How reproducible: Always Steps to Reproduce: 1. Delete contents of /etc/glusterfs 2. start glusterd on command line. Actual results: just a usage format is printed on screen without telling what went wrong. Expected results: We should also print on screen what we are trying to log here. gf_msg ("glusterfs", GF_LOG_CRITICAL, errno, glusterfsd_msg_16); This is one example, there are probably few others. Let this bug cover all such occurences.