Obi200 Stability?
LTN1:
Quote from: Time_Lord on May 19, 2018, 09:39:57 am
Quote from: SteveInWA on May 16, 2018, 01:08:55 pm
I'm not clear on how you are using a POE switch with a OBi 200. The POE standard is 48 volts. Aside from that, whatever you are doing to drop that voltage (if you are!) may be failing. If you can plug in an ordinary power "wall wart" 12VDC power adapter and use that instead, it would be worth it for diagnostic purposes.
Trust me on this one, I have an adapter that takes PoE in and splits it to ethernet and power for none PoE devices. Plus if it was a power related issue the reboot code would be 0 (zero).
Just checked the Obi200 a few minutes ago and again the uptime was reset to "0 Days 1:17:18 (3)"
The reset code of 3 says "3: Reboot after New Profile Invoked" I made no changes, certainly not within the last hour and 17 minutes, and the Software version is still 3.2.2 (Build: 5859EX), same as it was when I started the thread.
So my question remains what new profile is obi pushing that requires a restart, and why are they pushing profile changes?
-TL
Rather than asking people on this forum how to troubleshoot something that could possibly be related to using PoE in an OBi200 device not created to do PoE, why don't you use the original power adapter (and remove the PoE) for the OBi200 for a day or more and see if you get the same issues? If the same issue exists, we can rule out the PoE. If the issue doesn't continue, then it could be the PoE causing a glitch.
Time_Lord:
I've enabled syslog and I'm forwarding it to another system, I'm accepting all messages and the obi sends debug level messages so maybe I'll get something of value to see what is being sent that is causing a reload "type 3".
-TL
Time_Lord:
I though I had an uptime record, the OBI was up for 23 days, I checked this morning at it restarted again, reason "3" configuration change. "0 Days 7:38:22 (3)" This puts the reload at about 1:15am this morning, I can assure you I was not making changes to the device.
Because I started syslog (see below) I was able to obtain some information, apparently a configuration check/push was done from obi which then a reload was issued.
What changes is obi pushing to the device?
This at least proves that my power is stable even with my PoE adapter as the reboot was commanded not caused by power.
-TL
at 1:16am -
Jun 14 01:16:47 172.18.19.19 Obi200: PNNCOMM:Receive sync req, set auto config
Jun 14 01:16:47 172.18.19.19 Obi200: We will check OBt config in 10 s
Jun 14 01:16:57 172.18.19.19 Obi200: PROV: Start to download files ...
Jun 14 01:16:57 172.18.19.19 Obi200: TCP:Connect OK(HTTP GET)40
Jun 14 01:16:57 172.18.19.19 Obi200: Trying to connect ssl
Jun 14 01:16:57 172.18.19.19 Obi200: TC:ssl connected
Jun 14 01:16:57 172.18.19.19 Obi200: HTTPC: Server responses: 200
Jun 14 01:16:58 172.18.19.19 Obi200: PROV: Update Config with (0, 1)
Jun 14 01:16:58 172.18.19.19 Obi200: PROV: Start to download files ...
Jun 14 01:16:58 172.18.19.19 Obi200: TCP:Connect OK(HTTP GET)40
Jun 14 01:16:58 172.18.19.19 Obi200: Trying to connect ssl
Jun 14 01:16:58 172.18.19.19 Obi200: TC:ssl connected
Jun 14 01:16:58 172.18.19.19 Obi200: HTTPC: Server responses: 200
Jun 14 01:16:58 172.18.19.19 Obi200: PROV: Update Config with (0, 1)
Jun 14 01:16:58 172.18.19.19 Obi200: PROV: Update Config with (0, 1)
Jun 14 01:16:58 172.18.19.19 Obi200: PARAM have been changed 2...
Jun 14 01:16:58 172.18.19.19 Obi200: Reboot is scheduled in 1 second(s)
Jun 14 01:16:58 172.18.19.19 Obi200: We will check OBt config in 86400 s
Jun 14 01:16:58 172.18.19.19 Obi200: PARAM Cache Write Back(256 bytes)
Jun 14 01:16:59 172.18.19.19 Obi200: Reboot checking.....
Jun 14 01:16:59 172.18.19.19 Obi200: Final Cleanup before reboot....
Jun 14 01:17:00 172.18.19.19 Obi200: TCP:Broken Connection(spreg) 32 -1
Jun 14 01:17:00 172.18.19.19 Obi200: REG:HandleTcpEvent 3;wc=0
Jun 14 01:17:00 172.18.19.19 Obi200: SP2:Restart TCP Connect:ac121313:5889->4009f2ac:5061
Jun 14 01:17:00 172.18.19.19 Obi200: TLS-EXT Hostname:obihai.telephony.goog
Jun 14 01:17:00 172.18.19.19 Obi200: TCP:Connect OK(spreg)32
Jun 14 01:17:00 172.18.19.19 Obi200: Trying to connect ssl
Jun 14 01:17:00 172.18.19.19 Obi200: TC:ssl connected
Jun 14 01:17:00 172.18.19.19 Obi200: REG:HandleTcpEvent 2;wc=1
Jun 14 01:17:00 172.18.19.19 Obi200: Goodbye! Reboot Now. (reason: 3)
ProfTech:
To: Time_Lord According to your syslog this certainly appears to be tied to Google Voice and the portal. Google is in the process of changing their entire protocol [that is why they installed new firmware in your Obi] and this is supposed to be complete June 18. I would recommend waiting until after then and see what happens. I don't use Google voice any more precisely due to all of this so can't shed any light but if the issue persists after June 18 you might be able to stop it by removing the Obi from the portal but I don't know if that is possible in Googles new scheme.
chilirock:
Strange. I manage two devices on my account. I just checked and it looks like both rebooted early morning today. The reason code as viewed from ObiExpert mode on the portal is not showing for either.
As a side note, I've had the Uptime on my Obi200 go as high as 8 - 9 weeks. Usually, it's shorter because I've made a setting change or applied new firmware that results in a reboot.
Navigation
[0] Message Index
[#] Next page
[*] Previous page