GT-AC5300系统排程不正常

xieyi8610

系统重启设置的周一 周五凌晨3点…然而没有重启…刚截图系统运行时间3天，按理说今天凌晨应该重启的  

特来求助涵哥 以及管理员 谢谢

微信扫一扫，阅读更方便^_^

xieyi8610

上1个版本 固件 也是重启排程问题······

wjs6978

served for bad PEB handling: 4
Feb 14 08:00:27 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1109
Feb 14 08:00:28 pppd[1071]: PAP authentication succeeded
Feb 14 08:00:28 pppd[1071]: peer from calling number 18E7:7D:89:95 authorized
Feb 14 08:00:28 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Feb 14 08:00:28 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Feb 14 08:00:28 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Feb 14 08:00:28 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Feb 14 08:00:28 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2DB61C3C-2DA5-4BBF-828C-942CAEF02C51, small LPT model
Feb 14 08:00:28 pppd[1071]: local  IP address 122.142.98.211
Feb 14 08:00:28 pppd[1071]: remote IP address 122.142.96.1
Feb 14 08:00:28 pppd[1071]: primary   DNS address 202.98.5.68
Feb 14 08:00:28 pppd[1071]: secondary DNS address 202.98.0.68
Feb 14 00:00:28 rc_service: ip-up 1158:notify_rc start_firewall
Feb 14 08:00:28 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Feb 14 00:00:28 wan: finish adding multi routes
Feb 14 08:00:28 kernel: ubi1: detaching mtd9
Feb 14 08:00:28 kernel: ubi1: mtd9 is detached
Feb 14 08:00:28 rc_service: ip-up 1158:notify_rc stop_upnp
Feb 14 08:00:28 rc_service: waitting "start_firewall" via ip-up ...
Feb 14 08:00:29 kernel: ubi1: attaching mtd9
Feb 14 08:00:29 kernel: ubi1: scanning is finished
Feb 14 08:00:29 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Feb 14 08:00:29 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Feb 14 08:00:29 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Feb 14 08:00:29 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Feb 14 08:00:29 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Feb 14 08:00:29 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Feb 14 08:00:29 kernel: ubi1: max/mean erase counter: 21/11, WL threshold: 4096, image sequence number: 1412173660
Feb 14 08:00:29 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Feb 14 08:00:29 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1240
Feb 14 08:00:30 WAN Connection: WAN was restored.
Feb 14 08:00:30 roamast: eth6: add client [b0:f8:93:1e:01:4c] to monitor list
Feb 14 08:00:31 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Feb 14 08:00:31 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Feb 14 08:00:31 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Feb 14 08:00:31 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Feb 14 08:00:31 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2DB61C3C-2DA5-4BBF-828C-942CAEF02C51, small LPT model
Feb 14 08:00:31 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Feb 14 08:00:31 kernel: ubi1: detaching mtd9
Feb 14 08:00:31 kernel: ubi1: mtd9 is detached
Feb 14 08:00:31 ntp: start NTP update
Apr  9 06:06:20 rc_service: ntp 1220:notify_rc restart_upnp
Apr  9 06:06:20 rc_service: waitting "start_firewall" via ip-up ...
Apr  9 06:06:20 kernel: ubi1: attaching mtd9
Apr  9 06:06:20 kernel: ubi1: scanning is finished
Apr  9 06:06:20 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Apr  9 06:06:20 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Apr  9 06:06:20 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Apr  9 06:06:20 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Apr  9 06:06:20 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Apr  9 06:06:20 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Apr  9 06:06:20 kernel: ubi1: max/mean erase counter: 21/11, WL threshold: 4096, image sequence number: 1412173660
Apr  9 06:06:20 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Apr  9 06:06:20 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1303
Apr  9 06:06:20 BONDING: not linked
Apr  9 06:06:21 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Apr  9 06:06:21 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Apr  9 06:06:21 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Apr  9 06:06:21 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Apr  9 06:06:21 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2DB61C3C-2DA5-4BBF-828C-942CAEF02C51, small LPT model
Apr  9 06:06:21 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Apr  9 06:06:21 kernel: ubi1: detaching mtd9
Apr  9 06:06:21 kernel: ubi1: mtd9 is detached
Apr  9 06:06:24 roamast: eth6: add client [c8:93:46:b1:33:6f] to monitor list
Apr  9 06:06:24 modprobe: module scsi_wait_scan not found in modules.dep
Apr  9 06:06:24 kernel: SCSI subsystem initialized
Apr  9 06:06:25 modprobe: module mbcache not found in modules.dep
Apr  9 06:06:25 modprobe: module jbd not found in modules.dep
Apr  9 06:06:25 modprobe: module ext3 not found in modules.dep
Apr  9 06:06:25 modprobe: module ext4 not found in modules.dep
Apr  9 06:06:25 modprobe: module ext2 not found in modules.dep
Apr  9 06:06:25 modprobe: module btusbdrv not found in modules.dep
Apr  9 06:06:25 miniupnpd[958]: shutting down MiniUPnPd
Apr  9 06:06:25 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
Apr  9 06:06:25 miniupnpd[1422]: version 1.9 started
Apr  9 06:06:25 miniupnpd[1422]: HTTP listening on port 43552
Apr  9 06:06:25 miniupnpd[1422]: Listening for NAT-PMP/PCP traffic on port 5351
Apr  9 06:06:25 rc_service: ip-up 1158:notify_rc start_upnp
Apr  9 06:06:25 rc_service: waitting "stop_upnp" via ip-up ...
Apr  9 06:06:25 miniupnpd[1422]: shutting down MiniUPnPd
Apr  9 06:06:26 miniupnpd[1425]: version 1.9 started
Apr  9 06:06:26 miniupnpd[1425]: HTTP listening on port 46291
Apr  9 06:06:26 miniupnpd[1425]: Listening for NAT-PMP/PCP traffic on port 5351
Apr  9 06:06:26 miniupnpd[1427]: MiniUPnPd is already running. EXITING
Apr  9 06:06:27 rc_service: ntp 1220:notify_rc restart_diskmon
Apr  9 06:06:27 disk_monitor: Finish
Apr  9 06:06:27 disk monitor: be idle
Apr  9 06:06:29 kernel: SHN Release Version: 2.0.1 3529123_patch
Apr  9 06:06:29 kernel: UDB Core Version: 0.2.14 r3529123
Apr  9 06:06:29 kernel: sizeof forward pkt param = 280
Apr  9 06:06:33 rc_service: zcip 1804:notify_rc start_firewall
Apr  9 06:06:33 miniupnpd[1425]: shutting down MiniUPnPd
Apr  9 06:06:33 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
Apr  9 06:06:33 miniupnpd[1869]: version 1.9 started
Apr  9 06:06:33 miniupnpd[1869]: HTTP listening on port 40106
Apr  9 06:06:33 miniupnpd[1869]: Listening for NAT-PMP/PCP traffic on port 5351
Apr  9 06:06:33 rc_service: ip-up 1158:notify_rc start_firewall
Apr  9 06:06:33 miniupnpd[1869]: shutting down MiniUPnPd
Apr  9 06:06:33 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
Apr  9 06:06:33 miniupnpd[2007]: version 1.9 started
Apr  9 06:06:33 miniupnpd[2007]: HTTP listening on port 48327
Apr  9 06:06:33 miniupnpd[2007]: Listening for NAT-PMP/PCP traffic on port 5351
Apr  9 06:06:34 roamast: eth6: add client [fc:3f:7c:83:4e:a0] to monitor list
Apr  9 06:06:34 zcip client: configured 169.254.106.156
Apr  9 06:06:40 kernel: ubi1: attaching mtd9
Apr  9 06:06:40 kernel: ubi1: scanning is finished
Apr  9 06:06:40 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Apr  9 06:06:40 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Apr  9 06:06:40 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Apr  9 06:06:40 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Apr  9 06:06:40 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Apr  9 06:06:40 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Apr  9 06:06:40 kernel: ubi1: max/mean erase counter: 21/11, WL threshold: 4096, image sequence number: 1412173660
Apr  9 06:06:40 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Apr  9 06:06:40 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2482
Apr  9 06:06:42 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Apr  9 06:06:42 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Apr  9 06:06:42 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Apr  9 06:06:42 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Apr  9 06:06:42 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 2DB61C3C-2DA5-4BBF-828C-942CAEF02C51, small LPT model
Apr  9 06:06:42 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Apr  9 06:06:42 kernel: ubi1: detaching mtd9
Apr  9 06:06:42 kernel: ubi1: mtd9 is detached
Apr  9 06:06:48 crond[871]: time disparity of 603246 minutes detected
Apr  9 06:06:59 roamast: eth6: add client [54:19:c8:05:95:80] to monitor list
Apr  9 06:07:04 roamast: eth7: add client [28:c6:3f:a8:f7:14] to monitor list
Apr  9 06:07:45 rc_service: rc 3134:notify_rc restart_wrs
Apr  9 06:18:21 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
Apr  9 06:18:23 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex
Apr  9 06:18:25 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
Apr  9 06:18:26 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Apr  9 06:18:27 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex
Apr  9 06:18:29 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Apr  9 06:18:30 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Apr  9 06:18:33 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Apr  9 06:18:36 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
Apr  9 06:18:36 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Apr  9 06:18:38 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex
Apr  9 06:18:38 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Apr  9 06:52:09 roamast: eth6: add client [48:bf:6b:74:32:47] to monitor list
Apr  9 07:38:54 roamast: eth7: add client [cc:2d:83:3e:64:2c] to monitor list
Apr  9 07:54:29 roamast: eth6: add client [f4:9f:f3:53:00:28] to monitor list
Apr  9 08:39:54 roamast: eth6: add client [5c:a8:6a:7e:a3:1b] to monitor list
Apr  9 08:49:33 miniupnpd[2007]: PCP MAP: added mapping UDP 5353->192.168.1.123:5353 'PCP MAP f8364ce4b4fa886cd44e8fb1'
Apr  9 11:06:29 roamast: eth6: add client [44:04:44:16:a4:42] to monitor list
Apr  9 12:29:29 roamast: eth6: add client [04:56:04:84:15:a2] to monitor list
Apr  9 13:31:06 miniupnpd[2007]: PCP MAP: added mapping UDP 5353->192.168.1.123:5353 'PCP MAP c10abaa75d61395812a8bad8'
Apr  9 15:15:05 miniupnpd[2007]: PCP MAP: added mapping UDP 5353->192.168.1.123:5353 'PCP MAP ed6b7ad1cc7252e2801c5512'
Apr  9 16:14:04 roamast: eth6: add client [04:f1:28:5e:0b:58] to monitor list
Apr  9 16:42:25 miniupnpd[2007]: PCP MAP: added mapping UDP 5353->192.168.1.123:5353 'PCP MAP ed6b7ad1cc7252e2801c5512'
Apr  9 17:47:29 roamast: eth6: add client [54:19:c8:05:95:80] to monitor list
Apr  9 18:06:24 ntp: start NTP update
Apr  9 18:13:08 roamast: eth6: add client [4c:49:e3:be:d5:ed] to monitor list
Apr  9 18:47:18 roamast: eth6: add client [fc:3f:7c:83:4e:a0] to monitor list
Apr  9 19:55:31 miniupnpd[2007]: PCP MAP: added mapping UDP 5353->192.168.1.123:5353 'PCP MAP f6f83a1d4006e3b7049d6ca7'
Apr  9 20:08:28 roamast: eth6: add client [c0:9f:05:49:ee:f1] to monitor list
Apr  9 20:08:53 roamast: eth6: add client [c0:9f:05:49:ee:f1] to monitor list
Apr  9 20:46:03 roamast: eth7: add client [60:6b:ff:2b:77:ba] to monitor list
Apr  9 21:22:38 roamast: eth7: add client [60:6b:ff:2b:77:ba] to monitor list
Apr  9 22:25:58 miniupnpd[2007]: PCP MAP: added mapping UDP 5353->192.168.1.123:5353 'PCP MAP 3080170b45e3789c34dc8a94'
Apr  9 22:55:13 roamast: eth7: add client [60:6b:ff:2b:77:ba] to monitor list
Apr  9 23:06:27 disk_monitor: Got SIGALRM...
Apr  9 23:52:33 roamast: eth7: add client [60:6b:ff:2b:77:ba] to monitor list
Apr 10 01:56:48 roamast: eth7: add client [60:6b:ff:2b:77:ba] to monitor list
Apr 10 04:29:43 roamast: eth7: add client [28:c6:3f:a8:f7:14] to monitor list
Apr 10 04:43:09 kernel: klogd started: BusyBox v1.24.1 (2018-03-26 11:38:38 CST)
Apr 10 04:43:09 miniupnpd[2007]: shutting down MiniUPnPd
Apr 10 04:43:09 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
Apr 10 04:43:09 miniupnpd[11560]: version 1.9 started
Apr 10 04:43:09 miniupnpd[11560]: HTTP listening on port 49236
Apr 10 04:43:09 miniupnpd[11560]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 10 04:43:09 miniupnpd[11560]: shutting down MiniUPnPd
Apr 10 04:43:09 hour monitor: daemon is starting
Apr 10 04:43:09 hour monitor: daemon terminates
Apr 10 04:43:09 miniupnpd[11563]: version 1.9 started
Apr 10 04:43:09 miniupnpd[11563]: HTTP listening on port 40082
Apr 10 04:43:09 miniupnpd[11563]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 10 05:07:23 roamast: eth6: add client [fc:3f:7c:83:4e:a0] to monitor list
Apr 10 05:18:38 roamast: eth6: add client [f4:b7:b3:40:10:2e] to monitor list
Apr 10 05:23:03 roamast: eth7: add client [28:c6:3f:a8:f7:14] to monitor list
Apr 10 05:33:58 roamast: eth6: add client [c8:93:46:b1:33:6f] to monitor list
Apr 10 05:58:13 roamast: eth7: add client [28:c6:3f:a8:f7:14] to monitor list
我刷最新固件，QOS设置可以保存，不知道别的怎么样？

涵哥

我这边会帮你看看的
有结果告诉你

xieyi8610

涵哥 发表于 2018-4-10 08:39
我这边会帮你看看的
有结果告诉你

那个贴系统日志的不是我…

maple_1994

xieyi8610 发表于 2018-4-10 09:48
那个贴系统日志的不是我…

被人截胡

涵哥

xieyi8610 发表于 2018-4-10 09:48
那个贴系统日志的不是我…

我用相同的固件版本确认，没有发现问题。之后会放置在那边，长期观察看看
如果方便的话，可以把设定档提供给我，我这边再确认看看

xieyi8610

涵哥 发表于 2018-4-10 13:54
我用相同的固件版本确认，没有发现问题。之后会放置在那边，长期观察看看
如果方便的话，可以把设定档提 ...

具体是这个情况，设置两个重启时间点，比如周三和周日，保存之后周三的可以正常重启，但是周日的就不会重启了，上一个版本如此，这一个版本也是如此，都是第二个时间点没有重启成功，再次感谢涵哥

xieyi8610

排程依旧不正常…重启第一个时间后，第二个时间点就不会重启了