wayneph Posted February 12, 2023 Posted February 12, 2023 Just now getting started with Polyglot, but I think I'm in the same boat. Updated my polisy to 5.5.5 today. I was able to get into the polygot3 site. Added my local isy and then tried adding a couple of the free node servers to get a feel for them. It seemed to add one or two (one was showing up in the admin console) but then became unresponsive. I rebooted the polisy and then couldn't get into polygot3 anymore. As others have mentioned, I can get into the old polygot site and the admin console, but nothing for pg3.
macjeff Posted February 12, 2023 Author Posted February 12, 2023 18 hours ago, wayneph said: Just now getting started with Polyglot, but I think I'm in the same boat. Updated my polisy to 5.5.5 today. I was able to get into the polygot3 site. Added my local isy and then tried adding a couple of the free node servers to get a feel for them. It seemed to add one or two (one was showing up in the admin console) but then became unresponsive. I rebooted the polisy and then couldn't get into polygot3 anymore. As others have mentioned, I can get into the old polygot site and the admin console, but nothing for pg3. Yours might be different. It happens when you upgrade packages and admin console goes away too. Only pg2 and SSH comes back. Are you going to it via a URL like this (replace <IP> with IP of your Polisy https://<ip>:3000/dashboard it will probably warn you its not secure but ok that and you will be fine. Thats because it does not have an SSL cert. which is not needed locally. If you still cant get in I dont know. If admin console is working it does not sound like the same issue.
macjeff Posted February 13, 2023 Author Posted February 13, 2023 Thanks to @Chris Jahnand @brians I think I have a fix SSH into the Polisy (If you dont know how to do that or not comfortable please do not continue) at command prompt type cd /usr/local/etc/pkg/repos/ then type sudo ee FreeBSD.conf and when asked enter your password then change the word latest to quarterly so it looks like this FreeBSD: { url: "https://pkg.FreeBSD.org/${ABI}/quarterly", enabled: yes, priority: 1 } then hit the escape key hit a for leave and then a again for save once saved and back to prompt type sudo pkg upgrade -f mongo-c-driver type y when asked . should say this Number of packages to be reinstalled: 1 Number of packages to be downgraded: 1 once that is done type sudo reboot you should hear a beep and then another beep when the restart process is over And your back online!!! *** After talking to tech support I will update this post if anything needs to be done for long term fix.
brians Posted February 13, 2023 Posted February 13, 2023 Note this fix was originally discovered by over in the support forum for 5.5.5 by @shbatm, was just passing on info I seen over here 2
macjeff Posted February 13, 2023 Author Posted February 13, 2023 16 minutes ago, brians said: Note this fix was originally discovered by over in the support forum for 5.5.5 by @shbatm, was just passing on info I seen over here It looks like the fix came from Chris so I credited him but I did elaborate a lot on the fix with exact instructions. But thanks to @shbatmalso so that everyone is credited
TRI0N Posted February 13, 2023 Posted February 13, 2023 This also fixed the eisy 5.5.5 and PG3x issue on my home system. However I'm a little confused why eisy and PG3x even needed MongoDB if it was no longer used after PG2? TRI0N
macjeff Posted February 13, 2023 Author Posted February 13, 2023 4 minutes ago, TRI0N said: This also fixed the eisy 5.5.5 and PG3x issue on my home system. However I'm a little confused why eisy and PG3x even needed MongoDB if it was no longer used after PG2? TRI0N That would be a question for Bob who wrote PG3. I think he monitors this. Also I have sent all this to my support ticket and we shall see what they say. Until I find out more I would not run any updates. I will post here when I know more.
joeria Posted February 13, 2023 Posted February 13, 2023 thanks for these instructions! Got me back online.
macjeff Posted February 13, 2023 Author Posted February 13, 2023 ** Anyone who did this, the problem is fixed. What I did is go back and change BACK to latest in the text file (from quarterly) from previous post. then go to Admin console and upgrade packages. wait until its TOTALLY finished updating and then reboot Polisy one more time. You will end up on 5.5.6 (From 5.5.5) and everything else updated also.
DennisC Posted February 13, 2023 Posted February 13, 2023 4 minutes ago, macjeff said: ** Anyone who did this, the problem is fixed. What I did is go back and change BACK to latest in the text file (from quarterly) from previous post. then go to Admin console and upgrade packages. wait until its TOTALLY finished updating and then reboot Polisy one more time. You will end up on 5.5.6 (From 5.5.5) and everything else updated also. Do you have multiple node servers and are they all running now on PG3x?
bpwwer Posted February 13, 2023 Posted February 13, 2023 12 hours ago, TRI0N said: This also fixed the eisy 5.5.5 and PG3x issue on my home system. However I'm a little confused why eisy and PG3x even needed MongoDB if it was no longer used after PG2? TRI0N PG3/PG3x does not have any dependency on MongoDB or the mongo-c-driver package. PG3x does have a dependency on UDX and IoX IoX has a dependency on UDX
macjeff Posted February 13, 2023 Author Posted February 13, 2023 8 minutes ago, DennisC said: Do you have multiple node servers and are they all running now on PG3x? I have many notes servers and one left on PG2 but the rest on PG3
DennisC Posted February 13, 2023 Posted February 13, 2023 Just now, macjeff said: I have many notes servers and one left on PG2 but the rest on PG3 The original problem that led to the minor update with the bigger problem, was some node servers would not restart on PG3x. I am trying to understand if an upgrade packages will fix that issue and should we be updating now. Are all of your node servers on PG3x running after the upgrade?
DennisC Posted February 13, 2023 Posted February 13, 2023 (edited) After completing the upgrade to v5.5.6, I can confirm all of the node servers in PG3x are running. I had to clear Java cache and reload start.jnlp. I had to reboot multiple times (after waiting 30 minutes after the first upgrade packages) and trigger upgrade packages twice. I kept getting a message when signing in to admin console that some packages were ready for upgrade. I also kept getting an error that said "Event Received for a Different Subscription Restart". I received this multiple times but finally went away. All node servers required running a query to populate the admin console. I did this about 15 minutes after the last reboot. @bpwwerSo far, now about 30 minutes after the last restart, I can not get Weatherflow Tempest readings in the admin console. I have queried it several times and I see the query data in the Weatherflow node server log, but the admin console has all 0's for readings except for pressure & wind. I have tried closing and relogging in to admin console several times and I tried restarting the Weatherflow node server. Edit: Forecast data is populating in the admin console. Edited February 13, 2023 by DennisC Added info. 1
macjeff Posted February 13, 2023 Author Posted February 13, 2023 5 minutes ago, DennisC said: After completing the upgrade to v5.5.6, I can confirm all of the node servers in PG3x are running. I had to clear Java cache and reload start.jnlp. I had to reboot multiple times (after waiting 30 minutes after the first upgrade packages) and trigger upgrade packages twice. I kept getting a message when signing in to admin console that some packages were ready for upgrade. I also kept getting an error that said "Event Received for a Different Subscription Restart". I received this multiple times but finally went away. All node servers required running a query to populate the admin console. I did this about 15 minutes after the last reboot. @bpwwerSo far, now about 30 minutes after the last restart, I can not get Weatherflow Tempest readings in the admin console. I have queried it several times and I see the query data in the Weatherflow node server log, but the admin console has all 0's for readings except for pressure & wind. I have tried closing and relogging in to admin console several times and I tried restarting the Weatherflow node server. Edit: Forecast data is populating in the admin console. I had same issue but clicked on TEMPEST and hit query for that (not the Node Server query) and it came in about 5 seconds later.
DennisC Posted February 13, 2023 Posted February 13, 2023 7 minutes ago, macjeff said: I had same issue but clicked on TEMPEST and hit query for that (not the Node Server query) and it came in about 5 seconds later. The Tempest is included via a node server. I have tried querying it numerous times. I see data is sent in the node server log, but the fields in the admin console remain at 0 except for wind and pressure.
macjeff Posted February 13, 2023 Author Posted February 13, 2023 Just now, DennisC said: The Tempest is included via a node server. I have tried querying it numerous times. I see data is sent in the node server log, but the fields in the admin console remain at 0 except for wind and pressure. I know. I run the same node server I had to go into admin console. Go to the actual Tempest device. Not the forecast data and not the actual node server I right click on it and choose query and it comes in. Not sure why it’s not auto populating though. It used to
DennisC Posted February 13, 2023 Posted February 13, 2023 2 minutes ago, macjeff said: I know. I run the same node server I had to go into admin console. Go to the actual Tempest device. Not the forecast data and not the actual node server I right click on it and choose query and it comes in. Not sure why it’s not auto populating though. It used to Re-read my messages, that is the only way to query the Tempest. I am showing 0 except for wind and pressure.
TRI0N Posted February 13, 2023 Posted February 13, 2023 (edited) 5 hours ago, bpwwer said: PG3/PG3x does not have any dependency on MongoDB or the mongo-c-driver package. PG3x does have a dependency on UDX and IoX IoX has a dependency on UDX Well that just makes even more puzzling why mongo-c-driver crashed eisy with PG3x if that package isn't even used. Simply downgrading mongo-c-driver on the eisy did indeed fix my issue with multiple node-servers. Everything went back online the moment I did. Didn't even need to reboot. But I did preform a reboot just to see what would happen and nothing. Everything was back in working condition. TRI0N Edited February 13, 2023 by TRI0N
bpwwer Posted February 13, 2023 Posted February 13, 2023 the mongo package was causing problems for UDX and since everything depends on UDX, nothing would work. 1
Recommended Posts