similar to: Letter

Hi Strahil, Yes, we mount the fuse to the physical host and then use bind mount to provide access to the container. The same physical host also runs the gluster server. Therefore, when we stop gluster using 'stop-all-gluster-processes.sh' on the physical host, it kills the fuse mount and impacts containers accessing this volume via bind. Thanks, Anant ________________________________

Well, you prepare the host for shutdown, right ? So why don't you setup systemd to start the container and shut it down before the bricks ? Best Regards, Strahil Nikolov ? ?????, 16 ???????? 2024 ?. ? 18:48:36 ?. ???????+2, Anant Saraswat <anant.saraswat at techblue.co.uk> ??????: Hi Strahil, Yes, we mount the fuse to the physical host and then use bind mount to

On 19/02/2020 18:55, Philippe LeCavalier wrote: > Just another test. Could I get a few replies please? > > Regards, Phil > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you are not the intended recipient, you are notified > that disclosing, copying, distributing or

Just another test. Could I get a few replies please? Regards, Phil This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly

On 19/02/2020 19:00, Rowland penny via samba wrote: > On 19/02/2020 18:55, Philippe LeCavalier wrote: >> Just another test. Could I get a few replies please? >> >> Regards, Phil >> This email and any files transmitted with it are confidential and >> intended solely for the use of the individual or entity to whom they >> are addressed. If you are not the

On 19/02/2020 19:05, Rowland penny via samba wrote: > On 19/02/2020 19:00, Rowland penny via samba wrote: >> On 19/02/2020 18:55, Philippe LeCavalier wrote: >>> Just another test. Could I get a few replies please? >>> >>> Regards, Phil >>> This email and any files transmitted with it are confidential and >>> intended solely for the use of the

Hi Anant, Do you use the fuse client in the container ?Wouldn't it be more reasonable to mount the fuse and then use bind mount to provide access to the container ? Best Regards,Strahil Nikolov On Fri, Feb 16, 2024 at 15:02, Anant Saraswat<anant.saraswat at techblue.co.uk> wrote: Okay, I understand. Yes, it would be beneficial to include an option for skipping the client

So I'm using the READ() application within an IVR, and having a strange issue, and wondering if anyone else has had this problem. When calling from an outside line, and entering the digits during the read() part of my dialplan, it's accepting some of the digits twice, though it's only keyed in once. When testing the dialplan internally, it accepts only the digits that I key in.

Dear experts, Quick quotation... I have a sendmail server behind the shorewall-2.1.7 server. I would like to do Port forwarding (DNAT) for clients on the internet, who need to access the mail server. Please let me know, which way is the most suitable to accomplish this; using following 2 types of configurations Setup - Internet -- > shorewall -- > sendmail

Okay, I understand. Yes, it would be beneficial to include an option for skipping the client processes. This way, we could utilize the 'stop-all-gluster-processes.sh' script with that option to stop the gluster server process while retaining the fuse mounts. ________________________________ From: Aravinda <aravinda at kadalu.tech> Sent: 16 February 2024 12:36 PM To: Anant Saraswat

Hi Strahil, In our setup, the Gluster brick comes from an iSCSI SAN storage and is then used as a brick on the Gluster server. To extend the brick, we stop the Gluster server, extend the logical volume (LV) on the SAN server, resize it on the host, mount the brick with the extended size, and finally start the Gluster server. Please let me know if this process can be optimized, I will be happy to

I need to set the content to 0 because actually is not using malloc(), it uses calloc() that does set the memory to 0. Best Regards --------------------------------------------- Helios Cuevas L?pez Embedded Software Engineer Castle Care-tech Ltd. First Floor, 6 Bracknell Beeches, Old Bracknell Lane West, Bracknell, Berkshire, RG12 7BW Office - 01344 469470 Direct Dial - 01344 469485 FAX - 01344

Hello Everyone, We have a replicated Gluster volume with three nodes, and we face a strange issue whenever we need to restart one of the nodes in this cluster. As per my understanding, if we shut down one node, the Gluster mount should smoothly connect to another remaining Gluster server and shouldn't create any issues. In our setup, when we stop Gluster on any of the nodes, we mostly get

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 <gluster-users-bounces at gluster.org> on behalf of dev devops <dev.devops12 at gmail.com> Sent: 31 October 2023 3:10 AM

funny guy!!! A BIG thank you to Bjorn and Rowland for his relentless patience and support. Regards, Phil This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents

I saw some of the heat about the $20 bounty earlier. So I don't want to put a low bounty out. Quote me a bounty, and I'll see if I can get it approved by management. :-) I'm in need of getting this bug fixed. Bug has all of the details, but basically 1.4.22 broke it all. I've waited as long as I can - hoping the bug would 'resolve itself' - but now I'm putting a

Hi All, I have run the following commands on master3, and that has added master3 to geo-replication. gluster system:: execute gsec_create gluster volume geo-replication tier1data drtier1data::drtier1data create push-pem force gluster volume geo-replication tier1data drtier1data::drtier1data stop gluster volume geo-replication tier1data drtier1data::drtier1data start Now I am able to start the

Hi Anant, i would first start checking if you can do ssh from all masters to the slave node.If you haven't setup a dedicated user for the session, then gluster is using root. Best Regards, Strahil Nikolov ? ?????, 26 ?????? 2024 ?. ? 18:07:59 ?. ???????+2, Anant Saraswat <anant.saraswat at techblue.co.uk> ??????: Hi All, I have run the following commands on master3,

Hi, normally, when we shut down or reboot one of the (server) nodes, we call the "stop-all-gluster-processes.sh" script. But i think you did that, right? Best regards, Hubert Am Mo., 5. Feb. 2024 um 13:35 Uhr schrieb Anant Saraswat < anant.saraswat at techblue.co.uk>: > Hello Everyone, > > We have a replicated Gluster volume with three nodes, and we face a >

I'm having a strange issue, and not really sure where to even begin to troubleshoot it. First let me explain that I have all agents setup locally ( local/100 at agents/n) A call will come in and ring to the agent. When the agent answers the call, they just hear a dial tone. Agent hangs up. Asterisk still shows the agent as 'in use' in queue status. And 'show channels'