[Gluster-users] Géo-rep fail
anthony garnier
sokar6012 at hotmail.com
Tue May 17 07:34:56 UTC 2011
Hi,
I've put the Client log in Debug mod :
# gluster volume geo-replication /soft/venus config log-level DEBUG
geo-replication config updated successfully
# gluster volume geo-replication /soft/venus config log-file
/usr/local/var/log/glusterfs/geo-replication-slaves/${session_owner}:file%3A%2F%2F%2Fsoft%2Fvenus.log
# gluster volume geo-replication athena /soft/venus config session-owner
28cbd261-3a3e-4a5a-b300-ea468483c944
# gluster volume geo-replication athena /soft/venus start
Starting geo-replication session between athena & /soft/venus has been successful
# gluster volume geo-replication athena /soft/venus status
MASTER SLAVE STATUS
--------------------------------------------------------------------------------
athena /soft/venus starting...
and then :
# gluster volume geo-replication athena /soft/venus status
MASTER SLAVE STATUS
--------------------------------------------------------------------------------
athena /soft/venus faulty
For client :
cat /usr/local/var/log/glusterfs/geo-replication-slaves/28cbd261-3a3e-4a5a-b300-ea468483c944:file%3A%2F%2F%2Fsoft%2Fvenus.log
[2011-05-17 09:20:40.519731] I [gsyncd(slave):287:main_i] <top>: syncing: file:///soft/venus
[2011-05-17 09:20:40.520587] I [resource(slave):200:service_loop] FILE: slave listening
[2011-05-17 09:20:40.532951] I [repce(slave):61:service_loop] RepceServer: terminating on reaching EOF.
[2011-05-17 09:21:50.528803] I [gsyncd(slave):287:main_i] <top>: syncing: file:///soft/venus
[2011-05-17 09:21:50.529666] I [resource(slave):200:service_loop] FILE: slave listening
[2011-05-17 09:21:50.542349] I [repce(slave):61:service_loop] RepceServer: terminating on reaching EOF.
For server :
# cat /usr/local/var/log/glusterfs/geo-replication/athena/file%3A%2F%2F%2Fsoft%2Fvenus.log
[2011-05-17 09:30:04.431369] I [monitor(monitor):42:monitor] Monitor: ------------------------------------------------------------
[2011-05-17 09:30:04.431669] I [monitor(monitor):43:monitor] Monitor: starting gsyncd worker
[2011-05-17 09:30:04.486852] I [gsyncd:287:main_i] <top>: syncing: gluster://localhost:athena -> file:///soft/venus
[2011-05-17 09:30:04.488148] D [repce:131:push] RepceClient: call 30011:47491847633776:1305617404.49 __repce_version__() ...
[2011-05-17 09:30:04.635481] D [repce:141:__call__] RepceClient: call 30011:47491847633776:1305617404.49 __repce_version__ -> 1.0
[2011-05-17 09:30:04.635751] D [repce:131:push] RepceClient: call 30011:47491847633776:1305617404.64 version() ...
[2011-05-17 09:30:04.636342] D [repce:141:__call__] RepceClient: call 30011:47491847633776:1305617404.64 version -> 1.0
[2011-05-17 09:30:04.645972] E [syncdutils:131:log_raise_exception] <top>: FAIL:
Traceback (most recent call last):
File "/usr/local/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 102, in main
main_i()
File "/usr/local/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 294, in main_i
local.connect()
File "/usr/local/libexec/glusterfs/python/syncdaemon/resource.py", line 379, in connect
raise RuntimeError("command failed: " + " ".join(argv))
RuntimeError: command failed: /usr/local/sbin/glusterfs --xlator-option *-dht.assert-no-child-down=true -l /usr/local/var/log/glusterfs/geo-replication/athena/file%3A%2F%2F%2Fsoft%2Fvenus.gluster.log -s localhost --volfile-id athena --client-pid=-1 /tmp/gsyncd-aux-mount-TEqjwY
[2011-05-17 09:30:04.647973] D [monitor(monitor):57:monitor] Monitor: worker got connected in 0 sec, waiting 59 more to make sure it's fine
Thx for your help.
Anthony
> Date: Mon, 16 May 2011 20:56:44 +0530
> From: csaba at gluster.com
> CC: sokar6012 at hotmail.com
> Subject: Re: Géo-rep fail
>
> On 05/16/11 17:06, anthony garnier wrote:
> > Hi,
> > I'm currently trying to use géo-rep on the local data-node into a
> > directory but it fails with status "faulty"
> [...]
> > I've done this cmd :
> > # gluster volume geo-replication athena /soft/venus config
> >
> > # gluster volume geo-replication athena /soft/venus start
> >
> > # gluster volume geo-replication athena /soft/venus status
> > MASTER SLAVE STATUS
> > --------------------------------------------------------------------------------
> > athena /soft/venus faulty
> >
> >
> > Here is the log file in Debug mod :
> >
> > [2011-05-16 13:28:55.268006] I [monitor(monitor):42:monitor] Monitor:
> > ------------------------------------------------------------
> > [2011-05-16 13:28:55.268281] I [monitor(monitor):43:monitor] Monitor:
> > starting gsyncd worker
> [...]
> > [2011-05-16 13:28:59.547034] I [master:191:crawl] GMaster: primary
> > master with volume id 28521f8f-49d3-4e2a-b984-f664f44f5289 ...
> > [2011-05-16 13:28:59.547180] D [master:199:crawl] GMaster: entering .
> > [2011-05-16 13:28:59.548289] D [repce:131:push] RepceClient: call
> > 10888:47702589471600:1305545339.55 xtime('.',
> > '28521f8f-49d3-4e2a-b984-f664f44f5289') ...
> > [2011-05-16 13:28:59.596978] E [syncdutils:131:log_raise_exception]
> > <top>: FAIL:
> > Traceback (most recent call last):
> > File "/usr/local/libexec/glusterfs/python/syncdaemon/syncdutils.py",
> > line 152, in twrap
> > tf(*aa)
> > File "/usr/local/libexec/glusterfs/python/syncdaemon/repce.py", line
> > 118, in listen
> > rid, exc, res = recv(self.inf)
> > File "/usr/local/libexec/glusterfs/python/syncdaemon/repce.py", line 42,
> > in recv
> > return pickle.load(inf)
> > EOFError
> >
> >
> > Does anyone already got those errors ?
>
> This means slave gsyncd instance could not properly start up. To debug
> this further, we need to see the slave side logs. In your case, the
> following commands will set a debug log level for the slave (takes
> effect if done before starting the geo-replication session) and locate
> its log file:
>
> # gluster volume geo-replication /soft/venus config log-level DEBUG
> # gluster volume geo-replication /soft/venus config log-file
>
> The output of the latter will contain an unresolved parameter
> ${session-owner}. To get its actual value, run
>
> # gluster volume geo-replication athena /soft/venus config session-owner
>
> -- please post the content of the actual log file, path to which you get
> after the substitution. (Also, cf.
>
> http://www.gluster.com/community/documentation/index.php/Gluster_3.2:_Configuring_Geo-replication
>
> , slave-side logs are illustrated there.)
>
> Csaba
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20110517/b6df1692/attachment.html>
More information about the Gluster-users
mailing list