Bug 965175 - logging:volume status spurious message
Summary: logging:volume status spurious message
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: 2.1
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: krishnan parthasarathi
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-20 15:42 UTC by Saurabh
Modified: 2016-01-19 06:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-12 07:13:08 UTC
Embargoed:


Attachments (Terms of Use)

Description Saurabh 2013-05-20 15:42:10 UTC
Description of problem:
executing gluster volume status command
gives some spurious W(warning) messages in the logging 

Version-Release number of selected component (if applicable):
glusterfs-3.4.0.8rhs-1.el6rhs.x86_64

How reproducible:
always

Steps to Reproduce:
1. gluster volume status
2. keep checking the logs in /var/log/glusterfs/etc-glusterfs-glusterd.vol.log
3.

Actual results:
[2013-05-20 08:30:05.355235] I [glusterd-handler.c:3177:__glusterd_handle_status_volume] 0-management: Received status volume req for volume dist-rep
[2013-05-20 08:30:05.366575] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:05.416146] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:05.416189] W [syncop.c:32:__run] 0-management: re-running already running task



[2013-05-20 08:30:33.526797] I [glusterd-handler.c:3177:__glusterd_handle_status_volume] 0-management: Received status volume req for volume dist-rep
[2013-05-20 08:30:33.528441] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:33.528574] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:33.530286] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:33.530327] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:33.533925] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:33.534046] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:33.535841] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:30:33.535927] W [syncop.c:32:__run] 0-management: re-running already running task


[2013-05-20 08:44:54.737489] I [glusterd-handler.c:3177:__glusterd_handle_status_volume] 0-management: Received status volume req for volume dist-rep
[2013-05-20 08:44:54.745747] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:44:54.748482] W [syncop.c:32:__run] 0-management: re-running already running task
[2013-05-20 08:44:54.753601] W [syncop.c:32:__run] 0-management: re-running already running task


Expected results:
could not understand these messages and there requirement. What are we re-running, some process or something else.

Additional info:

Comment 2 Nagaprasad Sathyanarayana 2014-05-06 11:43:43 UTC
Dev ack to 3.0 RHS BZs

Comment 4 Atin Mukherjee 2014-08-12 07:13:08 UTC
Closing this bug as its no more reproducible with latest bits, kindly re-open if the issue persists.


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