Scott Korvek Posted June 29, 2023 Posted June 29, 2023 (edited) I'm not sure I'm getting this right, but I believe I'm following the instructions. (my eISY is on PG3x). My polisy is on 3.1.23. IoX is on 5.6.2. I've hit the upgrade packages button, waited a long time (hours- walked away). Rebooted. IoX seems fine, Polisy is still on PG3, 3.1.23. I've used the rest call https://polisy:8443/rest/pg3x.enable. more than once (not in a row). I've not renamed the Polisy, I believe that is the correct internal network URL (dropped .local) as that's the URL in the IoX finder to log into the admin console and how I'd access PG3 (https://polisy:3000). As above, no response in the browser (XML has no stylesheet message/blank page)- but not any error message/invalid URL response either. Logging into the PG3 interface- all nodes are connected/running. Done the reboot cycle after that too- nothing seems different. no pop-up messages. Still PG3, 3.1.23. Starting from the basics- is the REST request/response code logged anywhere for me to validate that I am triggering the pg3x.enable script? I can't seem to find any log entry anywhere. The only useful log entry. I can find is the /var/udx/logs/log file entry stating "no packages need updating." Thanks. Edited June 29, 2023 by Scott Korvek clarification of log entry
Scott Korvek Posted June 29, 2023 Author Posted June 29, 2023 No idea what was different this time but on the 4th cycle I get this: /usr/local/etc/udx.d/static/udx_startup.sh: running pg3 in pg3x mode . However - I'm still seeing in the UI PG3, not PG3x, and still logging in with PG3 credentials, not IoX credentials. And UD mobile is still complaining that the notifications feature requires migration from PG3 to PG3x. (But all along I am able to use network resources to send notifications to UDMobile from Polisy, just like I can from eISY)
DennisC Posted June 29, 2023 Posted June 29, 2023 Try removing power from Polisy and then rebooting after a short delay. You might need to restart Polyglot also. Before trying this, check the main PG3 log in Polyglot for any clues.
Scott Korvek Posted June 29, 2023 Author Posted June 29, 2023 2 hours ago, DennisC said: Before trying this, check the main PG3 log in Polyglot for any clues. Any idea what I should be searching for? I don't see anything unusual or any specific references to PG3x- only the usual log entries. I've tried debug logging too but that seems to reset to info after reboots.
Geddy Posted June 29, 2023 Posted June 29, 2023 @Scott Korvek If you've attempted this several times and it still isn't updating you are probably best served by opening a support ticket with UDI and getting help that way. According to the wiki for this process it should be an automated process once the Polisy reboots. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Upgrading_to_PG3x The only other suggestion I would have is to use the Polisy IP address rather than the "polisy.local" url. Some routers might have an issue with "polisy.local" address. If you've been able to access the Polisy using that in the past then you should be okay, but if you've only ever used the IP address use that in the rest address and see if that triggers the flag correctly. If still not updating open a support ticket: https://www.universal-devices.com/my-tickets 1
DennisC Posted June 29, 2023 Posted June 29, 2023 1 hour ago, Scott Korvek said: Any idea what I should be searching for? I don't see anything unusual or any specific references to PG3x- only the usual log entries. I've tried debug logging too but that seems to reset to info after reboots. If nothing jumps out at you in the log, then I would power cycle and try again. Set the flag, update packages, and then reboot, followed by restart of Polyglot. I agree with @Geddycomment to try using the IP address. 1
Scott Korvek Posted July 11, 2023 Author Posted July 11, 2023 worked this week- no new steps but noted there was a new set of package updates taken during the upgrade step. So perhaps a recent code change worked. Or elves. 1
Recommended Posts