[Bugs] [Bug 1727682] Upgrade from older versions 3.12.15 and 5.5 to gluster 6.3-1 fails - bricks become offline

[bugzilla at redhat.com]

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

Amgad <amgad.saleh at nokia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(amgad.saleh at nokia |
                   |.com)                       |



--- Comment #10 from Amgad <amgad.saleh at nokia.com> ---
Hi Sanju:

For 1. The output was showing a different port every time glusterd is started
(not 24007) till Amar advised to added explicitly in the 
/etc/glusterfs/glusterd.vol:
...
     option transport.socket.listen-port 24007
...
Then it started with 24007. It's supposed to be the default


For 2. after the failure, were not able to restart glusterd using systemctl
        Getting the following error:

[root at gfs ~]# systemctl restart glusterd
Job for glusterd.service failed because the control process exited with error
code. See "systemctl status glusterd.service" and "journalctl -xe" for details.
[root at gfs ~]# 

[root at gfs-bcmt-1906-control-02 ~]# systemctl -l  status glusterd.service
â glusterd.service - GlusterFS, a clustered file-system server
   Loaded: loaded (/etc/systemd/system/glusterd.service; enabled; vendor
preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2019-07-12
16:08:43 UTC; 2s ago
  Process: 12324 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid
--log-level $LOG_LEVEL $GLUSTERD_OPTIONS (code=exited, status=1/FAILURE)
    Tasks: 0
   Memory: 0B (limit: 3.8G)

Jul 12 16:08:43 gfs-bcmt-1906-control-02 systemd[1]: Failed to start GlusterFS,
a clustered file-system server.
Jul 12 16:08:43 gfs-bcmt-1906-control-02 systemd[1]: Unit glusterd.service
entered failed state.
Jul 12 16:08:43 gfs-bcmt-1906-control-02 systemd[1]: glusterd.service failed.

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