Mark Arzillo Posted January 4, 2018 Share Posted January 4, 2018 A few days ago I added a program that runs at startup and sends me an email saying the ISY restarted. I added some additional info such as how long it has been running prior to the reboot. After doing that I am noticing the ISY has restarted on its own 4 times. Anyone have any idea why this might be happening? Restarted on 2018/01/04 at 1:07:46 AM - Last Runtime was 234 minutes Restarted on 2018/01/03 at 9:12:10 PM - Last Runtime was 2866 minutes Restarted on 2018/01/01 at 9:24:34 PM - Last Runtime was 32 minutes Restarted on 2018/01/01 at 8:51:12 PM - Last Runtime was 289 minutes Link to comment
paulbates Posted January 4, 2018 Share Posted January 4, 2018 I have a program with a similar function and it has only run when I reboot the ISY, or there is a powerfailure. Typically programs set to run at start-up have no "If" clause? Is that the case for yours? Meaning the existence of an "if" clause might cause the program to run even though the ISY did not reboot Paul Link to comment
Teken Posted January 4, 2018 Share Posted January 4, 2018 A few days ago I added a program that runs at startup and sends me an email saying the ISY restarted. I added some additional info such as how long it has been running prior to the reboot. After doing that I am noticing the ISY has restarted on its own 4 times. Anyone have any idea why this might be happening? Restarted on 2018/01/04 at 1:07:46 AM - Last Runtime was 234 minutes Restarted on 2018/01/03 at 9:12:10 PM - Last Runtime was 2866 minutes Restarted on 2018/01/01 at 9:24:34 PM - Last Runtime was 32 minutes Restarted on 2018/01/01 at 8:51:12 PM - Last Runtime was 289 minutes One thing to point out is if your system is very loaded with tight loop programs this can cause the system to hang and freeze. I personally don't believe tracking the up time minutes is a good course of action. Monitoring the hourly up time removes any possible time constraints on the system and even balances out program conflicts. Link to comment
Mark Arzillo Posted January 4, 2018 Author Share Posted January 4, 2018 I have a program with a similar function and it has only run when I reboot the ISY, or there is a powerfailure. Typically programs set to run at start-up have no "If" clause? Is that the case for yours? Meaning the existence of an "if" clause might cause the program to run even though the ISY did not reboot Paul In my case I do not have an "If" clause. Each time it reboots (or I got the reboot message) I verify by looking at the startup time in the System Status. I verified that each reboot message did, in fact, get caused by an actual reboot as noted in the startup time. One thing to point out is if your system is very loaded with tight loop programs this can cause the system to hang and freeze. I personally don't believe tracking the up time minutes is a good course of action. Monitoring the hourly up time removes any possible time constraints on the system and even balances out program conflicts. I wouldn't have thought a 1 minute timer would overload the system. One second loops yes, but not not one minute loops. In any case I had 9 loop programs that ran every minute to track the time on or off for a given device including the ISY itself. I've disabled all of them but am keeping the reboot notify active to see if I still see the random reboots. Thanks for the tip Teken. Hopefully that stops the random reboots. Link to comment
paulbates Posted January 4, 2018 Share Posted January 4, 2018 To Teken's point, how you are using your ISY programs may influence or cause the rebooting. Some basic systems "blocking and tackling" questions How many programs do you have? Memory use: Go to tools, diagnostics, system status, paste a graphic of the response or type it in TIght loop programs: Go to the programs tab, rightclick on an item, pick status icons and detailed Go through and look at all running programs... are any continuous flickering and flashing (sign of a tight loop mentioned by teken) How many? If you are able to, disable those programs for a few days and see if the rebooting stops There's other memory diagnostics through telnet, but I'm not 100% clear how to interpret, lets start with the above Paul Link to comment
Teken Posted January 4, 2018 Share Posted January 4, 2018 Just to offer a little more insight regarding the folder colors. You can literally see folders flickering to what appears to be strobing none stop. Even if you don't see multiple folders strobing or changing state quickly. Be aware the ISY Series Controller is essentially a smart clock with a FIFO (First In First Out) operations. Meaning every thing happens in sequential order this is why its also important to cut down on *Run at Startup* programs. Also, something that has reduced the amount of boot time and responsiveness is to disable the polling of the Insteon network upon reboot. When you surpass hundreds of programs and hundreds of network resources all of these small things like reduced run at start up and polling the Insteon network helps the stability of the system. Lastly, if you have lots of inbound REST / out bound network resources being pushed to other cloud hosted services. These can slow down the ISY Series Controller to a point where the system appears to be in a unknown state of frozen, unresponsive, to locked up. Link to comment
Mark Arzillo Posted January 4, 2018 Author Share Posted January 4, 2018 To Teken's point, how you are using your ISY programs may influence or cause the rebooting. Some basic systems "blocking and tackling" questions How many programs do you have? Memory use: Go to tools, diagnostics, system status, paste a graphic of the response or type it in TIght loop programs: Go to the programs tab, rightclick on an item, pick status icons and detailed Go through and look at all running programs... are any continuous flickering and flashing (sign of a tight loop mentioned by teken) How many? If you are able to, disable those programs for a few days and see if the rebooting stops There's other memory diagnostics through telnet, but I'm not 100% clear how to interpret, lets start with the above Paul Paul, Thanks for the feedback... I have 57 total programs. 18 are disabled (ran on 1 minute loop) and the other 39 are enabled. Memory looks good. Total: 3956MB, Reserved: 395MB, Used: 10MB, Bad: 0MB, Free: 3550MB. I don't see any tight loop programs running as the ones I had running based on time last ran + 1 minute are disabled. They were more me testing out concepts anyway so nothing critical. After disabling the timer programs I had (9 total) that with an If Time is Last Run Time for 'program name' + 1 minute I have not had any reboots but it's only been a few hours. Typical only see the reboot once per day and sometimes twice. I'll give it a few days and see what happens. If I get no reboots I'm going to enable those programs again to see if the reboots come back. That will confirm that it's those +1 minute programs causing the issue. Having said that, I don't see why a program running once per minute would cause this or be considered a "tight running program". Perhaps it's my lack of knowledge on how the ISY processes state and executes programs. I'm quite familiar with many programming languages (been a developer for 30+ years) but the ISY is a bit different than what I have worked with in the past. Link to comment
paulbates Posted January 5, 2018 Share Posted January 5, 2018 Mark Something else is wrong. All of your program and memory setup look fine Once a minute should not be a problem. I have routines for my furnaces (x2) does a runtime calc for humidification cycles that repeat and count up runtime once a minute. Both can be running at the same time. I'm at 76 programs. I've had my ISY over 3 years and can't recall a reboot that wasn't me rebooting or a power failure. I've also been on the alpha v5. I would suggest submitting a ticket, and ISY can help figure this out, its not normal. Provide a link back to this thread Paul Link to comment
Mark Arzillo Posted January 6, 2018 Author Share Posted January 6, 2018 Mark Something else is wrong. All of your program and memory setup look fine Once a minute should not be a problem. I have routines for my furnaces (x2) does a runtime calc for humidification cycles that repeat and count up runtime once a minute. Both can be running at the same time. I'm at 76 programs. I've had my ISY over 3 years and can't recall a reboot that wasn't me rebooting or a power failure. I've also been on the alpha v5. I would suggest submitting a ticket, and ISY can help figure this out, its not normal. Provide a link back to this thread Paul Thanks Paul. I just submitted a ticket. Since disabling the looping programs I did get another unsolicited reboot today at 9:27pm. Link to comment
MWareman Posted January 8, 2018 Share Posted January 8, 2018 Do you have any network resources calling 127.0.0.1 (to call the local REST API)? This can cause unsolicited hangs or reboots.... Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.