[Bugs] [Bug 1592258] Gluster brick will not come back up online

[bugzilla at redhat.com]

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

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(stefan.luteijn at kp
                   |                            |n.com)



--- Comment #5 from Atin Mukherjee <amukherj at redhat.com> ---
This seems to me that the pidfile had a pid which was pointing to some other
running process (it may be a other gluster process or something completely
different). Ideally the pid allocation is forward moving process and
possibility of having pid clash in a running environment is vert very rare
until and unless the system has exhausted the upper bound of the pid limit and
starts scanning from the scratch. Do you see this happening frequently, if so
I'd definitely request you to capture the exact pid number from the brick
pidfile and then do a 'ps aux | grep <pid> to see what process is this
(ofcourse I'd require the brick name). Also what's the output of gluster volume
status at the moment and if we create a new dummy volume then, what pid does
the new brick pick up?

If you can help me with this information I guess we should be able to narrow
down this issue.

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