Mystery reboots Obi 110 build 2774
ProfTech:
That is interesting. I ran syslog for a couple of days but it never crashed. Since then, I have had other network issues not related to the Obi that either required me to reboot it, or an instance where we lost AC for a moment which caused my whole network to lose power. I would also like to know what the 91 means. Anyway, I saved my config a while back and did a paper clip factory restore. I have my fingers crossed but it seems to have possibly cured the situation. Time will tell.
CoalMinerRetired:
I'm kind of like you in that I moved on to pursue this a different way. I did a factory reset on my Obi202, and reentered everything via the ObiTalk portal, which I plan to use until this gets revolved or goes away. And I want to see how the other half lives using the ObiTalk portal on a device under active configuration.
BTW, if you have any exports from the recent past, take a look and see if there's a mystery reboot code.
Edit:
Another mystery on my Obi202, I see that it's now using "3.0.1 (Build: 3741)", whereas before it was on 3722. Hum? For those not on using the ObiTalk portal, I see this in the FirmwareURL field: "IF ( $FWV < 3.0.1.3741 ) FWU http://www.obihai.com/firmware/OBi202-3-0-1-3741.fw" -- noticed via the Web Server-Based Local Configuration (Device IP address), not seen via the ObiTalk portal.
Note to self: Evidently when using the ObiTalk portal you get new firmware updates like this, without having to do anything or click anything, and before they are made available via ***6. An educated guess is these updates are not new feature releases (or they'd be announced as such), they are bug fixes.
Ostracus:
My Obi202 FW: 3.0.1 (Build: 3722)
If it ain't broke... ;D
ProfTech:
Just when I thought it might be Ok... It looks like it rebooted last night with a code of 94 this time. "0 Days 8:46:21 (94)". Maybe I will try putting it back in the portal and see if it gets an update.
CoalMinerRetired:
FYI, I've got a 110 managed via the portal. It's at "1.3.0 (Build: 2774)", haven't seen that firmware change like I did on a 202.
Navigation
[0] Message Index
[#] Next page
[*] Previous page