REVIEW: http://review.gluster.org/9559 (rdma:reduce log level from E to W) posted (#2) for review on master by mohammed rafi kc (rkavunga)
Rafi, could you please include a public comment with some details about this bug?
Description of problem: After a fresh installation and when glusterd starts, following rdma related Errors are getting logged in the glusterd logs: --- [2012-05-11 15:53:00.190329] I [glusterfsd.c:1628:main] 0-glusterd: Started running glusterd version 3.3.0qa38 [2012-05-11 15:53:00.196526] I [graph.c:250:gf_add_cmdline_options] 0-management: adding option 'upgrade' for volume 'management' with value 'on' [2012-05-11 15:53:00.199228] I [glusterd.c:805:init] 0-management: Using /var/lib/glusterd as working directory [2012-05-11 15:53:00.228757] E [rpc-transport.c:261:rpc_transport_load] 0-rpc-transport: /usr/lib64/glusterfs/3.3.0qa38/rpc-transport/rdma.so: cannot open shared object file: No such file or directory [2012-05-11 15:53:00.228785] E [rpc-transport.c:265:rpc_transport_load] 0-rpc-transport: volume 'rdma.management': transport-type 'rdma' is not valid or not found on this machine --- Why is rdma enabled by default though at least one file needed in order to use it is not installed by default? From a support perspective, I understand that this can be safely ignored. But this may be confusing to the users as it is logged as an error "E" message. Can this be either logged as a Warning "W" or an Info "I"? Version-Release number of selected component (if applicable): All versions of Glusterfs. How reproducible: Always. Once glusterd started, you will see those errors in the glusterd logs. This behavior should be visible in all other types of installations as well.
REVIEW: http://review.gluster.org/9559 (rdma: reduce log level from E to W) posted (#3) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/9559 (rdma: reduce log level from E to W) posted (#4) for review on master by mohammed rafi kc (rkavunga)
COMMIT: http://review.gluster.org/9559 committed in master by Raghavendra G (rgowdapp) ------ commit eebc3c06693c324be261c994f8e74886b7715770 Author: Mohammed Rafi KC <rkavunga> Date: Tue Feb 10 17:11:21 2015 +0530 rdma: reduce log level from E to W glusterd process, when try to initialize default vol file, will always through an error if there is no rdma device. Changing the log levels and log messages to more appropriately. Change-Id: I75b919581c6738446dd2d5bddb7b7658a91efcf4 BUG: 1188232 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/9559 Reviewed-by: Raghavendra Talur <rtalur> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user