kzboray Posted April 8, 2023 Posted April 8, 2023 (edited) My Polisy spontaneously rebooted. I was notified via the new portal status and ignored it until after dinner much to my dismay. As it turned out the entire system was non-functional. Even logging in via AC was weird. I have gotten back some function, but am still trying to determine what happened and how to fully correct it. Here is what my AC login looks like now. The first issue I had trying to access IoX was that the password had reverted to factory default causing not just frustration when trying to access IoX but also caused Polyglot to disconnect due to a mismatch in passwords. Once I corrected that I was then able to log into IoX but it wasn't communicating with Polyglot yet and all Insteon devices where showing they needed to be updated, however the update icon on the top menu wasn't there! After several PoliSy reboots I finally loaded up an IoX backup and all Insteon devices came back, setting the password in Polyglot got all the NS's back, but there is obviously still something wrong as the AC top menu is missing a couple of options, I cannot communicate via the could to my IoX and the Portal still shows my device off line. I'll have to open a ticket at this point to see if Michel and his band of merry men can sort out what's happened. I am simply sharing a pretty catastrophic event that I was mostly able to recover from because I keep up to date backups! Edited April 8, 2023 by kzboray 1
wmcneil Posted April 11, 2023 Posted April 11, 2023 @kzboray, I've been getting spontaneous reboots of my polisy about once a day or so. Luckily so far, there has not been any loss of functionality. I'm running IoX 5.5.9 , and am waiting for the next IoX code release and hoping it fixes the problem.
DennisC Posted April 11, 2023 Posted April 11, 2023 26 minutes ago, wmcneil said: @kzboray, I've been getting spontaneous reboots of my polisy about once a day or so. Luckily so far, there has not been any loss of functionality. I'm running IoX 5.5.9 , and am waiting for the next IoX code release and hoping it fixes the problem. I have 2 Polisy's running v5.5.9 at two different locations and do not experience random reboots. Have you opened a UD support ticket? They can't fix something they don't know about. Have you checked your event and error log? Also haven't seen other Polisy owner's reporting this, could be this issue is specific to your installation. Try changing the power supply. 2
larryllix Posted April 11, 2023 Posted April 11, 2023 (edited) Possibly broken cable wiring inside the PSU cable at the connector from previous snags on it, or just a messed up connector contact inside the polisy. Try bending the cable multiple directions, at the connector (each end?) to see if you can cause it to happen. Edited April 11, 2023 by larryllix
kzboray Posted April 11, 2023 Author Posted April 11, 2023 Just a follow up. My PoliSy is now back to normal, but had experienced a loss of it's product ID. This was resolved via a remote desktop session by Michel and team. It took some digging to find and is definitely a bug. Since no one has mentioned it before and Michel had to do quit a bit of investigation to uncover what had happened I surmise it was the first time UD had run up against this particular bug. It isn't something the vast majority of owners should ever have to deal with.@wmcneil There was an issue with daily reboots in the previous version of firmware prior to 5.5.9. I'm pretty sure that issue was resolved in 5.5.9. I would double check you power supply as suggested by @larryllix and if that doesn't fix it open a ticket with UD.
wmcneil Posted April 11, 2023 Posted April 11, 2023 1 hour ago, kzboray said: @wmcneil There was an issue with daily reboots in the previous version of firmware prior to 5.5.9. I'm pretty sure that issue was resolved in 5.5.9. I would double check you power supply as suggested by @larryllix and if that doesn't fix it open a ticket with UD. @kzborayYes, there was a reboot issue resolved in a firmware version prior to 5.5.9 , so the reboot issue I am experiencing is something different. I realized today that the reboot is frequently happening not long after a query all is issued, so that may be a hint. I do have a ticket open and am waiting for UD response. 1
wmcneil Posted April 12, 2023 Posted April 12, 2023 The UD folks are helping me with the ticket I opened. Debug is not complete yet, but a couple of points that may help others: I have a rather old polisy. It shipped with a 12VDC 1amp power supply. One of the things I am trying currently is the use of a 12VDC 2amp supply. This was at the suggestion of UD. (I am using the ZMatter card in the polisy.) I have a program with an empty 'if' section and an email notification in the 'then' section. I have the "run at startup" option selected for this program. This causes the email notification to occur whenever the ISY service on the polisy box restarts. What UD has clarified is that the restart of the ISY service does necessarily been the box has rebooted. "Random" ISY service restarts should not be happening, nor should "random" reboots. In my case, I have been experiencing "random" ISY service restarts, not "random" reboots. Time will tell if the different power supply affects the behavior. 4
DaveStLou Posted April 13, 2023 Posted April 13, 2023 6 hours ago, wmcneil said: The UD folks are helping me with the ticket I opened. Debug is not complete yet, but a couple of points that may help others: I have a rather old polisy. It shipped with a 12VDC 1amp power supply. One of the things I am trying currently is the use of a 12VDC 2amp supply. This was at the suggestion of UD. (I am using the ZMatter card in the polisy.) I have a program with an empty 'if' section and an email notification in the 'then' section. I have the "run at startup" option selected for this program. This causes the email notification to occur whenever the ISY service on the polisy box restarts. What UD has clarified is that the restart of the ISY service does necessarily been the box has rebooted. "Random" ISY service restarts should not be happening, nor should "random" reboots. In my case, I have been experiencing "random" ISY service restarts, not "random" reboots. Time will tell if the different power supply affects the behavior. Very interesting. I had 3 or 4 "reboots" of my Polisy earlier this week. I have a program that sends me a Pushover notice - very similar to your email. I have not opened a ticket but I have reviewed the logs and haven't found anything obvious. In the meantime I've ordered a new power supply from UDI. It's on its way.
wmcneil Posted April 14, 2023 Posted April 14, 2023 (edited) On 4/12/2023 at 3:35 PM, wmcneil said: The UD folks are helping me with the ticket I opened. Debug is not complete yet, but a couple of points that may help others: I have a rather old polisy. It shipped with a 12VDC 1amp power supply. One of the things I am trying currently is the use of a 12VDC 2amp supply. This was at the suggestion of UD. (I am using the ZMatter card in the polisy.) I have a program with an empty 'if' section and an email notification in the 'then' section. I have the "run at startup" option selected for this program. This causes the email notification to occur whenever the ISY service on the polisy box restarts. What UD has clarified is that the restart of the ISY service does necessarily been the box has rebooted. "Random" ISY service restarts should not be happening, nor should "random" reboots. In my case, I have been experiencing "random" ISY service restarts, not "random" reboots. Time will tell if the different power supply affects the behavior. Update: The new power supply did not solve the problem. The isy service restarted several times early this morning, then when I manually initiated a 'query all', the box crashed and generated a *.core file (and then restarted), which the UD folks are debugging now. Edited April 14, 2023 by wmcneil 1 2
johnnyt Posted April 29, 2023 Posted April 29, 2023 Interesting. Although I've been using Polisy (one of the first ones out) for PG3 for a while now without problem, I just moved to IoP 2 days ago and had a spontaneous reboot last night. Of course it could be unrelated but maybe adding the zmatter board and the new processing demands of IoP is taxing the PS. Does anyone know what size the connector into Polis is?
johnnyt Posted April 30, 2023 Posted April 30, 2023 59 minutes ago, DennisC said: And the Polisy power supply is 12V 2A. Mine is one of the first ones made, which came with a 1A power supply
DennisC Posted April 30, 2023 Posted April 30, 2023 1 minute ago, johnnyt said: Mine is one of the first ones made, which came with a 1A power supply It was latter upgraded to 2A and if you decide later to use UD's ZMatter dongle, you would want the 2amp power supply. It won't hurt to use the 2 amp now, and you will be prepared. The load will only draw what it needs.
johnnyt Posted April 30, 2023 Posted April 30, 2023 8 minutes ago, DennisC said: It was latter upgraded to 2A and if you decide later to use UD's ZMatter dongle, you would want the 2amp power supply. It won't hurt to use the 2 amp now, and you will be prepared. The load will only draw what it needs. I do have the zmatter board in it and it's been there for a couple of months, although it and CPU were mostly idling until I migrated to IoP a couple of days ago. Before that it was only running 4 node servers. I went through my e-junk drawer and found a 2.5A PS with same polarity (+ on the inside) so I'm using that now.
wmcneil Posted April 30, 2023 Posted April 30, 2023 On 4/14/2023 at 1:36 PM, wmcneil said: Update: The new power supply did not solve the problem. The isy service restarted several times early this morning, then when I manually initiated a 'query all', the box crashed and generated a *.core file (and then restarted), which the UD folks are debugging now. My Polisy is continuing to restart the ISY service typically at least once when a program runs a query all at 3AM. This frequently also coincides with a core file dump. UD folks weren't able to pinpoint anything with the first core file I gave them. I have given them a second core file....It's certainly possible some hardware is broken in my polisy I guess.
Michel Kohanim Posted May 3, 2023 Posted May 3, 2023 @wmcneil, We have not been able to reproduce. Looking at your core file, it seems to be a faulty hardware. Will contact you via your ticket. With kind regards, Michel
theitprofessor Posted May 4, 2023 Posted May 4, 2023 I can now add my Polisy to this list of phantom reboots. It happen to mine this morning. Very weird, no idea what caused it.
DennisC Posted May 4, 2023 Posted May 4, 2023 1 hour ago, theitprofessor said: I can now add my Polisy to this list of phantom reboots. It happen to mine this morning. Very weird, no idea what caused it. What firmware and UI are you on?
Michel Kohanim Posted May 5, 2023 Posted May 5, 2023 @theitprofessor, In addition to the question from @DennisC, was it an actual hardware reboot or just IoX? With kind regards, Michel
theitprofessor Posted May 7, 2023 Posted May 7, 2023 IoP Firmware & UI are both on 5.5.9. I'm not sure what to look for in the log and which log to look in. If you can be specific I will take a look and get back to you.
DennisC Posted May 7, 2023 Posted May 7, 2023 53 minutes ago, theitprofessor said: IoP Firmware & UI are both on 5.5.9. I'm not sure what to look for in the log and which log to look in. If you can be specific I will take a look and get back to you. You should be on the latest firmware. Upgrade to v5 6.0 and be sure to clear Java cache and download a new start jnlp to get a new Launcher to access the admin console. Try looking in the event viewer around the last time of your reboot to see if there is any info.
DennisC Posted May 7, 2023 Posted May 7, 2023 52 minutes ago, theitprofessor said: Done, upgrade complete. Let us know if you experience any additional unexpected reboots and be sure to check logs.
wmcneil Posted May 23, 2023 Posted May 23, 2023 On 5/3/2023 at 3:39 PM, Michel Kohanim said: @wmcneil, We have not been able to reproduce. Looking at your core file, it seems to be a faulty hardware. Will contact you via your ticket. With kind regards, Michel Unfortunately a new polisy box did not solve the problem with spurious ISY Service restarts at my home location. I am also seeing occasional restarts at my second home. In both cases, when this happens, it is not long after a query all operation. Sometimes a core file is generated. The UD folks are back to looking at one of the core dumps.
Recommended Posts