chuckl Posted September 20, 2009 Posted September 20, 2009 Up early on a Sunday (the only day I can sleep in) because the ISY set my Work Day rountines to run. At 12:26 this morning, the ISY log indicated Mon 09/01/1941 08:30:00 PM -AND- The Program Summary of the ISY indicated a last run time of some programs of 10/08/1977 at 2:58AM *** Here's the interesting part: I then shut down the Admin Console down, restarted it, and the bad run times are gone! Blanks now appear in their place. Took a snapshot of everything and all of it along with a backup of my ISY is on the way to ISY Support. I have a basic ISY. How do I know if I've hit the wall for program stack space and need to purchase the PRO upgrade?
Michel Kohanim Posted September 20, 2009 Posted September 20, 2009 Hi Chuck, In ISY there's no such a thing as program stack space. Every piece of object and memory is mapped out and there's absolutely no way for you to run out of memory without receiving a warning. This problem seems to be Admin Console related. Please check your email for instructions. With kind regards, Michel
chuckl Posted September 27, 2009 Author Posted September 27, 2009 Status Update: As of today, there have been no more incidents of time shifting by my ISY. My ISY NTP is currently pointed to 3.north-america.pool.ntp.org as suggesed and as a precaution, I now CLOSE the Admin Console after use instead of minimizing it and having it run constantly.
Michel Kohanim Posted September 27, 2009 Posted September 27, 2009 Hello chuckl, Thanks so very much for the update. Mike Boulanger has also experienced this issue and as such we put some preventative measures in the code such that dates before 1980 and after 2030 are not accepted. This was done simply because we have not yet been able to figure out what's causing these errors. These fixes should be in our 2.7.7 release. With kind regards, Michel Status Update: As of today, there have been no more incidents of time shifting by my ISY. My ISY NTP is currently pointed to 3.north-america.pool.ntp.org as suggesed and as a precaution, I now CLOSE the Admin Console after use instead of minimizing it and having it run constantly.
Recommended Posts