node stays disconnected following power outage
admin
2,930 Posts
July 10, 2019, 4:03 pmQuote from admin on July 10, 2019, 4:03 pmEven if you leave the browser open and refresh and/or back/refresh it will tell you the node is already deployed. To get it to re-deploy you either need to delete some core files on the system (such as node_info.sjon) then refresh, in this case the wizard will do a normal re-deploy starting at page 1 and going on sequentially to page 8 or you post the internal page 8 url which as i understand is not something you see in the browser url or browser history. As far as the browser is concerned you are dealing with 1 url a t port 5001. One issue is that the wizard runs without a password (since it actually sets it), so cannot protect against internal urls being called. One thing we consider doing, is dis-able the wizard once it successfully deploys, currently we leave so prints a pretty message that the node is already up and can be managed via such and such ip. If you do find any more info please do let us know.
Even if you leave the browser open and refresh and/or back/refresh it will tell you the node is already deployed. To get it to re-deploy you either need to delete some core files on the system (such as node_info.sjon) then refresh, in this case the wizard will do a normal re-deploy starting at page 1 and going on sequentially to page 8 or you post the internal page 8 url which as i understand is not something you see in the browser url or browser history. As far as the browser is concerned you are dealing with 1 url a t port 5001. One issue is that the wizard runs without a password (since it actually sets it), so cannot protect against internal urls being called. One thing we consider doing, is dis-able the wizard once it successfully deploys, currently we leave so prints a pretty message that the node is already up and can be managed via such and such ip. If you do find any more info please do let us know.
deweyhylton
14 Posts
July 10, 2019, 4:37 pmQuote from deweyhylton on July 10, 2019, 4:37 pmFair enough. I'm out of ideas and suppose it's time to redeploy. Can it really be as simple as removing the file you mention or do I need to wipe and reinstall from scratch?
Fair enough. I'm out of ideas and suppose it's time to redeploy. Can it really be as simple as removing the file you mention or do I need to wipe and reinstall from scratch?
admin
2,930 Posts
July 10, 2019, 4:49 pmQuote from admin on July 10, 2019, 4:49 pmYou do not need to delete files, it was just a case to show when the wizard will allow you to redeploy.
In normal case: if a management node (first 3 nodes) fails, you re-install the node via installer and do a "Replace Management Node" during deployment,\. If it is node 4 and beyond, you should delete the node from the cluster (from the Node List) then optionally if you need to replace it then reinstall and deploy new node using "Join Existing Cluster". In the first case the node must have the same node name as original.
In your case you should do a replace management node. you need to re-install this node from scratch
You do not need to delete files, it was just a case to show when the wizard will allow you to redeploy.
In normal case: if a management node (first 3 nodes) fails, you re-install the node via installer and do a "Replace Management Node" during deployment,\. If it is node 4 and beyond, you should delete the node from the cluster (from the Node List) then optionally if you need to replace it then reinstall and deploy new node using "Join Existing Cluster". In the first case the node must have the same node name as original.
In your case you should do a replace management node. you need to re-install this node from scratch
node stays disconnected following power outage
admin
2,930 Posts
Quote from admin on July 10, 2019, 4:03 pmEven if you leave the browser open and refresh and/or back/refresh it will tell you the node is already deployed. To get it to re-deploy you either need to delete some core files on the system (such as node_info.sjon) then refresh, in this case the wizard will do a normal re-deploy starting at page 1 and going on sequentially to page 8 or you post the internal page 8 url which as i understand is not something you see in the browser url or browser history. As far as the browser is concerned you are dealing with 1 url a t port 5001. One issue is that the wizard runs without a password (since it actually sets it), so cannot protect against internal urls being called. One thing we consider doing, is dis-able the wizard once it successfully deploys, currently we leave so prints a pretty message that the node is already up and can be managed via such and such ip. If you do find any more info please do let us know.
Even if you leave the browser open and refresh and/or back/refresh it will tell you the node is already deployed. To get it to re-deploy you either need to delete some core files on the system (such as node_info.sjon) then refresh, in this case the wizard will do a normal re-deploy starting at page 1 and going on sequentially to page 8 or you post the internal page 8 url which as i understand is not something you see in the browser url or browser history. As far as the browser is concerned you are dealing with 1 url a t port 5001. One issue is that the wizard runs without a password (since it actually sets it), so cannot protect against internal urls being called. One thing we consider doing, is dis-able the wizard once it successfully deploys, currently we leave so prints a pretty message that the node is already up and can be managed via such and such ip. If you do find any more info please do let us know.
deweyhylton
14 Posts
Quote from deweyhylton on July 10, 2019, 4:37 pmFair enough. I'm out of ideas and suppose it's time to redeploy. Can it really be as simple as removing the file you mention or do I need to wipe and reinstall from scratch?
Fair enough. I'm out of ideas and suppose it's time to redeploy. Can it really be as simple as removing the file you mention or do I need to wipe and reinstall from scratch?
admin
2,930 Posts
Quote from admin on July 10, 2019, 4:49 pmYou do not need to delete files, it was just a case to show when the wizard will allow you to redeploy.
In normal case: if a management node (first 3 nodes) fails, you re-install the node via installer and do a "Replace Management Node" during deployment,\. If it is node 4 and beyond, you should delete the node from the cluster (from the Node List) then optionally if you need to replace it then reinstall and deploy new node using "Join Existing Cluster". In the first case the node must have the same node name as original.
In your case you should do a replace management node. you need to re-install this node from scratch
You do not need to delete files, it was just a case to show when the wizard will allow you to redeploy.
In normal case: if a management node (first 3 nodes) fails, you re-install the node via installer and do a "Replace Management Node" during deployment,\. If it is node 4 and beyond, you should delete the node from the cluster (from the Node List) then optionally if you need to replace it then reinstall and deploy new node using "Join Existing Cluster". In the first case the node must have the same node name as original.
In your case you should do a replace management node. you need to re-install this node from scratch