Hello all,

PG3x 3.1.35 is now in beta and has major stability enhancements and bug fixes:

• Significant rework on error handling in async functions
• Login API has been enhanced (Login should always work, or give an error message)
• Restore backup/Migrate from PG3: Made the UI more intuitive
• Notifications from PG3 now specify the uuid
• Restart required bug fixed

We would appreciate your feedback. Since this is a beta release, the installation is done through ssh with two commands:

sudo pkg add -f https://pkg.isy.io/udx13.staging/All/pg3x-3.1.35.pkg

sudo service udx restart

We would appreciate your feedback.

@Michel Kohanim,

I updated using the commands above.  Once the systems had restarted, I was not able to get into PG3x via the Admin Console or UD Mobile.  I restarted PG3x using the following command:

sudo service pg3 onerestart (sudo service pg3 restart didn't work, onerestart was recommended)

Now I can login to PG3 and all node servers appear to be running normally and the UI indicates 3.1.35 is running.

At this point, I have no issues to report other than the additional command to restart pg3.  I will continue to exercise the system and post any issues I find.

Thanks

@Michel Kohanim

similar but different to mbking

after udx restart, i could get to pg3, it reported as version .35, but had the red box "pg3 restart required"

after restarting with the onerestart command all is green and good

...Barry

 

1 minute ago, bgrubb1 said:

similar but different to mbking

after udx restart, i could get to pg3, it reported as version .35, but had the red box "pg3 restart required"

after restarting with the onerestart command all is green and good

My experience was similar to yours.  After performing the restart, all seems to be working.  Will monitor and post an update if any issues arise. 

Installed onto an eisy and a remote Polisy using the two commands provided above.  Both systems now show PG3x 3.1.35 and appear to be functioning properly. 

I ran the update on my eisy and everything seems to be working fine. After the commands and a restart of PG3x it still showed PG3x needed to be restarted so I performed the 6 button press shutdown and pulled the plug on eisy after the light turned red then after pugging it back in when it booted the restart PG3x was gone. I have made the 6 button press shutdown and removing power a standard step after an upgrade.

Installed onto Polisy using the two commands provided above.   System  show PG3x 3.1.35 and appear to be functioning properly. 

Followed Michel's instructions on a Polisy running 3.1.33 / 3.1.35. Update took less than a minute, then a restart. Once the system was back up both AC and the Web interface reported a restart was required. 

Using AC configuration/restart I restarted the Polisy, once it was back up, both Web and AC still reported a restart was needed. I power cycled the Polisy and everything is working as expected with no more restart messages.

Good morning,

I tried upgrading this morning and received "Not Found":

[admin@eisy ~]$
[admin@eisy ~]$ sudo pkg add -f https://pkg.isy.io/udx13.staging/All/pg3x-3.1.35.pkg
pkg: https://pkg.isy.io/udx13.staging/All/pg3x-3.1.35.pkg: Not Found
 

Any suggestions would be welcome.

Thanks,

-Tim

I tried twice and got “Not Found” as well.

22 hours ago, atomicboy said:

I tried twice and got “Not Found” as well.

Same for me this morning

 

Perhaps UDI filled their quota for beta testers already...

Hi All, 

Apologies. Please try again.

With kind regards,
Michel

Works again.  Installed 3.1.35 successfully.  I did have to use the "sudo service pg3 onerestart" command as noted above.  PG3 restart notice fixed.  Will monitor and update if any issues arise.  Thanks Michel.

I tried a few more times and again I still got “Not Found”.
To ensure no typing errors I copy pasted as well. 

 I am not that much of an experience user of ssh commands, so maybe it is me?

 I was a bit surprised when I typed in “sudo pkg add -f https://pkg.isy.io/udx13.staging/All/pg3x-3.1.35.pkg” that it prompted for the password (“admin”) again. I do not believe I experienced this before. I am just identifying this in case I made an error.

Edited July 10, 20232 yr by atomicboy

Hi @atomicboy,

Please try again. This said, based on the feedback, we are going to move to production soon.

With kind regards,
Michel

1 hour ago, atomicboy said:

I do not believe I experienced this before. I am just identifying this in case I made an error.

sudo asks for the password once every 15 minutes, or better stated, after 15 minutes of sudo inactivity password will again be prompted.

Just performed the upgrade.  I need to sudo service pg3 onerestart to get PG3x to open.  Still had the restart message so I did the 6 button shutdown, unplug/plug.  All is now well.  Thank you.

I just gave it another try and it worked. I ran both the ssh commands and it is restarting now.

Did 6 button shutdown. Restarted. Got the same message that PG3x needed to be restarted. Rebooted inside MobiLinc. All is good now.

As an aside: I was very quick with the copy paste and it immediately required the password again.

Edited July 10, 20232 yr by atomicboy