New Polisy / New problem

[bcdavis75]

So I got my shiny blue box today (hurray).  Setup went surprising smoothly.  However, after add a few nodes, my ISY started performing very oddly.  Super slugglish.  Then I couldn't get into at all.  When I eventually did it took forever and would kick me out of the admin console (the credentials screen would reappear).  I restarted the ISY twice.  Same result.  It would allow me to login but extremely slowly and console was not responsive.  Then I turned off the Policy and almost immediately the console became responsive again.

I plugged the Polisy back in and things seemed better... all the new nodes appeared (SimpleControl, MYQ, Kasa).  However, I was still getting logged out of the console every few minutes.  Then I also noticed on the portal tab that the POrtal Integration was offline.  Sure enough, Cloudpoly is not connecting either.

Seems like all the kids are not playing nice . Any help is appreciated.

 

[Bumbershoot]

9 hours ago, bcdavis75 said:

Then I turned off the Policy and almost immediately the console became responsive again.

Basics first, are you certain you don't have an IP address conflict on you network?  Check to be sure either box isn't somehow using an IP address that some other device is using.

I don't use the same nodeservers as you, so I don't know if there's an IP address included in the configuration of any that you're using.  If there is, make sure there isn't a reused address, there, either.

It seems a little unlikely that Polyglot is bombarding your ISY with so much data that it's overwhelmed, but I suppose it could happen.

From the "Dashboard | Details" view of your Polyglot web page, stop each nodeserver, one at a time, and check to see of the situation improves with your ISY.  If it does, after stopping one or more of them of them, then you've possibly found your culprit.

You could SSH into your Polisy and stop the Polyglot service itself from the command line.  Once stopped, if the ISY resumes it's normal functionality, then it's Polyglot that's hosing your ISY.  If you ISY still won't behave (even after a restart leaving the Polisy still running) it could likely be a network configuration issue with the Polisy itself.

Once you've SSH'd into you Polisy, the command to stop Polyglot is: sudo service polyglot stop

 

[Jimbo.Automates]

If you have nodeservers on Polyglot Cloud that are having problems authorizing to your ISY it will flood the ISY with attempts. I had this happen and only fix was @einstein.42 had to manually delete them.

Sent from my Pixel 3 XL using Tapatalk

[bcdavis75]

2 hours ago, Bumbershoot said:

Basics first, are you certain you don't have an IP address conflict on you network?  Check to be sure either box isn't somehow using an IP address that some other device is using.

I don't use the same nodeservers as you, so I don't know if there's an IP address included in the configuration of any that you're using.  If there is, make sure there isn't a reused address, there, either.

It seems a little unlikely that Polyglot is bombarding your ISY with so much data that it's overwhelmed, but I suppose it could happen.

From the "Dashboard | Details" view of your Polyglot web page, stop each nodeserver, one at a time, and check to see of the situation improves with your ISY.  If it does, after stopping one or more of them of them, then you've possibly found your culprit.

You could SSH into your Polisy and stop the Polyglot service itself from the command line.  Once stopped, if the ISY resumes it's normal functionality, then it's Polyglot that's hosing your ISY.  If you ISY still won't behave (even after a restart leaving the Polisy still running) it could likely be a network configuration issue with the Polisy itself.

Once you've SSH'd into you Polisy, the command to stop Polyglot is: sudo service polyglot stop

 

Morning update. Checked my router.  No IP conflicts.

All on it's own, things seem better this morning.  Including the Portal.  Thanks for the troubleshooting tips though.  If the problems re-occur, I'll try all of that.

[bcdavis75]

8 minutes ago, Jimbo said:

If you have nodeservers on Polyglot Cloud that are having problems authorizing to your ISY it will flood the ISY with attempts. I had this happen and only fix was @einstein.42 had to manually delete them.

Sent from my Pixel 3 XL using Tapatalk
 

Hmmm.  Sounds similar.