Issue with graphs
Pages: 1 2
shin234
6 Posts
November 1, 2017, 10:14 pmQuote from shin234 on November 1, 2017, 10:14 pmroot@sbd-cephmon01:~# systemctl stop petasan-mount-sharedfs
emctl stop glusterfs-server
killall glroot@sbd-cephmon01:~# systemctl stop glusterfs-server
usterfsd
killall glusterfsroot@sbd-cephmon01:~# killall glusterfsd
glusterfsd: no process found
root@sbd-cephmon01:~# killall glusterfs
glusterfs: no process found
root@sbd-cephmon01:~# rm -rf /var/lib/glusterd/vols/gfs-vol
rm -rf /oproot@sbd-cephmon01:~# rm -rf /opt/petasan/config/gfs-brick
rroot@sbd-cephmon01:~# mkdir -p /opt/petasan/config/gfs-brick
root@sbd-cephmon01:~# systemctl start petasan-mount-sharedfs
root@sbd-cephmon01:~# systemctl start glusterfs-server
root@sbd-cephmon01:~#
root@sbd-cephmon01:~# gluster vol create gfs-vol replica 3 192.168.15.100:/opt/petasan/config/gfs-brick 192.168.15.101:/opt/petasan/config/gfs-brick 192.168.15.102:/opt/petasan/config/gfs-brick
volume create: gfs-vol: failed: Host 192.168.15.102 is not in 'Peer in Cluster' state
root@sbd-cephmon01:~# gluster vol start gfs-vol
volume start: gfs-vol: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol set gfs-vol network.ping-timeout 5
volume set: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol set gfs-vol nfs.disable true
volume set: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol info gfs-vol
Volume gfs-vol does not exist
root@sbd-cephmon01:~# systemctl stop petasan-mount-sharedfs
emctl stop glusterfs-server
killall glroot@sbd-cephmon01:~# systemctl stop glusterfs-server
usterfsd
killall glusterfsroot@sbd-cephmon01:~# killall glusterfsd
glusterfsd: no process found
root@sbd-cephmon01:~# killall glusterfs
glusterfs: no process found
root@sbd-cephmon01:~# rm -rf /var/lib/glusterd/vols/gfs-vol
rm -rf /oproot@sbd-cephmon01:~# rm -rf /opt/petasan/config/gfs-brick
rroot@sbd-cephmon01:~# mkdir -p /opt/petasan/config/gfs-brick
root@sbd-cephmon01:~# systemctl start petasan-mount-sharedfs
root@sbd-cephmon01:~# systemctl start glusterfs-server
root@sbd-cephmon01:~#
root@sbd-cephmon01:~# gluster vol create gfs-vol replica 3 192.168.15.100:/opt/petasan/config/gfs-brick 192.168.15.101:/opt/petasan/config/gfs-brick 192.168.15.102:/opt/petasan/config/gfs-brick
volume create: gfs-vol: failed: Host 192.168.15.102 is not in 'Peer in Cluster' state
root@sbd-cephmon01:~# gluster vol start gfs-vol
volume start: gfs-vol: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol set gfs-vol network.ping-timeout 5
volume set: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol set gfs-vol nfs.disable true
volume set: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol info gfs-vol
Volume gfs-vol does not exist
admin
2,930 Posts
November 1, 2017, 10:31 pmQuote from admin on November 1, 2017, 10:31 pmThings are rough 🙂 it seems node 192.168.15.102 peering was not done/ready. I made a small modification to the steps maybe it will work. Also if this is test cluster you just installed it may be easy to try re-install it should not take long, so..
try to do the following on all 3 nodes:
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
Then after the above is done on all 3 nodes, start the following services on all 3 nodes:
systemctl start petasan-mount-sharedfs
systemctl start glusterfs-server
then on all 3 nodes run
gluster peer status
and make sure on all 3 nodes each node sees the other 2 peers as "Connected", sometimes it takes a couple of seconds after service restart, so check the status a couple of times.
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 IP1:/opt/petasan/config/gfs-brick IP2:/opt/petasan/config/gfs-brick IP3:/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
Things are rough 🙂 it seems node 192.168.15.102 peering was not done/ready. I made a small modification to the steps maybe it will work. Also if this is test cluster you just installed it may be easy to try re-install it should not take long, so..
try to do the following on all 3 nodes:
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
Then after the above is done on all 3 nodes, start the following services on all 3 nodes:
systemctl start petasan-mount-sharedfs
systemctl start glusterfs-server
then on all 3 nodes run
gluster peer status
and make sure on all 3 nodes each node sees the other 2 peers as "Connected", sometimes it takes a couple of seconds after service restart, so check the status a couple of times.
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 IP1:/opt/petasan/config/gfs-brick IP2:/opt/petasan/config/gfs-brick IP3:/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
Pages: 1 2
Issue with graphs
shin234
6 Posts
Quote from shin234 on November 1, 2017, 10:14 pmroot@sbd-cephmon01:~# systemctl stop petasan-mount-sharedfs
emctl stop glusterfs-server
killall glroot@sbd-cephmon01:~# systemctl stop glusterfs-server
usterfsd
killall glusterfsroot@sbd-cephmon01:~# killall glusterfsd
glusterfsd: no process found
root@sbd-cephmon01:~# killall glusterfs
glusterfs: no process found
root@sbd-cephmon01:~# rm -rf /var/lib/glusterd/vols/gfs-vol
rm -rf /oproot@sbd-cephmon01:~# rm -rf /opt/petasan/config/gfs-brick
rroot@sbd-cephmon01:~# mkdir -p /opt/petasan/config/gfs-brick
root@sbd-cephmon01:~# systemctl start petasan-mount-sharedfs
root@sbd-cephmon01:~# systemctl start glusterfs-server
root@sbd-cephmon01:~#
root@sbd-cephmon01:~# gluster vol create gfs-vol replica 3 192.168.15.100:/opt/petasan/config/gfs-brick 192.168.15.101:/opt/petasan/config/gfs-brick 192.168.15.102:/opt/petasan/config/gfs-brick
volume create: gfs-vol: failed: Host 192.168.15.102 is not in 'Peer in Cluster' state
root@sbd-cephmon01:~# gluster vol start gfs-vol
volume start: gfs-vol: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol set gfs-vol network.ping-timeout 5
volume set: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol set gfs-vol nfs.disable true
volume set: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol info gfs-vol
Volume gfs-vol does not exist
root@sbd-cephmon01:~# systemctl stop petasan-mount-sharedfs
emctl stop glusterfs-server
killall glroot@sbd-cephmon01:~# systemctl stop glusterfs-server
usterfsd
killall glusterfsroot@sbd-cephmon01:~# killall glusterfsd
glusterfsd: no process found
root@sbd-cephmon01:~# killall glusterfs
glusterfs: no process found
root@sbd-cephmon01:~# rm -rf /var/lib/glusterd/vols/gfs-vol
rm -rf /oproot@sbd-cephmon01:~# rm -rf /opt/petasan/config/gfs-brick
rroot@sbd-cephmon01:~# mkdir -p /opt/petasan/config/gfs-brick
root@sbd-cephmon01:~# systemctl start petasan-mount-sharedfs
root@sbd-cephmon01:~# systemctl start glusterfs-server
root@sbd-cephmon01:~#
root@sbd-cephmon01:~# gluster vol create gfs-vol replica 3 192.168.15.100:/opt/petasan/config/gfs-brick 192.168.15.101:/opt/petasan/config/gfs-brick 192.168.15.102:/opt/petasan/config/gfs-brick
volume create: gfs-vol: failed: Host 192.168.15.102 is not in 'Peer in Cluster' state
root@sbd-cephmon01:~# gluster vol start gfs-vol
volume start: gfs-vol: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol set gfs-vol network.ping-timeout 5
volume set: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol set gfs-vol nfs.disable true
volume set: failed: Volume gfs-vol does not exist
root@sbd-cephmon01:~# gluster vol info gfs-vol
Volume gfs-vol does not exist
admin
2,930 Posts
Quote from admin on November 1, 2017, 10:31 pmThings are rough 🙂 it seems node 192.168.15.102 peering was not done/ready. I made a small modification to the steps maybe it will work. Also if this is test cluster you just installed it may be easy to try re-install it should not take long, so..
try to do the following on all 3 nodes:
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-brickThen after the above is done on all 3 nodes, start the following services on all 3 nodes:
systemctl start petasan-mount-sharedfs
systemctl start glusterfs-serverthen on all 3 nodes run
gluster peer status
and make sure on all 3 nodes each node sees the other 2 peers as "Connected", sometimes it takes a couple of seconds after service restart, so check the status a couple of times.
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 IP1:/opt/petasan/config/gfs-brick IP2:/opt/petasan/config/gfs-brick IP3:/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
Things are rough 🙂 it seems node 192.168.15.102 peering was not done/ready. I made a small modification to the steps maybe it will work. Also if this is test cluster you just installed it may be easy to try re-install it should not take long, so..
try to do the following on all 3 nodes:
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
Then after the above is done on all 3 nodes, start the following services on all 3 nodes:
systemctl start petasan-mount-sharedfs
systemctl start glusterfs-server
then on all 3 nodes run
gluster peer status
and make sure on all 3 nodes each node sees the other 2 peers as "Connected", sometimes it takes a couple of seconds after service restart, so check the status a couple of times.
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 IP1:/opt/petasan/config/gfs-brick IP2:/opt/petasan/config/gfs-brick IP3:/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