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

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1790670

Sanju <srakonde at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |NOTABUG
        Last Closed|                            |2020-01-14 09:30:56



--- Comment #4 from Sanju <srakonde at redhat.com> ---
>From the comment 2:

Thread 1 (Thread 0x7fe147a7b700 (LWP 143)):
#0  0x00007fe1470740b8 in ?? () from /lib64/libgcc_s.so.1
#1  0x00007fe147074fb9 in _Unwind_Backtrace () from /lib64/libgcc_s.so.1
#2  0x00007fe14f046a56 in backtrace () from /lib64/libc.so.6
#3  0x00007fe1509277ff in _gf_msg_backtrace_nomem () from
/lib64/libglusterfs.so.0
#4  0x00007fe150932234 in gf_print_trace () from /lib64/libglusterfs.so.0
#5  <signal handler called>
#6  0x00007fe1470740b8 in ?? () from /lib64/libgcc_s.so.1
#7  0x00007fe147074fb9 in _Unwind_Backtrace () from /lib64/libgcc_s.so.1
#8  0x00007fe14f046a56 in backtrace () from /lib64/libc.so.6
#9  0x00007fe14efaaea4 in __libc_message () from /lib64/libc.so.6
#10 0x00007fe14f04a527 in __fortify_fail () from /lib64/libc.so.6
#11 0x00007fe14f04a4e2 in __stack_chk_fail () from /lib64/libc.so.6
#12 0x00007fe14ac94ab5 in glusterd_store_perform_peer_store () from
/usr/lib64/glusterfs/7.1/xlator/mgmt/glusterd.so

We are seeing no memory error here:
#3  0x00007fe1509277ff in _gf_msg_backtrace_nomem ()

This might have caused the peer probe to fail because peer probe tries write
into the store /var/lib/glusterd/ about the new peer. As there is no memory
available, glusterd has crashed.

Closing this as not a bug. Please feel free to re-open if you hit this issue
when you have memory available as well.

Thanks,
Sanju

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