I have a 333 that is locking up and has this message in the log file. Anybody can tell me what it means?
Thank you.
What is the message ??
:> look at the topic
avantwireless -
I have had the same issue - in ROS 3.7 on an RB333
OK MT - what causes this? I hesitate to upgrade at the moment (3.9).
R/
same problems on rb600
jan/01/1970 01:00:05 system,error,critical router was rebooted without proper shutdown (cause 1)
mt 3.10 newest firmware 2.15
I am also getting this, any news on what is cause 1?
Ekkas
I have not had this problem myself, but others are blaming it on the voltage monitor circuit. It apparently may read high in some units, and shut down if it determines the voltage is too high (>30v). In other posts I have read, the users affected by this say the solution was to use an 18v power supply rather that 24v.
Can anyone confirm or deny this claim?
I saw the problem with a 13.5V input… I don’t think it is cured going to 24V supply. I think mine was cured by the latest firmware for the board.
Got 18V, ROS 3.10 with FW 2.15 since it came out. Reboots only started recently.
Seems to happen when I do something in Dude, like setting up or changing some settings. If I leave it alone in Dude, it doesn’t reboot. Not sure if that is the cause, just noticed that it reboots then.
Ekkas
I have the same problem with RB333. It seems to me that the mix of 2.9.51 and 3.10 and EOIP. I change the other End of the EOIP to 3.10 and the problem disappears. In an other case it does not work. In this case I changed the end of the EOIP to an other board and the problem was gone. Today I had it on an other RB333. I assume that it is a little bit to warm today (34 Cel). I will change the Speed from 333 to 266 Mhz. May it works…
I will report if something new happen…
My RB333 have no EoIP or any firewall/mangle rules and it reboots at random times, even at night when it’s cold and there
's little traffic. So I do not think it’s that reason. I haven’t changed any settings and it’s been up now for 1 day, but still it randomly reboots from time to time. I have other RB333 that is up for 15 days without problems.
I also still have a RB333 that is rebooting with this in the logs. MT guys told me to set CPU-speed lower, but that will kind of defeat the object of buying a ‘high-powered’ routerboard…
if your RouterOS and Bootloader both up to date? Have you uninstalled all packages that you don’t use?
Yes, ROS 3.11/FW2.16
Also only
Advanced-tools
dhcp
routerboard
routing
wireless
security
system
packages installed.
I am also getting this. It all began when I decided to upgrade from 3.2. I tried 3.10 and 3.11. Also, I have a RB333. Not sure how to check boot version. The supply is 24V. Didn’t have any problems with 3.2. I’m debating on downgrading it back. I did have 2 unused EOIP interfaces. I disabled them and so far everything seems good. Been good for 48 hours; but it is probably too early to know.
Eric
Strange thing in my case.
I have RB333 RouterOS v3.10 that was randomly rebooting with that error (+ watchdog timer one) during approx 1 month, and it stopped ~18 days ago. When I log in the ONLY difference I can see is this:
system routerboard print
routerboard: yes
model: "333"
serial-number: "XXXXXXXXXXXXX"
current-firmware: ""
upgrade-firmware: "2.15"
There is no info about current firmware! I am sure it is v2.15, but I dont know how that info could be lost. I dont want to do anything for now, for it’s functioning well.
system resource print
uptime: 2w4d18h1m42s
version: "3.10"
free-memory: 47964kB
total-memory: 62324kB
cpu: "e300c2"
cpu-count: 1
cpu-frequency: 333MHz
cpu-load: 12
free-hdd-space: 40196kB
total-hdd-space: 61440kB
write-sect-since-reboot: 1063
write-sect-total: 1063
bad-blocks: 0
architecture-name: "powerpc"
board-name: "RB333"
I have also same problem with a RB133C, upgraded to 3.11 & then FW 2.16 but it also still shows empty current firmware.
So far I’ve been stable for 3 days since turning off all my EOIP interfaces. Again its still too early to tell if that was it.
Eric
Mine runs just fine for days on end, then suddenly reboot, maybe one or twice in a day, then fine again…
Yeah I’m getting the same thing here and I am using EoIP tunnels as well…
3.11 loader
Just upgraded the Firmware version to 2.16 of 2.16
If this keeps happening I’m gunna try turning off the tunnel, see if that makes a difference