DaveStLou Posted November 13, 2021 Posted November 13, 2021 I am unable to bring up PG3 dashboard in my browser and my nodes are blank in ISY on Polisy and PG3 nodes are showing all zeros in my ISY94i. I've tried restarting polyglot and rebooting Polisy but to no avail. This occurred while in the process of deleting a PG3 Nodeserver. Appreciate help in getting PG3 up again. Thanks!
mbking Posted November 13, 2021 Posted November 13, 2021 @DaveStLou, I have the same issue. I updated Polisy yesterday and it uninstalled PG3. I can't say why, but I suspect it will be back soon.
DaveStLou Posted November 13, 2021 Author Posted November 13, 2021 Appreciate the optimistic thoughts but I suspect it will take some intervention on my part with a little help from my forum friends.
DaveStLou Posted November 13, 2021 Author Posted November 13, 2021 I discovered PG3 was missing from /usr/local/etc/rc.d so I reinstalled it. I have access again still checking if all is back to normal now.
mbking Posted November 16, 2021 Posted November 16, 2021 @Michel Kohanim, I regularly check for updates on Polisy and the upgrade I found on 12Nov2021 removed PG3. Was this normal? The portion of the update listing looked like this: [admin@polisy ~]$ sudo pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: node16: 16.13.0 [udi] Installed packages to be UPGRADED: npm: 6.14.8 -> 6.14.8_1 [udi] Number of packages to be Number of packages to be The process will require 11 MiB to be downloaded. installed: 1 upgraded: 1 37 MiB more space. Proceed with this action? [y/N]: y[1/2] Fetching npm-6.14.8_1.pkg: 100% 4 MiB 619.0kB/s 00:06 00:08 [2/2] Fetching node16-16.13.0.pkg: 100% Checking integrity... done (1 conflicting) 7 MiB 970.2kB/s - node16-16.13.0 [udi] conflicts with node-17.0.1 [installed] on /usr/local/bin/node Checking integrity... done (0 conflicting) Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. The following 4 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: node: 17.0.1 pg3: 3.0.29_2 New packages to be INSTALLED: node16: 16.13.0 [udi] Installed packages to be UPGRADED: npm: 6.14.8 -> 6.14.8_1 [udi] Number of packages to be removed: 2 Number of packages to be installed: 1 Number of packages to be upgraded: 1 The operation will free 61 MiB. Proceed with this action? [y/N]: y [1/4] Deinstalling pg3-3.0.29_2... [1/4] Deleting files for pg3-3.0.29_2: 100% ==> You should manually remove the "polyglot" user. ==> You should manually remove the "polyglot" group [2/4] Deinstalling node-17.0.1... [2/4] Deleting files for node-17.0.1: 100% [3/4] Installing node16-16.13.0... [3/4] Extracting node16-16.13.0: 100% [4/4] Upgrading npm from 6.14.8 to 6.14.8_1... [4/4] Extracting npm-6.14.8_1: 100% By the way, I have all of my time based loops on ISY on Polisy 5.1.1 and they have been working as expected. I'm waiting for Push Notifications in UD Mobile and PG3 to begin moving additional loops. Mark
bpwwer Posted November 16, 2021 Posted November 16, 2021 The latest PG3 version depends on node 17.0.1 and for some reason your upgrade removed node 17.0.1 and replaced it with node 16.13.0. You might have to specifically install PG3 which would then delete node 16.13 and re-install node 17.0.1. We're still working on getting the packaging dependencies correct so I suspect that this is just a one-time glitch. 2
mbking Posted November 16, 2021 Posted November 16, 2021 29 minutes ago, bpwwer said: The latest PG3 version depends on node 17.0.1 and for some reason your upgrade removed node 17.0.1 and replaced it with node 16.13.0. You might have to specifically install PG3 which would then delete node 16.13 and re-install node 17.0.1. We're still working on getting the packaging dependencies correct so I suspect that this is just a one-time glitch. @bpwwer, Thanks for the explanation; it seemed strange that versioning went backwards. With that, I can reinstall.
Recommended Posts