+++ This bug was initially created as a clone of Bug #1192452 +++ 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): ******************************************* mainline How reproducible: ********************************************* Always 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.
The only way to get rid of this is to change the log level from ERROR to INFO as glusterd.info file gets created lately on the first probe or volume create. If we move the log level to INFO then the genuine errors can be ignored. I don't think we would need to fix this atm.