After a Host Reboot Glusterd Crashes and Doesn't Start.

Issue

• After a Gluster node reboots, glusterd is unable to start. Reviewing the file /var/log/glusterfs/glusterd.log the following messages are observed:

  [2019-10-11 23:12:30.410479] E [MSGID: 106187] [glusterd-store.c:4342:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore
  [2019-10-11 23:12:30.410532] E [MSGID: 101019]      [xlator.c:433:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again
  [2019-10-11 23:12:30.410543] E [graph.c:322:glusterfs_graph_init] 0-management: initializing translator failed
  [2019-10-11 23:12:30.410550] E [graph.c:661:glusterfs_graph_activate]   0-graph: init failed
  pending frames:
  patchset: git://git.gluster.com/glusterfs.git
  signal received: 11
  time of crash:
  2019-10-11 23:12:30
  configuration details:
  argp 1
  backtrace 1
  dlfcn 1
  libpthread 1
  llistxattr 1
  setfsid 1
  spinlock 1
  epoll.h 1
  xattr.h 1
  st_atim.tv_nsec 1
  package-string: glusterfs 3.7.9
  [2019-10-11 23:12:30.411083] W [glusterfsd.c:1251:cleanup_and_exit] (-->/usr/sbin/glusterd(glusterfs_volumes_init+0xfd) [0x7f0b2071936d] -->/usr/sbin/glusterd(glusterfs_process_volfp+0x172) [0x7f0b20719212] -->/usr/sbin/glusterd(cleanup_and_exit+0x6b) [0x7f0b2071878b] ) 0-: received signum (1), shutting down
  

• The above traces indicate that glusterdprocess has crashed. If the abrtd tool is installed, there should be a coredumpfile available at directory /var/tmp/abrt/ccpp-<date>. For further information about the abrtd service, please check Chapter 25 of the RHEL administration guide