Crash on one LUN while creating new LUNs
Pages: 1 2
admin
2,918 Posts
June 13, 2020, 12:02 pmQuote from admin on June 13, 2020, 12:02 pmdid this happen after you upgraded to 2.5.3 ?
was this server an iSCSI service before ?
on the server, does /opt/petasan/config/node_info.json : does it show the is_iscsi flag as true ?
did this happen after you upgraded to 2.5.3 ?
was this server an iSCSI service before ?
on the server, does /opt/petasan/config/node_info.json : does it show the is_iscsi flag as true ?
therm
121 Posts
June 13, 2020, 12:08 pmQuote from therm on June 13, 2020, 12:08 pmThe flag is true. I was not aware that this server had this flag until now so I recognized it after upgrade (it has never shown up in the gui). Nevertheless how to bring it back into the gui or howto move paths the correct server and set flag to false?
The flag is true. I was not aware that this server had this flag until now so I recognized it after upgrade (it has never shown up in the gui). Nevertheless how to bring it back into the gui or howto move paths the correct server and set flag to false?
admin
2,918 Posts
June 13, 2020, 12:30 pmQuote from admin on June 13, 2020, 12:30 pmturn fencing off
set the flag to false manually ( can be done in 2.6 from ui )
do a restart of iscsi service
systemctl restart petasan-iscsi
wait for paths to move to other servers
systemctl stop petasan-iscsi
turn fencing on
turn fencing off
set the flag to false manually ( can be done in 2.6 from ui )
do a restart of iscsi service
systemctl restart petasan-iscsi
wait for paths to move to other servers
systemctl stop petasan-iscsi
turn fencing on
therm
121 Posts
June 13, 2020, 12:52 pmQuote from therm on June 13, 2020, 12:52 pmRestarting does not move the paths, shall I stop it?
Restarting does not move the paths, shall I stop it?
therm
121 Posts
June 13, 2020, 12:59 pmQuote from therm on June 13, 2020, 12:59 pmIn an old email some years ago there was mentioned to do a
consul kv put PetaSAN/Nodes/NODE_NAME @/opt/petasan/config/node_info.json
after changing the flag. Should I?
Also using /opt/petasan/scripts/util/move_path.py leads to the ip beeing removed shortly but reassign after. The ip comes back to the server. Tried it 3 times, maybe it is because the other server have more ips to serve.
In an old email some years ago there was mentioned to do a
consul kv put PetaSAN/Nodes/NODE_NAME @/opt/petasan/config/node_info.json
after changing the flag. Should I?
Also using /opt/petasan/scripts/util/move_path.py leads to the ip beeing removed shortly but reassign after. The ip comes back to the server. Tried it 3 times, maybe it is because the other server have more ips to serve.
Last edited on June 13, 2020, 1:21 pm by therm · #15
admin
2,918 Posts
June 13, 2020, 3:11 pmQuote from admin on June 13, 2020, 3:11 pmif you change the flag in consul as you showed, you should be able to use the move path in the ui to move paths away, the iscsi service should be running.
another option is to have the set to false both locally and in consul then reboot the node if this is possible.
if you change the flag in consul as you showed, you should be able to use the move path in the ui to move paths away, the iscsi service should be running.
another option is to have the set to false both locally and in consul then reboot the node if this is possible.
therm
121 Posts
June 13, 2020, 3:22 pmQuote from therm on June 13, 2020, 3:22 pmI think I got it:
- I turned fencing off
- changed node_info.json
- systemctl stop petasan-iscsi
- uploaded config to consul
- used move_path.py to move the paths (needs petasan-iscsi to be stopped otherwise ips come back to the same server)
- rebooted the host (maybe not needed)
- created a new disk just to make sure it does not has paths from this host
- turned fencing on
I think I got it:
- I turned fencing off
- changed node_info.json
- systemctl stop petasan-iscsi
- uploaded config to consul
- used move_path.py to move the paths (needs petasan-iscsi to be stopped otherwise ips come back to the same server)
- rebooted the host (maybe not needed)
- created a new disk just to make sure it does not has paths from this host
- turned fencing on
admin
2,918 Posts
Pages: 1 2
Crash on one LUN while creating new LUNs
admin
2,918 Posts
Quote from admin on June 13, 2020, 12:02 pmdid this happen after you upgraded to 2.5.3 ?
was this server an iSCSI service before ?
on the server, does /opt/petasan/config/node_info.json : does it show the is_iscsi flag as true ?
did this happen after you upgraded to 2.5.3 ?
was this server an iSCSI service before ?
on the server, does /opt/petasan/config/node_info.json : does it show the is_iscsi flag as true ?
therm
121 Posts
Quote from therm on June 13, 2020, 12:08 pmThe flag is true. I was not aware that this server had this flag until now so I recognized it after upgrade (it has never shown up in the gui). Nevertheless how to bring it back into the gui or howto move paths the correct server and set flag to false?
The flag is true. I was not aware that this server had this flag until now so I recognized it after upgrade (it has never shown up in the gui). Nevertheless how to bring it back into the gui or howto move paths the correct server and set flag to false?
admin
2,918 Posts
Quote from admin on June 13, 2020, 12:30 pmturn fencing off
set the flag to false manually ( can be done in 2.6 from ui )
do a restart of iscsi service
systemctl restart petasan-iscsi
wait for paths to move to other servers
systemctl stop petasan-iscsi
turn fencing on
turn fencing off
set the flag to false manually ( can be done in 2.6 from ui )
do a restart of iscsi service
systemctl restart petasan-iscsi
wait for paths to move to other servers
systemctl stop petasan-iscsi
turn fencing on
therm
121 Posts
Quote from therm on June 13, 2020, 12:52 pmRestarting does not move the paths, shall I stop it?
Restarting does not move the paths, shall I stop it?
therm
121 Posts
Quote from therm on June 13, 2020, 12:59 pmIn an old email some years ago there was mentioned to do a
consul kv put PetaSAN/Nodes/NODE_NAME @/opt/petasan/config/node_info.json
after changing the flag. Should I?
Also using /opt/petasan/scripts/util/move_path.py leads to the ip beeing removed shortly but reassign after. The ip comes back to the server. Tried it 3 times, maybe it is because the other server have more ips to serve.
In an old email some years ago there was mentioned to do a
consul kv put PetaSAN/Nodes/NODE_NAME @/opt/petasan/config/node_info.json
after changing the flag. Should I?
Also using /opt/petasan/scripts/util/move_path.py leads to the ip beeing removed shortly but reassign after. The ip comes back to the server. Tried it 3 times, maybe it is because the other server have more ips to serve.
admin
2,918 Posts
Quote from admin on June 13, 2020, 3:11 pmif you change the flag in consul as you showed, you should be able to use the move path in the ui to move paths away, the iscsi service should be running.
another option is to have the set to false both locally and in consul then reboot the node if this is possible.
if you change the flag in consul as you showed, you should be able to use the move path in the ui to move paths away, the iscsi service should be running.
another option is to have the set to false both locally and in consul then reboot the node if this is possible.
therm
121 Posts
Quote from therm on June 13, 2020, 3:22 pmI think I got it:
- I turned fencing off
- changed node_info.json
- systemctl stop petasan-iscsi
- uploaded config to consul
- used move_path.py to move the paths (needs petasan-iscsi to be stopped otherwise ips come back to the same server)
- rebooted the host (maybe not needed)
- created a new disk just to make sure it does not has paths from this host
- turned fencing on
I think I got it:
- I turned fencing off
- changed node_info.json
- systemctl stop petasan-iscsi
- uploaded config to consul
- used move_path.py to move the paths (needs petasan-iscsi to be stopped otherwise ips come back to the same server)
- rebooted the host (maybe not needed)
- created a new disk just to make sure it does not has paths from this host
- turned fencing on
admin
2,918 Posts