[Bugs] [Bug 1790670] glusterd crashed when trying to add node

bugzilla at redhat.com bugzilla at redhat.com
Tue Jan 14 09:47:57 UTC 2020


Rick Pizzi <pizzi at leopardus.com> changed:

           What    |Removed                     |Added
             Status|CLOSED                      |NEW
         Resolution|NOTABUG                     |---
           Keywords|                            |Reopened

--- Comment #5 from Rick Pizzi <pizzi at leopardus.com> ---
I have put triple the memory in the POD (300M now) and the problem persists.

Besides, I don't think it is correct that an out of memory condition crashes
the glusterd daemon, it should just fail gracefully (malloc returns NULL, you
know, just trap that).

Again, it doesn't look like it is memory dependent to me. Also, previous node
was working fine with identical config, including memory.

I believe there is some sort of buffer overflow going on, as it is overwriting
the stack.

One thing that I have done is to change hostname of the previous node but this
did not create problem to other existing nodes, it's just the peer probe that

Can you please have another look? 

Thank you.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Bugs mailing list