@Jimbo.Automates Hi Jim, I have restarted a few times, also stopped, and started a few times, upgrade isnt happening. Am nervous to do a uninstall, reinstall same slot as the Elk is by far the most integrated and used NS throughout my programs. 

Thoughts? thanks.

17 minutes ago, dbwarner5 said:

@Jimbo.Automates Hi Jim, I have restarted a few times, also stopped, and started a few times, upgrade isnt happening. Am nervous to do a uninstall, reinstall same slot as the Elk is by far the most integrated and used NS throughout my programs. 

That's a PG3 bug.  Go to "Node Server Store" , Select ELK, Select "Install" of the Perpetual version.  This will show in option "ELK is already installed in slot x, Reinstall here?".   To be safe, I'd backup PG3 first, but I've not heard of this causing any issues.

 

@Jimbo.Automates what about the problem with having to power cycle polisy after connecting to elkrp to get it to connect again?

@Jimbo.Automates what about the problem with having to power cycle polisy after connecting to elkrp to get it to connect again?

Hopefully that is fixed in 3.5.8. I've never seen that happen before.

Sent from my Pixel 6 Pro using Tapatalk

15 minutes ago, Jimbo.Automates said:

Hopefully that is fixed in 3.5.8. I've never seen that happen before.

Sent from my Pixel 6 Pro using Tapatalk
 

It was reproducible.  Both time I connected to ElkRP2 I had to power cycle polisy.  Soft restarts of the node and PG3 did nothing either time.  The first time I also tried power cycling the Elk ethernet module.

It was reproducible.  Both time I connected to ElkRP2 I had to power cycle polisy.  Soft restarts of the node and PG3 did nothing either time.  The first time I also tried power cycling the Elk ethernet module.

Sorry, not clear. Even after upgrading to 3.5.8?

Sent from my Pixel 6 Pro using Tapatalk

23 minutes ago, Jimbo.Automates said:

Sorry, not clear. Even after upgrading to 3.5.8?

Sent from my Pixel 6 Pro using Tapatalk
 

No.  I just did the update a few minutes ago so haven't tried.  It is now running .8  But since you had never seen this issue, I'm assuming you didn't do anything that might fix it between the .7 and .8 versions.  Unless you accidentally fixed it because it was something in common with another issue you did know about.  Just seems very odd to me that an entire power cycle of polisy is needed.  What issue could persist through a restart of the node or a soft restart of polisy?

No.  I just did the update a few minutes ago so haven't tried.  It is now running .8  But since you had never seen this issue, I'm assuming you didn't do anything that might fix it between the .7 and .8 versions.  Unless you accidentally fixed it because it was something in common with another issue you did know about.  Just seems very odd to me that an entire power cycle of polisy is needed.  What issue could persist through a restart of the node or a soft restart of polisy?

There are incompatible issues with the python elk library which caused a lot of issues and hopefully this one as well. The reason it required a reboot was likely because a subprocess didn't exit properly. Please test and let me know if it persists.


Sent from my Pixel 6 Pro using Tapatalk

7 minutes ago, Jimbo.Automates said:

There are incompatible issues with the python elk library which caused a lot of issues and hopefully this one as well. The reason it required a reboot was likely because a subprocess didn't exit properly. Please test and let me know if it persists.


Sent from my Pixel 6 Pro using Tapatalk
 

Wouldn't any processes be reset with a soft reboot?  Anyway, I'll test it out tonight.

I have tested it and it appears to work now.  I connected elkrp2 to the system, disconnected, and ISY still had access to the system.  Thanks.  @Jimbo.Automates