Displaying 8 results from an estimated 8 matches for "connect_remot".
Did you mean:
connect_remote
2017 Sep 29
1
Gluster geo replication volume is faulty
...gfs/brick2/gv0):271:finalize]
<top>: exiting.
[2017-09-29 15:53:30.105407] I [monitor(monitor):280:monitor] Monitor:
starting gsyncd worker brick=/gfs/brick1/gv0
slave_node=ssh://geo-rep-user at gfs6:gluster://localhost:gfsvol_rep
[2017-09-29 15:53:30.232007] I
[resource(/gfs/brick1/gv0):1772:connect_remote] SSH: Initializing SSH
connection between master and slave...
[2017-09-29 15:53:30.232738] I
[changelogagent(/gfs/brick1/gv0):73:__init__] ChangelogAgent: Agent
listining...
[2017-09-29 15:53:30.248094] I [monitor(monitor):363:monitor] Monitor:
worker died in startup phase brick=/gfs/brick2/gv0
[2...
2017 Oct 06
0
Gluster geo replication volume is faulty
...ze] <top>: exiting.
> [2017-09-29 15:53:30.105407] I [monitor(monitor):280:monitor] Monitor:
> starting gsyncd
> workerbrick=/gfs/brick1/gv0slave_node=ssh://geo-rep-user at gfs6:gluster://localhost:gfsvol_rep
> [2017-09-29 15:53:30.232007] I
> [resource(/gfs/brick1/gv0):1772:connect_remote] SSH: Initializing SSH
> connection between master and slave...
> [2017-09-29 15:53:30.232738] I
> [changelogagent(/gfs/brick1/gv0):73:__init__] ChangelogAgent: Agent
> listining...
> [2017-09-29 15:53:30.248094] I [monitor(monitor):363:monitor] Monitor:
> worker died in star...
2018 Mar 06
1
geo replication
...brick=/gfs/testtomcat/mount slave_node=ssh://root at stogfstest11:gluster://localhost:testtomcat
[2018-03-06 08:32:46.961122] I [changelogagent(/gfs/testtomcat/mount):73:__init__] ChangelogAgent: Agent listining...
[2018-03-06 08:32:46.962470] I [resource(/gfs/testtomcat/mount):1771:connect_remote] SSH: Initializing SSH connection between master and slave...
[2018-03-06 08:32:48.515974] I [resource(/gfs/testtomcat/mount):1778:connect_remote] SSH: SSH connection between master and slave established. duration=1.5530
[2018-03-06 08:32:48.516247] I [resource(/gfs/testtomcat/mount):1493:...
2024 Jan 24
1
Geo-replication status is getting Faulty after few seconds
...tus] GeorepStatus: Worker Status Change [{status=Initializing...}]
[2024-01-24 19:51:24.81020] I [monitor(monitor):160:monitor] Monitor: starting gsyncd worker [{brick=/opt/tier1data2019/brick}, {slave_node=drtier1data}]
[2024-01-24 19:51:24.158021] I [resource(worker /opt/tier1data2019/brick):1387:connect_remote] SSH: Initializing SSH connection between master and slave...
[2024-01-24 19:51:25.951998] I [resource(worker /opt/tier1data2019/brick):1436:connect_remote] SSH: SSH connection between master and slave established. [{duration=1.7938}]
[2024-01-24 19:51:25.952292] I [resource(worker /opt/tier1data2...
2024 Jan 27
1
Geo-replication status is getting Faulty after few seconds
...s] GeorepStatus: Worker Status Change [{status=Initializing...}]
[2024-01-24 19:51:24.81020] I [monitor(monitor):160:monitor] Monitor: starting gsyncd worker [{brick=/opt/tier1data2019/brick}, {slave_node=drtier1data}]
[2024-01-24 19:51:24.158021] I [resource(worker /opt/tier1data2019/brick):1387:connect_remote] SSH: Initializing SSH connection between master and slave...
[2024-01-24 19:51:25.951998] I [resource(worker /opt/tier1data2019/brick):1436:connect_remote] SSH: SSH connection between master and slave established. [{duration=1.7938}]
[2024-01-24 19:51:25.952292] I [resource(worker /opt/tier1dat...
2018 Jul 13
2
Upgrade to 4.1.1 geo-replication does not work
...the geo-replication up and running again.
Best regards
Marcus Peders?n
Part of geo-replication log from master node:
[2018-07-11 18:42:48.941760] I [changelogagent(/urd-gds/gluster):73:__init__] ChangelogAgent: Agent listining...
[2018-07-11 18:42:48.947567] I [resource(/urd-gds/gluster):1780:connect_remote] SSH: Initializing SSH connection between master and slave...
[2018-07-11 18:42:49.363514] E [syncdutils(/urd-gds/gluster):304:log_raise_exception] <top>: connection to peer is broken
[2018-07-11 18:42:49.364279] E [resource(/urd-gds/gluster):210:errlog] Popen: command returned error cmd=...
2024 Jan 27
1
Geo-replication status is getting Faulty after few seconds
...s] GeorepStatus: Worker Status Change [{status=Initializing...}]
[2024-01-24 19:51:24.81020] I [monitor(monitor):160:monitor] Monitor: starting gsyncd worker [{brick=/opt/tier1data2019/brick}, {slave_node=drtier1data}]
[2024-01-24 19:51:24.158021] I [resource(worker /opt/tier1data2019/brick):1387:connect_remote] SSH: Initializing SSH connection between master and slave...
[2024-01-24 19:51:25.951998] I [resource(worker /opt/tier1data2019/brick):1436:connect_remote] SSH: SSH connection between master and slave established. [{duration=1.7938}]
[2024-01-24 19:51:25.952292] I [resource(worker /opt/tier1dat...
2024 Jan 22
1
Geo-replication status is getting Faulty after few seconds
Hi There,
We have a Gluster setup with three master nodes in replicated mode and one slave node with geo-replication.
# gluster volume info
Volume Name: tier1data
Type: Replicate
Volume ID: 93c45c14-f700-4d50-962b-7653be471e27
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: master1:/opt/tier1data2019/brick
Brick2: master2:/opt/tier1data2019/brick