similar to: Failure while upgrading gluster to 3.10.1

Hello Atin, I've gotten around to this and was able to get upgrade done using 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't working well. On 3.11 though I notice that gluster/nfs is really made optional and nfs-ganesha is being recommended. We have plans to switch to nfs-ganesha on new clusters but would like to have glusterfs-gnfs on existing clusters so a seamless upgrade

On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: > Hello Atin, > > I've gotten around to this and was able to get upgrade done using 3.7.0 > before moving to 3.11. For some reason 3.7.9 wasn't working well. > > On 3.11 though I notice that gluster/nfs is really made optional and > nfs-ganesha is being recommended. We have plans to

On 07/03/2017 04:34 AM, Atin Mukherjee wrote: > > On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: > > Hello Atin, > > I've gotten around to this and was able to get upgrade done using > 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't working well. > > On 3.11 though I notice that gluster/nfs is really

Hi Kaleb, Thanks, this refers to 3.11.x On Mon, Jul 3, 2017 at 4:16 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > On 07/03/2017 06:29 AM, Kaleb S. KEITHLEY wrote: > >> On 07/03/2017 04:34 AM, Atin Mukherjee wrote: >> >>> >>> On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: >>> >>> Hello Atin,

On 07/03/2017 06:29 AM, Kaleb S. KEITHLEY wrote: > On 07/03/2017 04:34 AM, Atin Mukherjee wrote: >> >> On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: >> >> Hello Atin, >> >> I've gotten around to this and was able to get upgrade done using >> 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't

Sir, Kindlly Guide me how to get the R CELFILES. I have install R but I cannat asses the command: Data <- ReadAffy() and I got the error: Error in AllButCelsForReadAffy(..., filenames = filenames, widget = widget, : No cel filennames specified and no cel files in specified directory:C:/Documents and Settings/pawan.k/Desktop. Wit regds, Pawan ________________________________ This e-mail

Hello Everybody, I have pretty basic question abut REXML. I want to put the String "John doe" in titles array, if attribute name is equal to "93". Please see the code below. I could not find how to do it.. any help would be very appriciated. Here is the XML i am trying to parse <entrydata columnnumber="2" name="93"> <text>John

Good morning. We have a 6 node cluster. 3 nodes are participating in a replica 3 volume. Naming convention: xx01 - 3 nodes participating in ovirt_vol xx02 - 3 nodes NOT particpating in ovirt_vol Last week, restarted glusterd on each node in cluster to update (one at a time). The three xx01 nodes all show the following in glusterd.log: [2018-02-26 14:31:47.330670] E

https://bugzilla.mindrot.org/show_bug.cgi?id=3666 Bug ID: 3666 Summary: sshd crash Product: Portable OpenSSH Version: 8.2p1 Hardware: Other OS: Linux Status: NEW Severity: critical Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org Reporter:

hello friends friend i had just finished my chapters of asterisk. ill be configuring asterisk in for home for r/d purpose. i am having p4 machine with 1 GB RAM, ill be configuring asterisk on centos 5.3, the only doubt which i am having is which hardware ill have to buy to configure asterisk. i think analog card ? plz clear my doubt. n be with me from beginning till end, of the journey of

Hi! Please see bellow. Note that web1.dasilva.network is the address of the local machine where one of the bricks is installed and that ties to mount. [2017-08-20 20:30:40.359236] I [MSGID: 100030] [glusterfsd.c:2476:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.11.2 (args: /usr/sbin/glusterd -p /var/run/glusterd.pid) [2017-08-20 20:30:40.973249] I [MSGID: 106478]

On Mon, Aug 21, 2017 at 2:49 AM, Cesar da Silva <thunderlight1 at gmail.com> wrote: > Hi! > I am having same issue but I am running Ubuntu v16.04. > It does not mount during boot, but works if I mount it manually. I am > running the Gluster-server on the same machines (3 machines) > Here is the /tc/fstab file > > /dev/sdb1 /data/gluster ext4 defaults 0 0 > >

Hi, In my LAN Iam trying to make following setup: - All the traffic generated by 10.0.2.1 should go to 10.0.2.11, If the destination of this traffic is internet than it should be placed on its interface eth1. Outgoing traffic on eth1 should be shaped.For this I am using fw filters and cbq. _______ 10.0.2.1 -------> 10.0.2.11(eth0 )----| A

Please stop emailing me personally. If no one replies to a post, it means that everyone is busy or they think you should read through the documentation before posting. If you can't figure out simple things like Music on hold from the documentation, then i dont think VOIP is for you. -----Original Message----- From: asterisk at opensourcesolution.in [mailto:asterisk at opensourcesolution.in]

The issue of I/O stopping may also be with glusterfsd not being properly killed before rebooting the server. For example in RHEL 7.4 with official Gluster 3.8.4, the glusterd service does *not* stop glusterfsd when you run systemctl stop glusterd So give this a try on the nose you wish to reboot: 1. Stop glusterd 2. Check if glusterfsd processes are still running. If they are, use: killall

Hi Diego, indeed glusterfsd processes are runnin and it is the reason I do server reboot instead of systemctl glusterd stop. Is killall different from reboot in a way glusterfsd processes are terminated in CentOS (init 1?)? However I will try this and let you know. -ps On Fri, Sep 8, 2017 at 12:19 PM, Diego Remolina <dijuremo at gmail.com> wrote: > The issue of I/O stopping may also

This is exactly the problem, Systemctl stop glusterd does *not* kill the brick processes. On CentOS with gluster 3.10.x there is also a service, meant to only stop glusterfsd (brick processes). I think the reboot process may not be properly stopping glusterfsd or network or firewall may be stopped before glusterfsd and so the nodes go into the long timeout. Once again , in my case a simple

If your VMs use ext4 also check this: https://joejulian.name/blog/keeping-your-vms-from-going- read-only-when-encountering-a-ping-timeout-in-glusterfs/ I asked him what to do for VMs using XFS and he said he could not find a fix (setting to change) for those. HTH, Diego On Sep 8, 2017 6:19 AM, "Diego Remolina" <dijuremo at gmail.com> wrote: > The issue of I/O stopping may

This is the qemu log of instance: [2017-09-08 09:31:48.381077] C [rpc-clnt-ping.c:160:rpc_clnt_ping_timer_expired] 0-gv_openstack_1-client-1: server 10.0.1.202:49152 has not responded in the last 1 seconds, disconnecting. [2017-09-08 09:31:48.382411] E [rpc-clnt.c:365:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fbcadb09e8b] (-->

I think this should be considered a bug If you have a server crash, glusterfsd process obviously doesn't exit properly and thus this could least to IO stop ? And server crashes are the main reason to use a redundant filesystem like gluster Il 8 set 2017 12:43 PM, "Diego Remolina" <dijuremo at gmail.com> ha scritto: This is exactly the problem, Systemctl stop glusterd does