Open madmax01 opened 1 year ago
just as info.. this crash happens started with 10.2 (10.1 was fine and never crashed) but each version after now includes 11 also crashes... specific change made after 10.1 makes bricks/glusterd unhappy after a while (10.2,10.3 + 11).. 10.4 not tested
Also strange is > it was configured as 2-way replication.. but command shows Distributed-Replicate which is another fault
Any News on the crash and on the Distributed-replicate where it should be replicated. Other user already dedicated opend a thread for 2nd issue and no answer as well on that one.
Same issue for me. Downgraded to 10.4 gluster on ubuntu 20.04 for now.
Description of problem: i got on 13.04 "all bricks down" issue. Glusterd Services are up (and green - no red alert). Network is up and responsive. Firewalld and selinux are not activ
The exact command to reproduce the issue: gluster volume status (to check brick status) and i see for both "N"
The full output of the command that failed:
Expected results: Y
Mandatory info: - The output of the
gluster volume info
command:- The output of the
gluster volume status
command:- The output of the
gluster volume heal
command: both bricks down (not able to fetch volfile from glusterd**- Provide logs present on following locations of client and server nodes - https://we.tl/t-vhRe9vteni
**- Is there any crash ? Provide the backtrace and coredump here is the coredump (don't know about backtrace) its alma 8.7 simple downstream of RH https://we.tl/t-ouj08o13Xm
Additional info:
- The operating system / glusterfs version: AlmaLinux release 8.7 (Stone Smilodon) / 11.0
Note: Please hide any confidential data which you don't want to share in public like IP address, file name, hostname or any other configuration