Bug 1218506 - gf_msg not giving output to STDOUT.
Summary: gf_msg not giving output to STDOUT.
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: 3.7.0
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-05 06:40 UTC by Manikandan
Modified: 2017-03-08 10:58 UTC (History)
5 users (show)

Fixed In Version:
Clone Of: 1215017
Environment:
Last Closed: 2017-03-08 10:58:26 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Manikandan 2015-05-05 06:40:21 UTC
+++ This bug was initially created as a clone of Bug #1215017 +++

Description of problem:
gf_msg not sending the output to STDOUT.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
Run the command glusterfsd --print-exports tests/configfiles/bad_exports.
Change gf_log to gf_msg and run the same command.


Actual results:
[2015-04-24 06:47:15.375196] W [exports.c:1161:_exp_line_parse] 0-nfs-exports: Error parsing netgroups for: /asdf @ObVyg571RJaorkGbgVerI9esrck8yiVD7NVqqJvj2H9DuPH3SzHnYLIXjd4zZjuuh2N0O0bYYQf7VYNrYHoxc1llgRU1iEsQRy2XaWnUlhTHKVEL8tt1TrbZCi8qXyg0l058rTnW4msvU5hW83ESwyOE4bBSz4VsW0sJaVd8Gv4waZqojemLN8AIlAoChVOfP1yhuAP1298ejkaf2fjhdfa4t4effhgadff342fdddgasdg42gahgdmnui24290hfjdjadgdkjhg2nvncms(sec=sys,rw,anonuid=1)
/test @test(rw,anonuid=0,sec=sys,) shreyas.s(rw,anonuid=595,sec=sys,) shreyas.facebook.com(rw,anonuid=0,sec=sys,)


Expected results:
/test @test(rw,anonuid=0,sec=sys,) shreyas.s(rw,anonuid=595,sec=sys,) shreyas.facebook.com(rw,anonuid=0,sec=sys,)

Additional info:

Comment 2 Kaushal 2017-03-08 10:58:26 UTC
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.


Note You need to log in before you can comment on or make changes to this bug.