Kernel.Error SYSTEM REBOOTED (Reason: 3, lifecycle: 3634)<000>
RonR:
You will have have to make changes to the OBi directly while Auto Provisioning is disabled. Unless you actually need to be able to configure an OBi that is at a remote location, the OBiTALK Web Portal doesn't offer any particular advantage over direct configuration. You actually have access to a few more settings and status with direct access.
Huib:
I noticed this morning that my OBi was rebooting, showing code 3 (profile change) as reason. I haven't made any changes recently so I thought "that's odd" but left it at that. Now I noticed it again, same code. Don't know how many times it has done this but it's not right that it's rebooting so many times for no reason.
RonR:
Quote from: Huib on January 21, 2012, 11:35:41 am
I noticed this morning that my OBi was rebooting, showing code 3 (profile change) as reason. I haven't made any changes recently so I thought "that's odd" but left it at that. Now I noticed it again, same code. Don't know how many times it has done this but it's not right that it's rebooting so many times for no reason.
Have you tried temporarily disabling Auto Provisioning to see if it eliminates the reboots and identifies the problem as described on Reply #1 above?
nmssystems1:
yes it does seem to fix the problem of the reboot.. but i have around 25 of these in remote sites
using various dsl, cable and wireless internet service providers.
not using the obi web portal is going to make the managment of the obi devices more time consuming
and complicated.
humm one problem leads to another it would seem..
thanks for all the help and info..
RonR:
Quote from: nmssystems1 on January 21, 2012, 11:49:34 am
yes it does seem to fix the problem of the reboot..
At least the cause of the reboots has apparently been identified and an immediate solution to the problem is known. Presumably, OBihai will fix the problem someday.
Navigation
[0] Message Index
[#] Next page
[*] Previous page