Kernel.Error SYSTEM REBOOTED (Reason: 3, lifecycle: 3634)<000>
nmssystems1:
Any have this problem of the obi rebooting through out the day..
all the units have the new firmware on them..
it does this serveral times a day it seems..
it almost seems like the unit reboots if it can not talk to the google voice servers
after so many attemps.. just and idea not sure what it is..
thanks
here is the entire syslog entry..for the event..
2012-01-20 22:29:10 Kernel.Error 192.168.3.190 SYSTEM REBOOTED (Reason: 3, lifecycle: 3634)<000>
2012-01-20 22:29:10 Local5.Notice 192.168.3.190 ZT: CustomID 1<000>
2012-01-20 22:29:10 Kernel.Emerg 192.168.3.190 SLIC_init ...<000>
2012-01-20 22:29:10 Kernel.Emerg 192.168.3.190 Reset SLIC...<000>
2012-01-20 22:29:10 Local2.Info 192.168.3.190 Setup Provisioning2 for system start! 1800<000>
2012-01-20 22:29:12 Kernel.Emerg 192.168.3.190 SLIC & DAA is initialized<000>
2012-01-20 22:29:14 Kernel.Info 192.168.3.190 Start Main Service Now<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 Voice Main<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 [CPT] --- FXS s/w tone generator (ringback) ---<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 BASESSL:load cert:5<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 BASESSL:Load certificate ok<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 XMPP:State changed from: 0 to:1<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 GTT:Init xmpp node ok<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 XMPP:State changed from: 1 to:2<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 XMPP:Invalid cfg use for xmpp<000>
2012-01-20 22:29:14 Kernel.Debug 192.168.3.190 GTT:xmpp not configured<000>
2012-01-20 22:29:16 Kernel.Debug 192.168.3.190 [SLIC]:Slic#0 ON HOOK<000>
2012-01-20 22:29:18 Kernel.Debug 192.168.3.190 [DAA]: FXO ONHOOK MONITOR<000>
2012-01-20 22:29:19 Kernel.Debug 192.168.3.190 XMPP:State changed from: 2 to:3<000>
2012-01-20 22:29:19 Kernel.Debug 192.168.3.190 TCP:Connect OK(xmpp)14<000>
2012-01-20 22:29:19 Kernel.Debug 192.168.3.190 XMPP:State changed from: 3 to:4<000>
2012-01-20 22:29:19 Kernel.Debug 192.168.3.190 XMPP:Enable reqto<000>
2012-01-20 22:29:19 Kernel.Debug 192.168.3.190 XMPP_PROC:TLS required!<000>
2012-01-20 22:29:19 Kernel.Debug 192.168.3.190 XMPP:State changed from: 4 to:5<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 TC:ssl connected<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:State changed from: 5 to:6<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:Enable reqto<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:new stream restarted from remote, old state=1<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:State changed from: 6 to:8<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:State changed from: 8 to:9<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:Enable reqto<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:new stream restarted from remote, old state=1<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:State changed from: 9 to:10<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:State changed from: 10 to:11<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:State changed from: 11 to:12<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:State changed from: 12 to:13<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:State changed from: 13 to:14<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 XMPP:Disable reqto<000>
2012-01-20 22:29:21 Kernel.Debug 192.168.3.190 GTT:xmpp service up<000>
2012-01-20 22:29:22 Kernel.Debug 192.168.3.190 GTALKVM:Checking VM....<000>
2012-01-20 22:29:22 Kernel.Debug 192.168.3.190 GTALKVM:state changed from 0 to 1<000>
2012-01-20 22:29:22 Kernel.Debug 192.168.3.190 [CPT] --- FXS s/w tone generator (sit_1) ---<000>
2012-01-20 22:29:22 Kernel.Debug 192.168.3.190 TCP:Connect OK(lhttpc)18<000>
2012-01-20 22:29:22 Kernel.Debug 192.168.3.190 Trying to connect ssl<000>
2012-01-20 22:29:23 Kernel.Debug 192.168.3.190 TC:ssl connected<000>
2012-01-20 22:29:23 Kernel.Debug 192.168.3.190 LHC:Response OK<000>
2012-01-20 22:29:23 Kernel.Debug 192.168.3.190 LHC:set Retrying:www.google.com, 1<000>
RonR:
Just as an experiment, log into the OBi directly and temporarily set:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
and see if the periodic reboots go away.
You must click Submit at the bottom of the page and then click Reboot in the upper right corner of the page for these changes to be made. After the reboot, log back in and verify that they took.
Once you determine whether this has any effect on the reboots, you can restore these settings if you wish to by simply checking the Default checkboxes again.
nmssystems1:
ok what do these settings do for the obi?
can you explain?
thanks
RonR:
2012-01-20 22:29:10 Kernel.Error 192.168.3.190 SYSTEM REBOOTED (Reason: 3, lifecycle: 3634)<000>
The reboot reason code being displayed in your Syslog is 3:
3: Reboot after New Profile Invoked
This would seem to indicate that the OBiTALK Web Portal may be repeatedly sending a new profile to your OBi, causing it to reboot each time.
Disabling Auto Provisioning will stop the loading of new profiles from the OBiTALK Web Portal and might identify the source of your unexpected reboots.
nmssystems1:
I kind of thought it was getting some kind of update from the web portal config files etc..
then restarting..
my next question would be if i change some thing on the web portal will this particular obi device that i have disabled provisioning on. will it get the update change from the obitalk web portal? my guess is no it will not.
this means i can not manage the obi device that has provisioning disabled using the obitalk web portal?
thanks
Navigation
[0] Message Index
[#] Next page