I thought i would never write about storage on this blog, but it turns out strange things happen to SAN”s as well. I do normally not work with SAN that much, the ones im familiar to is IBM DS3400 and Storeweize v7000. Today the v7000 stoped answer to https, so we could not manage it with the web gui.
Luckily one of the nodes still got HTTP service up. So here is what i did:
- Connect to the Node.
- Chose the Node you would like to restart the tomcat on (webserver).
- Go to “Restart Service”
4. And chose to restart the Web server (Tomcat)
If you don’t have the same amount of luck as i had. You will have to restart the web server using CLI. You can only run satask commands if you connected to the CLI using the SSH private key which is associated with the user called superuser. No other SSH key will allow you to run satask commands:
panel_name cluster_id cluster_name node_id node_name relation node_status error_data
01-1 000002006540697C ldcluster-22b 1 node1 local Active
01-2 000002006540697C ldcluster-22b 3 node2 partner Active
To find out which node is the configuration node, run the following command
sainfo lsservicestatus <panel name>
the following line tells you which node is the config node:
Use the following command to restart the web service on the configuration node
satask restartservice -service tomcat <panel name>
Wait at least 5 minutes for the service to restart before assuming that this has failed
If this do no’t solve your problems, you should restart the cannister with configuration node on it. Remember to connect to the Node that’s not configuration node. And restart the “partner”. If unable to get it reset, reset the canister physically. that is, pull it out a few inches from the chassis and then insert it again after 30 seconds.