asbril Posted March 16, 2023 Share Posted March 16, 2023 My Tesla nodeserver stopped working and restart did not help. I decided to re-install the ns and first deleted it from the Administrative Console and then pressed delete in the PG3 Dashboard. This is what I get : I tried several times but no luck. What should I do ? Thanks Link to comment
DennisC Posted March 16, 2023 Share Posted March 16, 2023 Are you able to just reinstall the node server in to the same slot? When you click on install there should be an option located about mid page to reinstall in same slot. Link to comment
asbril Posted March 16, 2023 Author Share Posted March 16, 2023 1 hour ago, DennisC said: Are you able to just reinstall the node server in to the same slot? When you click on install there should be an option located about mid page to reinstall in same slot. This is what I have now...... When I was not able to remove the not working nodeserver in slot 21, I added it (also) in slot 19. After a while it occurred to me to replace the Tesla "Refresh Token", a specific requirement for the Tesla ns and the nodeserver started to work again. Now I need to remove the Tesla ns from slot 19, but it does not let me. Maybe I need a sudo command ???? Link to comment
DennisC Posted March 16, 2023 Share Posted March 16, 2023 Are you on Polisy/eisy? On PG3, if you go in to the node server, where the command buttons for the node server are. There should be a button to Stop the node server and then there should be a button to Delete the node server. Just make sure you select the node server in the slot that is not working. If Delete button doesn't work, I think you will need to reach out to Bob. Link to comment
bpwwer Posted March 16, 2023 Share Posted March 16, 2023 Log files. I can't emphasize this enough. While I've tried to improve the error reporting to the UI, it's just not designed well enough to make make error reporting easy and intuitive. The log files should contain the details when things go wrong. Node server control (install/start/stop/remove) is very different for PG3x on eisy and PG3 on Polisy so knowing which is also important. In your initial message you say that you: 1. first delete the node server from the admin console. Don't do that. PG3(x) installs the node server and should also remove the node server from the IoX. By first deleting it using the AC, you've remove it from the IoX and now PG3(x) is somewhat confused as you did that "behind it's back". Using the AC to remove a node server should only be done for orphaned node servers (ones that are currently being managed by something (PG2/PG3(x)). Link to comment
asbril Posted March 16, 2023 Author Share Posted March 16, 2023 1 hour ago, bpwwer said: Log files. I can't emphasize this enough. While I've tried to improve the error reporting to the UI, it's just not designed well enough to make make error reporting easy and intuitive. The log files should contain the details when things go wrong. Node server control (install/start/stop/remove) is very different for PG3x on eisy and PG3 on Polisy so knowing which is also important. In your initial message you say that you: 1. first delete the node server from the admin console. Don't do that. PG3(x) installs the node server and should also remove the node server from the IoX. By first deleting it using the AC, you've remove it from the IoX and now PG3(x) is somewhat confused as you did that "behind it's back". Using the AC to remove a node server should only be done for orphaned node servers (ones that are currently being managed by something (PG2/PG3(x)). I understand what I did wrong (deleting NS from AC), but what do I do now ? Thanks for your help pg3_3-16-2023_21737-PM.zip Link to comment
Solution bpwwer Posted March 16, 2023 Solution Share Posted March 16, 2023 Looks like there's a bug in the latest PG3x release that's preventing it from removing node servers. Link to comment
asbril Posted March 16, 2023 Author Share Posted March 16, 2023 35 minutes ago, bpwwer said: Looks like there's a bug in the latest PG3x release that's preventing it from removing node servers. 1. The good news....... : It's not me 2. The bad news...... : a bit of annoyment Link to comment
bwade913 Posted March 16, 2023 Share Posted March 16, 2023 I'm also seeing this with the Yolink NS. Deleting and reinstalling is the only way to update that NS, and now that's blocked. Link to comment
bpwwer Posted March 16, 2023 Share Posted March 16, 2023 Will be fixed in 3.1.24 that will be available as soon as I can get it out there. 1 Link to comment
bpwwer Posted March 17, 2023 Share Posted March 17, 2023 Version 3.1.24 of PG3x should be available now although it may take a few hours before your eisy checks for available upgrades. Link to comment
asbril Posted March 17, 2023 Author Share Posted March 17, 2023 "Confirm" and "Cancel" are greyed out. In fact the same with Restart PG3, and I had to power cycle eisy to get the upgrade. Link to comment
glarsen Posted March 17, 2023 Share Posted March 17, 2023 See the same thing - the Confirm/Cancel dialog is greyed out/inactive after installing 3.1.24 Link to comment
bpwwer Posted March 17, 2023 Share Posted March 17, 2023 All model dialog boxes are disabled. I don't know why this rebuild of the UI is like that. In the meantime, I've removed 3.1.24 and rolled it back to 3.1.23. 1 Link to comment
bpwwer Posted March 17, 2023 Share Posted March 17, 2023 Ok, a new version of 3.1.24 is back up and should have working dialog boxes again. "Upgrade Packages" should see it and update it. Link to comment
asbril Posted March 18, 2023 Author Share Posted March 18, 2023 3 hours ago, bpwwer said: Ok, a new version of 3.1.24 is back up and should have working dialog boxes again. "Upgrade Packages" should see it and update it. Dialog boxes working again but deleting ns not working. Link to comment
bpwwer Posted March 18, 2023 Share Posted March 18, 2023 Pushed out yet another update. Hopefully I got it right this time. This is still version 3.1.24. 1 1 Link to comment
asbril Posted March 18, 2023 Author Share Posted March 18, 2023 32 minutes ago, bpwwer said: Pushed out yet another update. Hopefully I got it right this time. This is still version 3.1.24. Bingo ! Thanks 1 Link to comment
Recommended Posts