Error: command ['systemctl', 'status', '--full', 'corosync.service'] failed with exit code 3: ● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2021-05-17 19:44:31 EDT; 8min ago
     Docs: man:corosync
           man:corosync.conf
           man:corosync_overview
  Process: 2423 ExecStart=/usr/sbin/corosync -f $COROSYNC_OPTIONS (code=exited, status=20)
 Main PID: 2423 (code=exited, status=20)

May 17 19:44:31 vox-server1 corosync[2423]:   [TOTEM ] Created or loaded sequence id 4.127.0.0.1 for this ring.
May 17 19:44:31 vox-server1 corosync[2423]:   [QB    ] server name: cmap
May 17 19:44:31 vox-server1 corosync[2423]: May 17 19:44:31 info    [QB    ] server name: cmap
May 17 19:44:31 vox-server1 corosync[2423]: May 17 19:44:31 info    [QB    ] server name: cfg
May 17 19:44:31 vox-server1 corosync[2423]:   [QB    ] server name: cfg
May 17 19:44:31 vox-server1 corosync[2423]:   [QB    ] server name: cpg
May 17 19:44:31 vox-server1 corosync[2423]: May 17 19:44:31 info    [QB    ] server name: cpg
May 17 19:44:31 vox-server1 systemd[1]: corosync.service: Main process exited, code=exited, status=20/n/a
May 17 19:44:31 vox-server1 systemd[1]: corosync.service: Failed with result 'exit-code'.
May 17 19:44:31 vox-server1 systemd[1]: Failed to start Corosync Cluster Engine.
------
Error: command ['systemctl', 'status', '--full', 'gluster-ta-volume.service'] failed with exit code 3: ● gluster-ta-volume.service - GlusterFS, Thin-arbiter process to maintain quorum for replica volume
   Loaded: loaded (/lib/systemd/system/gluster-ta-volume.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2021-05-17 19:44:32 EDT; 8min ago
  Process: 3200 ExecStart=/usr/sbin/glusterfsd -N --volfile-id ta -f /var/lib/glusterd/thin-arbiter/thin-arbiter.vol --brick-port 24007 --xlator-option ta-server.transport.socket.listen-port=24007 -LWARNING (code=exited, status=255)
 Main PID: 3200 (code=exited, status=255)

May 17 19:44:32 vox-server1 systemd[1]: gluster-ta-volume.service: Service hold-off time over, scheduling restart.
May 17 19:44:32 vox-server1 systemd[1]: gluster-ta-volume.service: Scheduled restart job, restart counter is at 5.
May 17 19:44:32 vox-server1 systemd[1]: Stopped GlusterFS, Thin-arbiter process to maintain quorum for replica volume.
May 17 19:44:32 vox-server1 systemd[1]: gluster-ta-volume.service: Start request repeated too quickly.
May 17 19:44:32 vox-server1 systemd[1]: gluster-ta-volume.service: Failed with result 'exit-code'.
May 17 19:44:32 vox-server1 systemd[1]: Failed to start GlusterFS, Thin-arbiter process to maintain quorum for replica volume.
------
Error: command ['systemctl', 'status', '--full', 'sipsentry.service'] failed with exit code 3: ● sipsentry.service - SIPSentry client
   Loaded: loaded (/etc/systemd/system/sipsentry.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2021-05-17 19:44:48 EDT; 8min ago
  Process: 2592 ExecStart=/opt/sipsentry/bin/run.sh (code=exited, status=0/SUCCESS)
 Main PID: 2820 (code=exited, status=1/FAILURE)

May 17 19:44:31 vox-server1 systemd[1]: Starting SIPSentry client...
May 17 19:44:31 vox-server1 systemd[1]: sipsentry.service: Failed to parse PID from file /var/run/sipsentry.pid: Invalid argument
May 17 19:44:31 vox-server1 systemd[1]: Started SIPSentry client.
May 17 19:44:48 vox-server1 systemd[1]: sipsentry.service: Main process exited, code=exited, status=1/FAILURE
May 17 19:44:48 vox-server1 systemd[1]: sipsentry.service: Failed with result 'exit-code'.