Unresponsive ISY

[shannong]

Arg!  Catastrophe!!

 

My ISY is unresponsive. I notice some programs weren't executing. Went to my Admin console that's always open on my home server and it was generating socket errors and was unresponsive. Looked at the logging via USB port (which I always have running) and I saw a repeating message about the queue was full.

 

UDQ: Queue(s) Full, message ignored

 

So I rebooted it. It was REALLY slow to reboot fully. I couldn't log in for about 5 min. Even now the console command line is kind of slow. And the Admin console crashed when trying to load after logging in.

Thoughts or suggestions on where to start troubleshooting this one?

 

ISY v4.6.2

[Teken]

Normally this is caused by rapid network resources / programs. Disable all programs and activate one at a time until it faults out. It should be noted rebooting the system will cause the queue full to take some time to fill up / show an error.

 

 

Sent from my iPhone using Tapatalk

[shannong]

How do I do that if I can't load the admin console?

[shannong]

BTW. In the past week I only created one program to turn on a light when a switch is switched on. Hard to do wrong. And no problems for 24 hours after that. No other programs/network resources were changed. The only other thing I did was increase the font size to max size for the Admin console for a new laptop I got which has a very high resolution.

[G W]

Turn it off, disconnect the PLM, turn it on, login and disable all programs. Turn it off, plug in the PLM, power the ISY, login and watch the Event Viewer in lever 3.

 

Sent from my Nexus 6P using Tapatalk

[shannong]

This problem continues to plague me. I disabled all programs using a RESTful call to set a variable I have on the root folder. Forgot I had that and although delayed did finally work.

 

After another reboot I was able to open the Admin console and waited for the initial query to complete. Then I enabled all my programs. Nothing happened. Everything seemed to operate fine.

 

After a several hours it was starting to slow down again. Some programs didn't run. Some ran but delayed.

 

The Event Viewer doesn't show any chatty devices or constant activity. 

 

Any other suggestions on where to look or how to isolate the root cause?

[Teken]

If we assume this is caused by programs a nice diagnostic tool besides the level 3 logs open and viewing is to watch the status colors of each program / folder .

 

If you see rapid changes in color like it's strobing. That is a key indicator that specific program / folder needs attention. I've been fighting with the very same issue here.

 

 

Sent from my iPhone using Tapatalk

[shannong]

I'm not currently believing this to be caused by a programming issue. Although, I certainly can't rule it out.

 

I expanded all my folders and don't see any programs firing. Although I have several hundred spread across two-levels of folders so it's not easy to view them.

 

Arg!

[Teken]

I'm not currently believing this to be caused by a programming issue. Although, I certainly can't rule it out.

 

I expanded all my folders and don't see any programs firing. Although I have several hundred spread across two-levels of folders so it's not easy to view them.

 

Arg!

Nope, you will need to sit and watch for awhile. In my case it's either very apparent or not. The not is due to change in seasons. More specifically I have lots of I/O from power, temperature, water, voice, programs which are updated based on environmental in the home.

 

When it's super hot / cold there are hundreds of programs and variables firing off. That amount of activity seems to be locking up my controller about 24~48 hours in.

 

 

Sent from my iPhone using Tapatalk

[stusviews]

I'm not currently believing this to be caused by a programming issue. Although, I certainly can't rule it out.

 

I expanded all my folders and don't see any programs firing. Although I have several hundred spread across two-levels of folders so it's not easy to view them.

 

Arg!

 

Select My Programs. Create a condition that's false. That should prevent any programs from running. (I don't know if it'll stop State variable triggered programs.). Is  your ISY still running slow?

[MWareman]

This problem continues to plague me. I disabled all programs using a RESTful call to set a variable I have on the root folder.

The RESTful call, what do you have in the Host box for the network resource? If it is 127.0.0.1 there is a known issue that causes ISY to become very unresponsive. If this is the case, change it to the actual lan IP address...

 

Edit: Red herring. I didn’t read properly. However, anyone that uses a network resource to call the ISY itself needs to know this issue exists.

[Brad]

I've had this problem in the past. Usually what caused it was that I had the bright idea to use program state as a Boolean flag. When doing that, you can get into this sort of situation where events are triggered by the programs true/false state and that program or another triggers it into the opposite state... ad nauseam... Infinite loop is born.

 

If you have any code doing that, hunt it down and change the design to use state variables. I'm vaguely remembering that I thought I saw that even if a program is already true and it runs the then side, it caused an event to to get queued and vice versa. With state variables, they only they only queue an event when their value changes.

 

 

Sent from my HTC U11 using Tapatalk

[larryllix]

I've had this problem in the past. Usually what caused it was that I had the bright idea to use program state as a Boolean flag. When doing that, you can get into this sort of situation where events are triggered by the programs true/false state and that program or another triggers it into the opposite state... ad nauseam... Infinite loop is born.

 

If you have any code doing that, hunt it down and change the design to use state variables. I'm vaguely remembering that I thought I saw that even if a program is already true and it runs the then side, it caused an event to to get queued and vice versa. With state variables, they only they only queue an event when their value changes.

 

 

Sent from my HTC U11 using Tapatalk

I consider using a program state bad form and avoid it if at all possible. It is way to obscure and even some variable usage on a trigger driven ISY engine can be hard enough to sleuth.

 

You'll get caught taking days or even weeks of your time and learn the hard way. Or if in formal code school, get expelled for it.

 

Sent from my SGH-I257M using Tapatalk

[paulbates]

I consider using a program state bad form and avoid it if at all possible. It is way to obscure and even some variable usage on a trigger driven ISY engine can be hard enough to sleuth.

 

You'll get caught taking days or even weeks of your time and learn the hard way. Or if in formal code school, get expelled for it.

 

Sent from my SGH-I257M using Tapatalk

 

Using program state as logic is more matter programming style. Like a state variable, a program state is just another event state.

 

I don't look for ways to use it, but in some situations it saves variables and variable handling, and makes the programs more readable with less code.

 

Paul