Strange router problem

RouterOS General
1

Hi everyone,
first to say that problem is solved with reset button, but I’d like to start discussion to figure out how this problem happened.

Board: RB951-2n (mispbe)
OS: 6.33.3

Router gave no response, no reaction on any action:
When LAN cable was pluged-in, LED didn’t blinked.
After several power off, nothing changed.
Every network segments what are connected directly threw this router was unavailable.

At the end, I held reset button 5 sec, and everything works from that moment.
I checked log, and first line I found is:
Mar/27/2016 03:00:03 - system,error,critical - router was rebooted without proper shutdown
saw interface disconnected, expected data lost… (don’t have anymore this part of log :frowning: )
and between Mar/27/2016 03:00:45 and Mar/28/2016 12:04:00 (reset time) there was no log activity

Interesting thing that this night was daylight saving change (2 AM became 3 AM)

Can this cause error, or maybe something else?

Cheers

2

There is any autosupout file?

3

Here is last supout result:

                   uptime: 11m46s
                  version: 6.33.3 (stable)
               build-time: Dec/03/2015 16:08:10
              free-memory: 5.3MiB
             total-memory: 32.0MiB
                      cpu: MIPS 24Kc V7.4
                cpu-count: 1
            cpu-frequency: 360MHz
                 cpu-load: 100%
           free-hdd-space: 45.0MiB
          total-hdd-space: 64.0MiB
  write-sect-since-reboot: 1205
         write-sect-total: 1205
               bad-blocks: 2.8%
        architecture-name: mipsbe
               board-name: RB951-2n
                 platform: MikroTik

CLOCK
                  time: 23:02:40
                  date: mar/28/2016
  time-zone-autodetect: no
        time-zone-name: CET
            gmt-offset: +02:00
            dst-active: yes

IRQs
Flags: ro - read-only
 #    IRQ USERS                                    CPU ACTIVE-CPU         COUNT
 0      2 wlan1                                   auto          0        18 964
 1      3 usb1                                    auto          0             0
 2      4 WAN                                     auto          0        18 298
 3      5 switch0                                 auto          0        36 633

SYSTEM
Linux MikroTik 3.3.5 #1 Thu Dec 3 14:44:59 EET 2015 mips unknown
CPU ACTIVE-CPU         COUNT
 0      2 wlan1                                   auto          0        18 964
 1      3 usb1                                    auto          0             0
 2      4 WAN                                     auto          0        18 298
 3      5 switch0                                 auto          0        36 633

SYSTEM
Linux MikroTik 3.3.5 #1 Thu Dec 3 14:44:59 EET 2015 mips unknown
MEMORY
MemTotal:          27936 kB
MemFree:            1128 kB
Buffers:               0 kB
Cached:             6820 kB
SwapCached:            0 kB
Active:             9088 kB
Inactive:           2368 kB
Active(anon):       6820 kB
Inactive(anon):       60 kB
Active(file):       2268 kB
Inactive(file):     2308 kB
Unevictable:        2652 kB
Mlocked:            2332 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:          7308 kB
Mapped:             4588 kB
Shmem:               152 kB
Slab:               7924 kB
SReclaimable:       1920 kB
SUnreclaim:         6004 kB
KernelStack:         520 kB
PageTables:          736 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:       13968 kB
Committed_AS:      13516 kB
VmallocTotal:     261940 kB
VmallocUsed:       31972 kB
VmallocChunk:     220464 kB
CPU
system type		: Mikrotik RB951-2n
processor		: 0
cpu model		: MIPS 24Kc V7.4
cpu MHz			: 360.000
BogoMIPS		: 239.61
wait instruction	: yes
microsecond timers	: yes
tlb_entries		: 16
extra interrupt vector	: no
hardware watchpoint	: yes, count: 4, address/irw mask: [0x0000, 0x0ff8, 0x0ff8, 0x0ff8]
ASEs implemented	: mips16
shadow register sets	: 1
kscratch registers	: 0
core			: 0
VCED exceptions		: not available
VCEI exceptions		: not available
4

The thing is supout would be more useful if generated when the problem happened.

Default System > Watchdog setting is to generate supout file automatically, as you mentioned the router rebooted itself (or looks like) that would have been the more useful supout.

In any case 6.33.3 isn’t neither bugfix nor current version, so guess there’s no point in sending the info to mikrotik as in case it has been a bug it may have been already fixed.

CCRs had a similar bug last year, and as its understandable lots of people reported it.

I’d netinstall that unit in any case.

Have you checked System > routerboard to see if firmware is up to date?