Description of problem: ******************************************* After the fresh install of glusterfs the log file shows following error: E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/glusterd.info, returned error: (No such file or directory) E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/glusterd.info, returned error: (No such file or directory) E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/options, returned error: (No such file or directory) Even though the info file gets created after glusterd service start we should not log this message as error after the fresh install. Version-Release number of selected component (if applicable): ******************************************* glusterfs-libs-3.6.0.44-1.el6rhs.x86_64 glusterfs-server-3.6.0.44-1.el6rhs.x86_64 samba-vfs-glusterfs-4.1.16-3.el6rhs.x86_64 glusterfs-api-3.6.0.44-1.el6rhs.x86_64 glusterfs-cli-3.6.0.44-1.el6rhs.x86_64 glusterfs-geo-replication-3.6.0.44-1.el6rhs.x86_64 glusterfs-3.6.0.44-1.el6rhs.x86_64 glusterfs-fuse-3.6.0.44-1.el6rhs.x86_64 glusterfs-rdma-3.6.0.44-1.el6rhs.x86_64 How reproducible: ********************************************* Saw after fresh install. Steps to Reproduce: 1.Install latest glusterfs 2.Verify the logs for any errors Actual results: ******************************************** The log file shows errors for glusterd.info file as : E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/glusterd.info, returned error: (No such file or directory) Expected results: *********************************************** It should not be logged as Error after the fresh install. Additional info:
Isn't this a duplicate of Bug 1110715?
I am not sure about the root cause but i see the error for glusterd.info file in gluster logs after fresh install, which should not happen.Discussed with KP and it needs to be fixed in gluster-server.I would like to track this seperately until the root cause is found for both the bz's.
(In reply to Prasanth from comment #2) > Isn't this a duplicate of Bug 1110715? Prasanth, This is a different from BZ 1110715. glusterd.info is generated lately, until a peer is probed or volume is created. So what happens in the fresh installation is, glusterd finds this glusterd.info file is missing and reports it as an error in glusterd logs. This bug is to move such an log message to INFO message, and not under ERROR category
As this is expected as explained in #c4, closing this bug.