[SOLVED] ISY Troubles...

[EddieRock]

I noticed that my ISY was not available online (my.isy.io Portal and via my PC using Java) and I could not log into it. I rebooted my ISY and PLM. it would respond but extremely slow. Once I finally got logged in, none of my programs were available, and the logs were empty. I was thinking that I had a run-away program but there were none there. I decided to try and click on "Undo Changes" under program details and all my programs came back or appeared. I clicked on Save changes after that.

 

I then tried to do a backup and then I noticed that all my icons were blank and there the backup/restore options are unavailable.

 

On the main page, there is a red ! on the ISY.

 

After I clicked in the "Undo Changes" the system does seem like it's responding now and I can turn on/off devices from the Main tab.

 

The front of the ISY only has the blue light on. Before and after the restart (unplugging power).

 

Any idea of what's going on?

 

I could do a restore (backup after every change) but I'm afraid to move forward until I get some understanding of what's going on.

 

Also, all the programs do seem to run fine. 

 

Any help would be appreciated

 

EddieRock

 

ISY Version: 4.4.3

 

EDIT: I Got into my logs and attached the error log

 

ISY Error Log.v4.4.3__Thu 2016.03.24 09.53.21 PM.txt

[EddieRock]

I attempted to log in again and the system does seem to be acting normal now. I made another backup. I could restore from Sunday but I would like to know what the problem may have been. 

 

It wouldn't even respond to a ping earlier. It's all back up, responds to pings and is accessible via my.isy.io.

 

Let me now if anyone needs more info to help me troubleshoot.

 

Regards,

 

Ed

 

UPDATE: 

 

It's happening again after 10 minutes or so. here is a latest ping of the device:

 

Request timed out.

Reply from 192.168.0.230: bytes=32 time=3ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Request timed out.

Request timed out.

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Request timed out.

Request timed out.

Reply from 192.168.0.230: bytes=32 time=2ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Request timed out.

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time=4ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Request timed out.

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Request timed out.

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

Request timed out.

Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

[MWareman]

I had this happen when I had a network resource calling http://127.0.0.1 (to loop back and call itself).

 

This isn't supported, and can cause the IP stack to behave like this. Check to make sure that any network resources calling back to the ISY are using the actual IP of the ISY rather than 127.0.0.1.

 

Alternatively, very tight loops and/or recursive programs triggering can cause the ISY to become unresponsive as well. Something else to check for.

[EddieRock]

Thank you @MWareman for the response. 

 

After some troubleshooting last night and this morning, I had a network switch that had gone bad and was flapping some ports. Once I remove that, all the problems had gone away.

 

During my troubleshooting, I had realized that the ISY and PLM were working correctly as everything seemed to work fine from an automation standpoint. So, after putting those puzzle pieces together, I concentrated on my network. Systematically turning things off and/or unplugging them to reduce complexity steered me in the right direction. 

 

Time to go to MicroCenter to pick up a new switch (with a price match on Amazon )

Ed