Bug 764271 (GLUSTER-2539) - gsyncd log management
Summary: gsyncd log management
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2539
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: pre-2.0
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: kaushik
QA Contact:
URL:
Whiteboard:
: GLUSTER-2561 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 19:09 UTC by Csaba Henk
Modified: 2011-05-19 07:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Csaba Henk 2011-03-16 19:09:51 UTC
glusterd should also take care of to set up logging for gsyncd (according to its namespace logic)

Comment 1 kaushik 2011-04-08 10:20:18 UTC
*** Bug 2561 has been marked as a duplicate of this bug. ***

Comment 2 Csaba Henk 2011-04-08 13:19:23 UTC
Fix in bz #2561 (duplicate) fixes this too.

Comment 3 Lakshmipathi G 2011-04-15 06:24:38 UTC
checked with 3.2.0qa12, gsyncd comes with default log file-
----
 gluster volume gsync config  :beta1 root.compute.amazonaws.com::slave  
state_file: /etc/glusterd/gsync/gluster%3A%2F%2F127.0.0.1%3Abeta1/ssh%3A%2F%2Froot%4079.125.76.86%3Agluster%3A%2F%2F127.0.0.1%3Aslave.status
log_level: debug
ssh_command: ssh -oPasswordAuthentication=no
pid_file: /etc/glusterd/gsync/gluster%3A%2F%2F127.0.0.1%3Abeta1/ssh%3A%2F%2Froot%4079.125.76.86%3Agluster%3A%2F%2F127.0.0.1%3Aslave.pid
log_file: /usr/local/var/log/glusterfs/gsync/gluster%3A%2F%2F127.0.0.1%3Abeta1/ssh%3A%2F%2Froot%4079.125.76.86%3Agluster%3A%2F%2F127.0.0.1%3Aslave.log
remote_gsyncd: /usr/local/libexec/glusterfs/gsyncd
gluster_command: /usr/local/sbin/glusterfs
-----------------------

Comment 4 Lakshmipathi G 2011-05-19 04:28:57 UTC
its a enhancement..moved to RTNR


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