Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[RYAT3]

02:36 am....   Whatever code 16 means! 

[GreenBay42]

Never seen that before. I will try to find out what that means.

[GreenBay42]

Was there any activity in the log right before (i.e. anything that triggered the error?)

Techs will message the engineers tonight and they will probably ask for more details.

[RYAT3]

I've never seen it either.

Nothing specific in the log.  192.168.0.100 is a local computer that logs into the DNR-202L to view.

I can get some info on through a google search.  I'm not sure if that relates to the DNR-202L. 

This menu allows to configure system to reboot, when an specific IP address does not respond, or when it detects, that the software has locked up. The detection is done in two ways: Software watchdog timer (mostly caused by hardware malfunction) device can recover itself with reboot.Oct 13, 2017
Manual:System/Watchdog - MikroTik Wiki
https://wiki.mikrotik.com/wiki/Manual:System/Watchdog

 
2017/11/15  06:20:24  admin login Ok from 192.168.0.100
2017/11/15  02:37:00  usb1 mounted successfully.
2017/11/15  02:36:51  network set to DHCP
2017/11/15  02:36:45  system power on.
2017/11/15  02:36:18  system watch-dog reboot.(code 16)
2017/11/14  13:52:16  admin login Ok from 192.168.0.100
2017/11/14  09:35:08  admin login Ok from 192.168.0.100
2017/11/14  09:34:50  network set to DHCP
2017/11/14  09:34:41  network port connected.
2017/11/14  09:34:40  network port disconnected.
2017/11/14  09:33:49  usb1 mounted successfully.
2017/11/14  09:34:00  system set to new time 2017/11/14 09:33:49.
2017/11/14  09:33:45  network set to DHCP
2017/11/14  09:33:39  system power on.
2017/11/14  09:33:06  system abnormal power off.
2017/11/14  09:25:08  admin login Ok from 192.168.0.100

[GreenBay42]

The engineers will look into this. The US office is closed til Monday so I may not hear anything until next week.

[FurryNutz]

Not seeing this in my logs...

[RYAT3]

The engineers will look into this. The US office is closed til Monday so I may not hear anything until next week.

This appears to be tied into the menu's and screens looking funny. This device threw a code 64 and rebooted to the odd state.

Both units have been in service for a year now.  It's pretty cold and not like in a high temp area in the home.

2017/11/25 13:14:45 system power on.
2017/11/25 13:14:22 system watch-dog reboot.(code 64)
2017/11/25 13:02:53 admin login Ok from 192.168.1.156

[FurryNutz]

I would check the power supplies on both...under load...

[briihrke]

Hi,

I have seen this code 64 reboot twice now. Is there any more information about this event yet?

2018/01/10  17:35:06  system set to new time 2018/01/10 17:34:54.
2018/01/10  17:35:03  usb2 mounted successfully.
2018/01/10  17:34:56  usb1 mounted successfully.
2018/01/10  17:34:51  network set to static IP 192.168.1.75
2018/01/10  17:34:48  system power on.
2018/01/10  17:34:27  system watch-dog reboot.(code 64)
2018/01/05  07:58:53  system set to new time 2018/01/05 07:58:22.

2017/12/22  08:00:02  admin login Ok from 192.168.1.28
2017/12/22  07:18:56  system set to new time 2017/12/22 07:18:44.
2017/12/22  07:18:54  usb2 mounted successfully.
2017/12/22  07:18:46  usb1 mounted successfully.
2017/12/22  07:18:41  network set to static IP 192.168.1.75
2017/12/22  07:18:38  system power on.
2017/12/22  07:18:17  system watch-dog reboot.(code 64)
2017/12/16  15:08:47  usb2 mounted successfully.

Thanks

[FurryNutz]

Link>Welcome!

• What Hardware version is your DNR? Look at the sticker behind or under the device.
• Link>What Firmware version is currently loaded? Found on the DNRs web page under status.
• What region are you located?

What Mfr and model is the main host router?

Hi,

I have seen this code 64 reboot twice now. Is there any more information about this event yet?

2018/01/10  17:35:06  system set to new time 2018/01/10 17:34:54.
2018/01/10  17:35:03  usb2 mounted successfully.
2018/01/10  17:34:56  usb1 mounted successfully.
2018/01/10  17:34:51  network set to static IP 192.168.1.75
2018/01/10  17:34:48  system power on.
2018/01/10  17:34:27  system watch-dog reboot.(code 64)
2018/01/05  07:58:53  system set to new time 2018/01/05 07:58:22.

2017/12/22  08:00:02  admin login Ok from 192.168.1.28
2017/12/22  07:18:56  system set to new time 2017/12/22 07:18:44.
2017/12/22  07:18:54  usb2 mounted successfully.
2017/12/22  07:18:46  usb1 mounted successfully.
2017/12/22  07:18:41  network set to static IP 192.168.1.75
2017/12/22  07:18:38  system power on.
2017/12/22  07:18:17  system watch-dog reboot.(code 64)
2017/12/16  15:08:47  usb2 mounted successfully.

Thanks

[GreenBay42]

I've sent many emails about this but havent heard back. I will send it again.

[FurryNutz]

We find that phone contact has better immediate results over using email.   

I've sent many emails about this but havent heard back. I will send it again.

[GreenBay42]

LOL yes it does 

[RYAT3]

Hi,

I have seen this code 64 reboot twice now. Is there any more information about this event yet?

2018/01/10  17:35:06  system set to new time 2018/01/10 17:34:54.
2018/01/10  17:35:03  usb2 mounted successfully.
2018/01/10  17:34:56  usb1 mounted successfully.
2018/01/10  17:34:51  network set to static IP 192.168.1.75
2018/01/10  17:34:48  system power on.
2018/01/10  17:34:27  system watch-dog reboot.(code 64)
2018/01/05  07:58:53  system set to new time 2018/01/05 07:58:22.

2017/12/22  08:00:02  admin login Ok from 192.168.1.28
2017/12/22  07:18:56  system set to new time 2017/12/22 07:18:44.
2017/12/22  07:18:54  usb2 mounted successfully.
2017/12/22  07:18:46  usb1 mounted successfully.
2017/12/22  07:18:41  network set to static IP 192.168.1.75
2017/12/22  07:18:38  system power on.
2017/12/22  07:18:17  system watch-dog reboot.(code 64)
2017/12/16  15:08:47  usb2 mounted successfully.

Thanks

Are your menus also going bad?