Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes

, and finally start the Gluster server. Please let me know if this process can be optimized, I will be happy to do so. Many thanks, Anant From: Strahil Nikolov Sent: 24 February 2024 12:33 PM To: Anant Saraswat Cc: gluster-users@gluster.org Subject: Re: [Gluster

Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes

; Anant Saraswat Cc: ronny.adse...@amazinginternet.com ; gluster-users@gluster.org Subject: Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Well, you prepare the host for shutdown

Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes

and impacts containers accessing this volume via bind. Thanks, Anant From: Strahil Nikolov Sent: 16 February 2024 3:51 PM To: Anant Saraswat ; Aravinda Cc: ronny.adse...@amazinginternet.com ; gluster-users@gluster.org Subject: Re: [Gluster-users] Graceful shutdown

Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes

. From: Aravinda Sent: 16 February 2024 12:36 PM To: Anant Saraswat Cc: ronny.adse...@amazinginternet.com ; gluster-users@gluster.org ; Strahil Nikolov Subject: Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes EXTERNAL: Do not click links or open attachments if you do

Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes

Hello Everyone, We are mounting this external Gluster volume (dc.local:/docker_config) for docker configuration on one of the Gluster servers. When I ran the stop-all-gluster-processes.sh script, I wanted to stop all gluster server-related processes on the server, but not to unmount the

Re: [Gluster-users] geo-replication {error=12} on one primary node

Hi @Stefan Kania, Please try to enable the geo-replication debug logs using the following command on the primary server, and recheck or resend the logs. gluster volume geo-replication privol01 geobenutzer@s01.gluster::secvol01 config log-level DEBUG​ Thanks,

Re: [Gluster-users] __Geo-replication status is getting Faulty after few seconds

extended to Aravinda, Strahil, and Diego. Have a great evening. Many thanks, Anant From: Aravinda Sent: 09 February 2024 5:33 PM To: Anant Saraswat Cc: Diego Zuccato ; gluster-users@gluster.org ; Strahil Nikolov Subject: Re: [Gluster-users] __Geo-replication

Re: [Gluster-users] __Geo-replication status is getting Faulty after few seconds

4-4dee-9561-bbc57e4aaf10 -rw-r--r-- 2 root root 40212 Jan 22 15:06 1bdb4239-5823-415b-951f-ce315a45492b Please check the attached CHANGELOG file for the given gfid. Many thanks, Anant From: Aravinda Sent: 09 February 2024 5:06 PM To: Anant Saraswat Cc:

Re: [Gluster-users] __Geo-replication status is getting Faulty after few seconds

regards, Anant From: Aravinda Sent: 09 February 2024 4:39 PM To: Anant Saraswat Cc: Diego Zuccato ; gluster-users@gluster.org ; Strahil Nikolov Subject: Re: [Gluster-users] __Geo-replication status is getting Faulty after few seconds EXTERNAL: Do not click links or open at

Re: [Gluster-users] __Geo-replication status is getting Faulty after few seconds

quot; to master2 and master3 nodes? Many thanks, Anant From: Strahil Nikolov Sent: 09 February 2024 5:28 AM To: Anant Saraswat ; Diego Zuccato ; gluster-users@gluster.org ; Aravinda Vishwanathapura Subject: Re: [Gluster-users] __Geo-replication status is getting Faulty after few seconds EX

Re: [Gluster-users] __Geo-replication status is getting Faulty after few seconds

b0-ccbcbdc4baa8' [2024-02-07 22:37:37.344426] I [monitor(monitor):228:monitor] Monitor: worker died in startup phase [{brick=/opt/tier1data2019/brick}] [2024-02-07 22:37:37.346601] I [gsyncdstatus(monitor):248:set_worker_status] GeorepStatus: Worker Status Change [{status=Faulty}] Thanks, Anant ___

Re: [Gluster-users] __Geo-replication status is getting Faulty after few seconds

t it does (quite often). *Probably* it's safe to just delete it, but wait for advice from more competent users. Diego Il 08/02/2024 13:42, Anant Saraswat ha scritto: > Hi Everyone, > > As I was getting "OSError: [Errno 107] Transport endpoint is not > connected: '.gfid/d53fad8f-84e

Re: [Gluster-users] __Geo-replication status is getting Faulty after few    seconds

aster nodes, or should I delete it from master1? Many thanks, Anant ____ From: Gluster-users on behalf of Anant Saraswat Sent: 08 February 2024 12:01 AM To: Aravinda Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] __Geo-replication status is getting Fau

Re: [Gluster-users] __Geo-replication status is getting Faulty after few    seconds

died in startup phase [{brick=/opt/tier1data2019/brick}] [2024-02-07 22:37:37.346601] I [gsyncdstatus(monitor):248:set_worker_status] GeorepStatus: Worker Status Change [{status=Faulty}] Thanks, Anant From: Aravinda Sent: 07 February 2024 2:54 PM To: Anant Sara

Re: [Gluster-users] __Geo-replication status is getting Faulty after few    seconds

Nikolov Sent: 07 February 2024 2:36 PM To: Anant Saraswat ; Aravinda Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] __Geo-replication status is getting Faulty after fewseconds EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Have you tried

Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

Thanks Hubert, I will try to run the script initially for future reference. From: Hu Bert Sent: 07 February 2024 6:55 AM To: Anant Saraswat Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping

Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

t;https://aka.ms/o0ukef> From: Hu Bert Sent: Monday, February 5, 2024 6:15 PM To: Anant Saraswat Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node. EXTERNAL: Do not click

[Gluster-users] Graceful shutdown doesn't stop all Gluster processes

Hello Everyone, I am using GlusterFS 9.4, and whenever we use the systemctl command to stop the Gluster server, it leaves many Gluster processes running. So, I just want to check how to shut down the Gluster server in a graceful manner. Is there any specific sequence or trick I need to

[Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

tier1data clients FAILED: Commit failed on master1. Error: Unable to decode brick op response. Could anyone recommend a potential solution for this? Thanks, Anant Anant Saraswat DevOps Lead IT | Technology Blueprint Ltd. [mobilePhone] +44-8450047142 (5020) | +91-9818761614 [emailAddress

Re: [Gluster-users] Geo-replication status is getting Faulty after few    seconds

hanks, Anant From: Strahil Nikolov Sent: 31 January 2024 4:18 PM To: Anant Saraswat ; Aravinda Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] Geo-replication status is getting Faulty after few seconds EXTERNAL: Do not click links or open attachments if you do not recognize

Re: [Gluster-users] Geo-replication status is getting Faulty after few seconds

ge.c:7068:fini] 0-fuse: Closing fuse connection to '/tmp/gsyncd-aux-mount-c8c41k2k'. Can anyone suggest how can I find the reason of getting these disconnect requests from master1 or what shall I check next? Many thanks, A From: Gluster-users on behalf of Anant

Re: [Gluster-users] Geo-replication status is getting Faulty after few seconds

__ From: Gluster-users on behalf of Anant Saraswat Sent: 29 January 2024 12:20 AM To: gluster-users@gluster.org ; Strahil Nikolov Subject: Re: [Gluster-users] Geo-replication status is getting Faulty after few seconds EXTERNAL: Do not click links or open attachments if y

Re: [Gluster-users] Geo-replication status is getting Faulty after few seconds

/secret.pem root@drtier1data Last login: Mon Jan 29 00:14:41 2024 from [root@drtier1data ~]# Thanks, Anant From: Strahil Nikolov Sent: 28 January 2024 10:07 PM To: Anant Saraswat ; gluster-users@gluster.org Subject: Re: [Gluster-users] Geo-replication status is getting

Re: [Gluster-users] Geo-replication status is getting Faulty after few seconds

:connect_remote] SSH: SSH connection between master and slave established. [{duration=1.6981}] [2024-01-28 13:48:34.92130] I [resource(worker /opt/tier1data2019/brick):1116:connect] GLUSTER: Mounting gluster volume locally... Thanks, Anant From: Anant Saraswat Sent: 28

Re: [Gluster-users] Geo-replication status is getting Faulty after few seconds

uto -S /tmp/gsyncd-aux-ssh-0exuoeg7/75785990b3233f5dbbab9f43cc3ed895.sock drtier1data:/proc/553418/cwd}, {error=3}] Many thanks, Anant From: Strahil Nikolov Sent: 27 January 2024 5:25 AM To: gluster-users@gluster.org ; Anant Saraswat Subject: Re: [Gluster-users] Geo-

Re: [Gluster-users] Geo-replication status is getting Faulty after few seconds

From: Gluster-users on behalf of Anant Saraswat Sent: 22 January 2024 9:00 PM To: gluster-users@gluster.org Subject: [Gluster-users] Geo-replication status is getting Faulty after few seconds EXTERNAL: Do not click links or open attachments if you do not recognize

[Gluster-users] 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

Re: [Gluster-users] Gluster Geo replication

Hi, You simply need to enable port 22 on the geo-replication slave side. This will allow the master node to establish an SSH connection with the slave server and transfer data securely over SSH. Thanks, Anant From: Gluster-users on behalf of dev devops

Re: [Gluster-users] Big problems after update to 9.6

Hi David, It seems like a network issue to me, As it's unable to connect the other node and getting timeout. Few things you can check- * Check the /etc/hosts file on both the servers and make sure it has the correct IP of the other node. * Are you binding gluster on any specific IP,