Jump to content

Support thread for: PG3x v3.1.33 (June 30, 2023)


Recommended Posts

Same issues here.  I updated packages but PG3x showed the same version.  I restarted the system and now cannot login to PG3x at all. 

There is a known problem regarding logins that sometimes fail. That’s the next stability issue I’m focusing on.

I believe a reboot fixes the problem.


Sent from my iPhone using Tapatalk
Link to comment

I did the upgrade packages and it's still showing 3.1.31. Also tried a browser refresh and a reboot but it's still showing the previous revision number. I only have the Notification node server installed and it was still spitting out notifications so I guess it's still working.

BTW... I'm on Polisy.

image.jpeg.2eec89bb112760a755d3a694f580acf3.jpeg

Edited by vbPhil
polisy notation.
Link to comment
10 hours ago, bmercier said:

There is a known UI problem with 3.1.33:

  • The UI incorrectly displays version 3.1.35
  • The UI incorrectly displays "PG3x Restart Required", and a restart does not clear this message.

3.1.34 will fix this.

I re-ran the update this morning and am able to login to PG3x again.  I do see the issues @bmercier noted above, but everything seems to be working so I'll look forward to 3.1.34 being released to fix those items. 

Link to comment
12 hours ago, bmercier said:

If you can ssh to your eisy:

tail -f /var/polyglot/pg3/logs/pg3-current.log

I'm still unable to access PG3x, here's the log

 

[admin@eisy ~]$ tail -f /var/polyglot/pg3/logs/pg3-current.log
7/1/2023, 09:06:12 [pg3] info: Verifying node servers are installed on IoX correctly
7/1/2023, 09:06:12 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:62:4c] :: - http://127.0.0.1:8080/rest/profiles/ns/0/connection
7/1/2023, 09:06:12 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:62:4c] :: [200] :: 1.791212ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection
7/1/2023, 09:06:12 [pg3] info: [00:21:b9:02:62:4c_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB.
7/1/2023, 09:06:32 [pg3] info: startRefreshToken: Refreshing Portal token
7/1/2023, 09:06:32 [pg3] info: Portal Authentication: Token expires 7/1/2023, 10:06:31 AM
7/1/2023, 09:11:12 [pg3] info: Verifying node servers are installed on IoX correctly
7/1/2023, 09:11:12 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:62:4c] :: - http://127.0.0.1:8080/rest/profiles/ns/0/connection
7/1/2023, 09:11:12 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:62:4c] :: [200] :: 1.789716ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection
7/1/2023, 09:11:12 [pg3] info: [00:21:b9:02:62:4c_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB.

Edited by Techman
Link to comment
I'm still unable to access PG3x, here's the log
 
[admin@eisy ~]$ tail -f /var/polyglot/pg3/logs/pg3-current.log
7/1/2023, 09:06:12 [pg3] info: Verifying node servers are installed on IoX correctly
7/1/2023, 09:06:12 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:62:4c] :: - http://127.0.0.1:8080/rest/profiles/ns/0/connection
7/1/2023, 09:06:12 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:62:4c] :: [200] :: 1.791212ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection
7/1/2023, 09:06:12 [pg3] info: [00:21:b9:02:62:4c_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB.
7/1/2023, 09:06:32 [pg3] info: startRefreshToken: Refreshing Portal token
7/1/2023, 09:06:32 [pg3] info: Portal Authentication: Token expires 7/1/2023, 10:06:31 AM
7/1/2023, 09:11:12 [pg3] info: Verifying node servers are installed on IoX correctly
7/1/2023, 09:11:12 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:62:4c] :: - http://127.0.0.1:8080/rest/profiles/ns/0/connection
7/1/2023, 09:11:12 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:62:4c] :: [200] :: 1.789716ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection
7/1/2023, 09:11:12 [pg3] info: [00:21:b9:02:62:4c_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB.

Please try to login while tail -f is active. We need to see the error if any when trying to login.


Sent from my iPhone using Tapatalk
Link to comment
@bmercier
I just tried removing power from the EISY and that appears to have corrected the problem. Previously I tried a reboot which didn't resolve the issue. Could it be a cache issue during the update?

Unfortunately I don’t know. If possible, open a ticket and attach todays log. You have at least one failed login, so I will be able to get more info on the problem. Please mention in the ticket that a power cycle fixed the problem.


Sent from my iPhone using Tapatalk
Link to comment
  •  
  •  
  • Should  I update or wait????

Hello everyone,

Here's the latest changes.

Changelog for 3.1.33

  • Fixed occasional uncaugh exceptions making PG3 restart
  • Fix to notifications
  • Fix for Internet outage
    • During an outage, PG3 would lose the portal credentials.
  • Fix for portal login sometimes not appearing, forcing a PG3 restart
  • Some other very minor fixes

Known problem

  • The UI incorrectly displays version 3.1.35
  • The UI incorrectly displays "PG3x Restart Required", and a restart does not clear this message. The message can be ignored.
Link to comment

Greetings;

Something weird happened the other day. A day or two after I received the 3.1.33 announcement, eisy stopped responding to Google Voice commands. Mind you, I had not yet upgraded to 3.1.33.

So I went into the Admin console and pushed the magic UPGRADE PACKAGES. It did it's magic and then asked me to reboot, which I also did via the admin console.

But look what I see in the PG3x console:

image.thumb.png.0cdf8963a46f3673b2b5e5ad2019cf3b.png

It is still asking me to restart PG3x... Shouldn't it restart when you reboot eisy?

I rebooted eisy again, just to be sure, no difference.

BTW, is there a way to restart just PG3x and not the whole eISY? I don't see that on the PG3x page, nor in the admin console, nor in the ISY Portal

Cheers;

 

Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...