Re: [Gluster-users] Gluster Periodic Brick Process Deaths

2020-01-14 Thread Nico van Royen
Verzonden: Maandag 13 januari 2020 12:20:29 Onderwerp: Re: [Gluster-users] Gluster Periodic Brick Process Deaths Hi Ben, we already identified the issue that caused crashes when gluster ports were scanned. The fix is present on 6.7 and 7.1, so if this was the reason for your problem, th

Re: [Gluster-users] Gluster Periodic Brick Process Deaths

2020-01-13 Thread Xavi Hernandez
Hi Ben, we already identified the issue that caused crashes when gluster ports were scanned. The fix is present on 6.7 and 7.1, so if this was the reason for your problem, those versions should help. Best regards, Xavi On Mon, Jan 13, 2020 at 11:57 AM Ben Tasker wrote: > Hi, > > Just an

Re: [Gluster-users] Gluster Periodic Brick Process Deaths

2020-01-13 Thread Ben Tasker
Hi, Just an update on this - we made our ACLs much, much stricter around gluster ports and to my knowledge haven't seen a brick death since. Ben On Wed, Dec 11, 2019 at 12:43 PM Ben Tasker wrote: > Hi Xavi, > > We don't that I'm explicitly aware of, *but* I can't rule it out as a >

Re: [Gluster-users] Gluster Periodic Brick Process Deaths

2019-12-11 Thread Ben Tasker
Hi Xavi, We don't that I'm explicitly aware of, *but* I can't rule it out as a probability as it's possible some of our partners do (some/most certainly have scans done as part of pentests fairly regularly). But, that does at least give me an avenue to pursue in the meantime, thanks! Ben On

Re: [Gluster-users] Gluster Periodic Brick Process Deaths

2019-12-11 Thread Xavi Hernandez
Hi Ben, I've recently seen some issues that seem similar to yours (based on the stack trace in the logs). Right now it seems that in these cases the problem is caused by some port scanning tool that triggers an unhandled condition. We are still investigating what is causing this to fix it as soon

[Gluster-users] Gluster Periodic Brick Process Deaths

2019-12-10 Thread Ben Tasker
Hi, A little while ago we had an issue with Gluster 6. As it was urgent we downgraded to Gluster 5.9 and it went away. Some boxes are now running 5.10 and the issue has come back. >From the operators point of view, the first you know about this is getting reports that the transport endpoint is