glusterfs-server.service not found
motoburn
1 Post
June 25, 2024, 11:15 amQuote from motoburn on June 25, 2024, 11:15 amHi,
While trying to fix the errors on the dashboard graph, one thread I found included some commands:
systemctl stop petasan-mount-sharedfs
systemctl stop glusterfs-server
killall glusterfsd
killall glusterfs
rm -rf /var/lib/glusterd/vols/gfs-vol
rm -rf /opt/petasan/config/gfs-brick
mkdir -p /opt/petasan/config/gfs-brick
systemctl start petasan-mount-sharedfs
systemctl start glusterfs-server
then do this from any node
#create volume: note replace IP1, IP2, IP3 with the ip addresses of your backend 1 ip for nodes 1,2,3 respectively:
gluster vol create gfs-vol replica 3 10.0.2.11:/opt/petasan/config/gfs-brick 10.0.2.12:/opt/petasan/config/gfs-brick 10.0.2.13:/opt/petasan/config/gfs-brick
# start volume
gluster vol start gfs-vol
gluster vol set gfs-vol network.ping-timeout 5
gluster vol set gfs-vol nfs.disable true
# check volume is working
gluster vol info gfs-vol
but when I get to the
systemctl start glusterfs-server
it returns a "service not found"
root@PS02:~# systemctl start glusterfs-server
Failed to start glusterfs-server.service: Unit glusterfs-server.service not found.
Any suggestions where to go from here?
Thanks,
Chris
Oh, and I'm on 3.3.0 - unbuntu server 20.04 - 4 node (3 manage, 1 storage) - production environment
Hi,
While trying to fix the errors on the dashboard graph, one thread I found included some commands:
systemctl stop petasan-mount-sharedfs
systemctl stop glusterfs-server
killall glusterfsd
killall glusterfs
rm -rf /var/lib/glusterd/vols/gfs-vol
rm -rf /opt/petasan/config/gfs-brick
mkdir -p /opt/petasan/config/gfs-brick
systemctl start petasan-mount-sharedfs
systemctl start glusterfs-server
then do this from any node
#create volume: note replace IP1, IP2, IP3 with the ip addresses of your backend 1 ip for nodes 1,2,3 respectively:
gluster vol create gfs-vol replica 3 10.0.2.11:/opt/petasan/config/gfs-brick 10.0.2.12:/opt/petasan/config/gfs-brick 10.0.2.13:/opt/petasan/config/gfs-brick
# start volume
gluster vol start gfs-vol
gluster vol set gfs-vol network.ping-timeout 5
gluster vol set gfs-vol nfs.disable true
# check volume is working
gluster vol info gfs-vol
but when I get to the
systemctl start glusterfs-server
it returns a "service not found"
root@PS02:~# systemctl start glusterfs-server
Failed to start glusterfs-server.service: Unit glusterfs-server.service not found.
Any suggestions where to go from here?
Thanks,
Chris
Oh, and I'm on 3.3.0 - unbuntu server 20.04 - 4 node (3 manage, 1 storage) - production environment
admin
2,930 Posts
June 26, 2024, 9:12 amQuote from admin on June 26, 2024, 9:12 amthe service has been renamed
systemctl start glusterd
the service has been renamed
systemctl start glusterd
glusterfs-server.service not found
motoburn
1 Post
Quote from motoburn on June 25, 2024, 11:15 amHi,
While trying to fix the errors on the dashboard graph, one thread I found included some commands:
systemctl stop petasan-mount-sharedfs
systemctl stop glusterfs-server
killall glusterfsd
killall glusterfsrm -rf /var/lib/glusterd/vols/gfs-vol
rm -rf /opt/petasan/config/gfs-brick
mkdir -p /opt/petasan/config/gfs-bricksystemctl start petasan-mount-sharedfs
systemctl start glusterfs-serverthen do this from any node
#create volume: note replace IP1, IP2, IP3 with the ip addresses of your backend 1 ip for nodes 1,2,3 respectively:
gluster vol create gfs-vol replica 3 10.0.2.11:/opt/petasan/config/gfs-brick 10.0.2.12:/opt/petasan/config/gfs-brick 10.0.2.13:/opt/petasan/config/gfs-brick# start volume
gluster vol start gfs-vol
gluster vol set gfs-vol network.ping-timeout 5
gluster vol set gfs-vol nfs.disable true# check volume is working
gluster vol info gfs-volbut when I get to the
systemctl start glusterfs-server
it returns a "service not found"
root@PS02:~# systemctl start glusterfs-server
Failed to start glusterfs-server.service: Unit glusterfs-server.service not found.Any suggestions where to go from here?
Thanks,
Chris
Oh, and I'm on 3.3.0 - unbuntu server 20.04 - 4 node (3 manage, 1 storage) - production environment
Hi,
While trying to fix the errors on the dashboard graph, one thread I found included some commands:
systemctl stop petasan-mount-sharedfs
systemctl stop glusterfs-server
killall glusterfsd
killall glusterfsrm -rf /var/lib/glusterd/vols/gfs-vol
rm -rf /opt/petasan/config/gfs-brick
mkdir -p /opt/petasan/config/gfs-bricksystemctl start petasan-mount-sharedfs
systemctl start glusterfs-serverthen do this from any node
#create volume: note replace IP1, IP2, IP3 with the ip addresses of your backend 1 ip for nodes 1,2,3 respectively:
gluster vol create gfs-vol replica 3 10.0.2.11:/opt/petasan/config/gfs-brick 10.0.2.12:/opt/petasan/config/gfs-brick 10.0.2.13:/opt/petasan/config/gfs-brick# start volume
gluster vol start gfs-vol
gluster vol set gfs-vol network.ping-timeout 5
gluster vol set gfs-vol nfs.disable true# check volume is working
gluster vol info gfs-vol
but when I get to the
systemctl start glusterfs-server
it returns a "service not found"
root@PS02:~# systemctl start glusterfs-server
Failed to start glusterfs-server.service: Unit glusterfs-server.service not found.
Any suggestions where to go from here?
Thanks,
Chris
Oh, and I'm on 3.3.0 - unbuntu server 20.04 - 4 node (3 manage, 1 storage) - production environment
admin
2,930 Posts
Quote from admin on June 26, 2024, 9:12 amthe service has been renamed
systemctl start glusterd
the service has been renamed
systemctl start glusterd