search for: szalbot

...fsd, but when the 42 > second timeout goes into effect, it gets paused and I have to go into > RHEVM to un-pause it. > > Diego > > On Fri, Sep 8, 2017 at 7:53 AM, Gandalf Corvotempesta > <gandalf.corvotempesta at gmail.com> wrote: >> 2017-09-08 13:44 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: >>> I did not test SIGKILL because I suppose if graceful exit is bad, SIGKILL >>> will be as well. This assumption might be wrong. So I will test it. It would >>> be interesting to see client to work in case of crash (SIGKILL) and not i...

2017-09-08 13:44 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: > I did not test SIGKILL because I suppose if graceful exit is bad, SIGKILL > will be as well. This assumption might be wrong. So I will test it. It would > be interesting to see client to work in case of crash (SIGKILL) and not in > case of graceful...

...usr/local/etc/dovecot-postfix-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-postfix-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 384 user: postfix group: postfix Many thanks for your suggestions! Zbigniew Szalbot

2017-09-08 13:07 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: > OK, so killall seems to be ok after several attempts i.e. iops do not stop > on VM. Reboot caused I/O errors after maybe 20 seconds since issuing the > command. I will check the servers console during reboot to see if the VM > errors appear just af...

...-only and dmesg contained I/O errors. This did not happen in the past while following the same upgrade procedure. Documentation mentions only upgrades to higher minor version. Is there a recommended way to upgrade or did I do something wrong that should be avoided? Thanks for any suggestion Pavel Szalbot

2017-09-08 13:21 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: > Gandalf, isn't possible server hard-crash too much? I mean if reboot > reliably kills the VM, there is no doubt network crash or poweroff > will as well. IIUP, the only way to keep I/O running is to gracefully exiting glusterfsd. killall should se...

...ng timeout value down from 42 seconds. I think it was mentioned that low ping timeout settings could lead to high cpu loads with many clients trying to reconnect if a short timeout was set. This is all hearsay, so the experts should explain it better... ? Diego On Sep 8, 2017 6:50 AM, "Pavel Szalbot" <pavel.szalbot at gmail.com> wrote: > On Fri, Sep 8, 2017 at 12:48 PM, Gandalf Corvotempesta > <gandalf.corvotempesta at gmail.com> wrote: > > I think this should be considered a bug > > If you have a server crash, glusterfsd process obviously doesn't exit &...

2017-09-08 14:11 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: > Gandalf, SIGKILL (killall -9 glusterfsd) did not stop I/O after few > minutes. SIGTERM on the other hand causes crash, but this time it is > not read-only remount, but around 10 IOPS tops and 2 IOPS on average. > -ps So, seems to be reliable to ser...

...rted doing something new. > check gluster logs for more information. > > > > -- > > Respectfully > *Mahdi A. Mahdi* > > ------------------------------ > *From:* gluster-users-bounces at gluster.org <gluster-users-bounces@ > gluster.org> on behalf of Pavel Szalbot <pavel.szalbot at gmail.com> > *Sent:* Monday, July 10, 2017 7:52:10 PM > *To:* gluster-users > *Subject:* [Gluster-users] Upgrading Gluster revision (3.8.12 to 3.8.13) > caused underlying VM fs corruption > > Hi, > > is there a recommended way to upgrade Gluster clust...

...monitor healing process and logs, after completion proceed to the other node" check gluster logs for more information. -- Respectfully Mahdi A. Mahdi ________________________________ From: gluster-users-bounces at gluster.org <gluster-users-bounces at gluster.org> on behalf of Pavel Szalbot <pavel.szalbot at gmail.com> Sent: Monday, July 10, 2017 7:52:10 PM To: gluster-users Subject: [Gluster-users] Upgrading Gluster revision (3.8.12 to 3.8.13) caused underlying VM fs corruption Hi, is there a recommended way to upgrade Gluster cluster when upgrading to newer revision? I exper...

Sorry to have bothered - just read the updating file...! I should have let the upgrading process remove the dovecot user... Warm regards, ZS ---------------------------- Original Message ---------------------------- Subject: wrong dovecot GID while upgrading From: "Zbigniew Szalbot" <zbyszek at szalbot.homedns.org> Date: Sat, February 17, 2007 21:10 To: dovecot at dovecot.org -------------------------------------------------------------------------- Hello, I tried to upgrade dovecot from 1.0.rc7 to rc22 but I got this error at the end of the upgrade proce...

On Fri, Sep 8, 2017 at 12:48 PM, Gandalf Corvotempesta <gandalf.corvotempesta at gmail.com> wrote: > 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 ? I agree with you completely in this.

...; seconds. I think it was mentioned that low ping timeout settings could lead > to high cpu loads with many clients trying to reconnect if a short timeout > was set. This is all hearsay, so the experts should explain it better... ? > > Diego > > On Sep 8, 2017 6:50 AM, "Pavel Szalbot" <pavel.szalbot at gmail.com> wrote: > >> On Fri, Sep 8, 2017 at 12:48 PM, Gandalf Corvotempesta >> <gandalf.corvotempesta at gmail.com> wrote: >> > I think this should be considered a bug >> > If you have a server crash, glusterfsd process obviousl...

...ility of my hardware/network. But if Diego is able to reproduce the "reboot crash", my doubts of hardware/network problems are close to none. -ps On Fri, Sep 8, 2017 at 1:11 PM, Gandalf Corvotempesta <gandalf.corvotempesta at gmail.com> wrote: > 2017-09-08 13:07 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: >> >> OK, so killall seems to be ok after several attempts i.e. iops do not stop >> on VM. Reboot caused I/O errors after maybe 20 seconds since issuing the >> command. I will check the servers console during reboot to see if the VM >&g...

On Sep 8, 2017 13:36, "Gandalf Corvotempesta" < gandalf.corvotempesta at gmail.com> wrote: 2017-09-08 13:21 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: > Gandalf, isn't possible server hard-crash too much? I mean if reboot > reliably kills the VM, there is no doubt network crash or poweroff > will as well. IIUP, the only way to keep I/O running is to gracefully exiting glusterfsd. No, even killal...

...server VM is OK with killall glusterfsd, but when the 42 second timeout goes into effect, it gets paused and I have to go into RHEVM to un-pause it. Diego On Fri, Sep 8, 2017 at 7:53 AM, Gandalf Corvotempesta <gandalf.corvotempesta at gmail.com> wrote: > 2017-09-08 13:44 GMT+02:00 Pavel Szalbot <pavel.szalbot at gmail.com>: >> I did not test SIGKILL because I suppose if graceful exit is bad, SIGKILL >> will be as well. This assumption might be wrong. So I will test it. It would >> be interesting to see client to work in case of crash (SIGKILL) and not in >> c...

On Fri, Sep 8, 2017 at 5:56 AM, Pavel Szalbot <pavel.szalbot at gmail.com> wrote: > 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. >...

...local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: root group: wheel Thank you for pointers as to what to do to fix that warning. Zbigniew Szalbot

True but to work your way into that problem with replica 3 is a lot harder to achieve than with just replica 2 + arbiter. On 7 September 2017 at 14:06, Pavel Szalbot <pavel.szalbot at gmail.com> wrote: > Hi Neil, docs mention two live nodes of replica 3 blaming each other and > refusing to do IO. > > https://gluster.readthedocs.io/en/latest/Administrator% > 20Guide/Split%20brain%20and%20ways%20to%20deal%20with% > 20it/#1-replica-3-volum...

...rar.net> wrote: > What he is saying is that, on a two node volume, upgrading a node will > cause the volume to go down. That's nothing weird, you really should use > 3 nodes. > > On Wed, Aug 23, 2017 at 06:51:55PM +0200, Gionatan Danti wrote: >> Il 23-08-2017 18:14 Pavel Szalbot ha scritto: >> > Hi, after many VM crashes during upgrades of Gluster, losing network >> > connectivity on one node etc. I would advise running replica 2 with >> > arbiter. >> >> Hi Pavel, this is bad news :( >> So, in your case at least, Gluster was not...