[Bugs] [Bug 1506487] glusterfs / glusterfsd processes may not start properly upon reboot/restart

bugzilla at redhat.com bugzilla at redhat.com
Wed Sep 5 13:59:15 UTC 2018


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

Sonal <sarora at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sarora at redhat.com



--- Comment #20 from Sonal <sarora at redhat.com> ---
Hi Milind,

(In reply to Milind Changire from comment #3)
> Sylvain,
> 1. Are you using Gluster for Virtual Machine image storage ?
> 2. Are Gluster nodes running on bare metal ?
> 3. Are you using arbiter bricks ?
> 
> If possible, could you share TRACE level logs of one of the brick that dies
> after a reboot ?
> 
> To set log-level to TRACE:
> # gluster volume set <vol> diagnostics.brick-log-level TRACE
> 
> To reset log-level to default (INFO), repeat the above command with INFO in
> place of TRACE.

One of my customer is facing the same issue.
He was getting `Transport endpoint not connected` for various bricks. On
forcefully restarting the volume, bricks came up but after sometime gluster
volume status showed down for those bricks. But brick process is up.

Logs of one of the brick (not sure if these brick logs are latest, checking
with customer) :

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


More information about the Bugs mailing list