At least for me, the latest few versions of this package will not run. I tried upgrading to 1:10.1-1 and the latest, 1:10.3-2, but have ultimately had to remain on 1:9.3-2, which continues to work for me and appears to be forward-compatible with 1:10.3-2.
The issue is unfortunately unclear. All I get is a coredump; here is my journalctl about this:
$this->bbcode_second_pass_code('', 'Dec 28 13:58:55 icarus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=_ msg='unit=systemd-coredump@3-830-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 28 13:58:55 icarus kernel: audit: type=1130 audit(1672257535.961:69): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=_ msg='unit=systemd-coredump@3-830-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 28 13:58:56 icarus systemd-coredump[831]: [] Process 827 (glusterd) of user 0 dumped core.
Stack trace of thread 827:
#0 0x00000000b6ee96c8 gf_io_run (libglusterfs.so.0 + 0x896c8)
ELF object binary architecture: ARM
Subject: Process 827 (glusterd) dumped core
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Process 827 (glusterd) crashed and dumped core.
This usually indicates a programming error in the crashing program and
should be reported to its vendor as a bug.
Dec 28 13:58:56 icarus systemd[1]: systemd-coredump@3-830-0.service: Deactivated successfully.
Subject: Unit succeeded
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit systemd-coredump@3-830-0.service has successfully entered the 'dead' state.
Dec 28 13:58:56 icarus kernel: audit: type=1131 audit(1672257536.661:70): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=_ msg='unit=systemd-coredump@3-830-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 28 13:58:56 icarus kernel: audit: type=1130 audit(1672257536.669:71): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=_ msg='unit=glusterd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Dec 28 13:58:56 icarus kernel: audit: type=1106 audit(1672257536.685:72): pid=823 uid=1001 auid=1001 ses=1 subj=_ msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Dec 28 13:58:56 icarus kernel: audit: type=1104 audit(1672257536.689:73): pid=823 uid=1001 auid=1001 ses=1 subj=_ msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Dec 28 13:58:56 icarus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=_ msg='unit=systemd-coredump@3-830-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 28 13:58:56 icarus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=_ msg='unit=glusterd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Dec 28 13:58:56 icarus audit[823]: USER_END pid=823 uid=1001 auid=1001 ses=1 subj=_ msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Dec 28 13:58:56 icarus audit[823]: CRED_DISP pid=823 uid=1001 auid=1001 ses=1 subj=_ msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Dec 28 13:58:56 icarus systemd[1]: glusterd.service: Control process exited, code=exited, status=1/FAILURE
Subject: Unit process exited
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
An ExecStart= process belonging to unit glusterd.service has exited.
The process' exit code is 'exited' and its exit status is 1.
Dec 28 13:58:56 icarus sudo[823]: pam_unix(sudo:session): session closed for user root
Dec 28 13:58:56 icarus systemd[1]: glusterd.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit glusterd.service has entered the 'failed' state with result 'exit-code'.
Dec 28 13:58:56 icarus systemd[1]: Failed to start GlusterFS, a clustered file-system server.
Subject: A start job for unit glusterd.service has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit glusterd.service has finished with a failure.
The job identifier is 453 and the job result is failed.')
In case it is worth anything, I am running a mixed-architecture cluster, that is I have this ARMv7 host peered with some x86 hosts. The x86 hosts are able to upgrade to the latest version of glusterfs and operate normally.
My issues on this ARMv7 host are before any network peering: the daemon crashes at launch.
Happy to share more information. Any help would be appreciated, thanks.