[Bugs] [Bug 1542829] New: Too many log messages about dictionary and options
bugzilla at redhat.com
bugzilla at redhat.com
Wed Feb 7 06:12:15 UTC 2018
Bug ID: 1542829
Summary: Too many log messages about dictionary and options
Assignee: bugs at gluster.org
Reporter: atumball at redhat.com
CC: bugs at gluster.org
Description of problem:
There are many logs added in the code base for developer's focus, but doesn't
make sense in a release, as they are harmless for now.
Some examples of such logs are:
> [2018-02-04 17:28:13.213433] I [MSGID: 101097] [xlator.c:322:xlator_dynload_newway] 0-xlator: dlsym(xlator_api) on /usr\
/local/lib/glusterfs/4.1dev/xlator/storage/posix.so: undefined symbol:
xlator_api. Fall back to old symbols
---- A user can't understand nor take any action to resolve it.
> [2018-02-04 17:28:13.209645] W [MSGID: 101002] [options.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' is \
deprecated, preferred is 'transport.address-family', continuing with correction
---- This is set from glusterd itself during volgen, and a user can't resolve
> [2018-02-04 17:28:13.216827] I [dict.c:1126:data_to_uint16] (-->/usr/local/lib/glusterfs/4.1dev/rpc-transport/socket.so\
-->/usr/local/lib/libglusterfs.so.0(data_to_uint16+0xf5) [0x7f11fe243b6c] )
0-dict: key null, \
unsigned integer type asked, has string type [Invalid argument]
---- This is a warning about the code itself, and in a released version, user
can't do anything about it.
> [2018-02-04 17:28:13.240042] W [MSGID: 101174] [graph.c:363:_log_if_unknown_option] 0-patchy-server: option 'rpc-auth.auth-null' is not recognized
---- Again, these options are set by glusterd, user can't do anything about it.
> [2018-02-04 17:28:14.532794] I [MSGID: 101016] [glusterfs3.h:738:dict_to_xdr] 0-dict: key 'trusted.ec.config' is would not be sent on wire in future [Invalid argument]
---- This is very much a warning for developer, but user can't handle nor
resolve any of this.
Version-Release number of selected component (if applicable):
release-4.0 (On master branch these logs are still applicable)
Steps to Reproduce:
1. Run glusterfs process (glusterd; volume create; start; mount);
These logs are flooded in log files.
No logs which are not actionable, nor causing a behavior change in product
should be logged in log file during normal operations.
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs