n18u 升級韌體後系統記錄有問題
型號: RT-N18U
Firmware: 3.0.0.4.382_51640-g679a7e3
系統版本:
序號:
本帖最後由 hoshugon 於 2019/11/3 11:22 編輯 昨天更新最新版後就變成這樣，重開後還是一樣，要如何解決~~~
Firmware: 3.0.0.4.382_51640-g679a7e3
系統版本:
序號:
本帖最後由 hoshugon 於 2019/11/3 11:22 編輯 昨天更新最新版後就變成這樣，重開後還是一樣，要如何解決~~~
May 5 13:05:05 acsd: selected channel spec: 0x1003 (3) May 5 13:05:05 acsd: Adjusted channel spec: 0x1003 (3) May 5 13:05:05 acsd: selected DFS-exit channel spec: 0x1003 (3) May 5 13:05:05 acsd: selected channel spec: 0x1003 (3) May 5 13:05:05 acsd: Adjusted channel spec: 0x1003 (3) May 5 13:05:05 acsd: selected channel spec: 0x1003 (3) May 5 13:05:05 acsd: acs_set_chspec: 0x1003 (3) for reason APCS_INIT May 5 13:05:05 RT-N18U: start httpd:80 May 5 13:05:06 NAT Tunnel: AAE Service is stopped May 5 13:05:06 disk monitor: be idle May 5 13:05:06 AAE: AAE Service is started May 5 13:05:06 jffs2: valid logs(1) May 5 13:05:06 hour monitor: daemon is starting May 5 13:05:06 hour monitor: daemon terminates May 5 13:05:07 miniupnpd[238]: version 1.9 started May 5 13:05:07 miniupnpd[238]: HTTP listening on port 55981 May 5 13:05:07 miniupnpd[238]: Listening for NAT-PMP/PCP traffic on port 5351 May 5 13:05:07 WAN Connection: Fail to connect with some issues. May 5 13:05:07 syslog: Generating SSL certificate... May 5 13:05:07 syslog: module ax88179_178a not found in modules.dep May 5 13:05:08 pppd[271]: pppd 2.4.7 started by hoshugon, uid 0 May 5 13:05:08 pppoe-relay[264]: PADO packet from 00:30:88:1e:0c:ff on interface eth0 does not have Relay-Session-Id tag May 5 13:05:08 pppd[271]: Connected to 00:30:88:1e:0c:ff via interface eth0 May 5 13:05:08 pppd[271]: Connect: ppp0 <--> eth0 May 5 13:05:08 pppoe-relay[264]: PADS packet from 00:30:88:1e:0c:ff on interface eth0 does not have Relay-Session-Id tag May 5 13:05:08 pppd[271]: PAP authentication succeeded May 5 13:05:08 pppd[271]: peer from calling number 00:30:88:1E:0C:FF authorized May 5 13:05:08 pppd[271]: local IP address 1.164.69.48 May 5 13:05:08 pppd[271]: remote IP address 168.95.98.254 May 5 13:05:08 rc_service: ip-up 284:notify_rc start_firewall May 5 13:05:08 pppoe-relay[264]: Discovery packet on eth0 with unknown code 211 May 5 13:05:08 Mastiff: init May 5 13:05:08 wan: finish adding multi routes May 5 13:05:09 rc_service: ip-up 284:notify_rc stop_upnp May 5 13:05:09 rc_service: waitting "start_firewall" via ip-up ... May 5 13:05:09 syslog: module ledtrig-usbdev not found in modules.dep May 5 13:05:09 syslog: module leds-usb not found in modules.dep May 5 13:05:09 wan: finish adding multi routes May 5 13:05:09 kernel: SCSI subsystem initialized May 5 13:05:11 kernel: jnl: driver (lke_9.2.0, May 27 2019 10:52:22, LBD=ON) loaded at bf649000 May 5 13:05:12 kernel: ufsd:: trace mask set to 0000000f May 5 13:05:12 kernel: ufsd: driver (lke_9.2.0 lke_9.2.0_r248656_b5, build_host("asuswrt-build-server"), acl, ioctl, bdi, sd2(0), wb, bz, tr, rsrc) loaded at bf656000 May 5 13:05:12 kernel: NTFS support included May 5 13:05:12 kernel: Hfs+/HfsJ support included May 5 13:05:12 kernel: optimized: speed May 5 13:05:12 kernel: Build_for__ASUS_PRODUCTS_003_k2.6.36_2013-11-07_lke_9.2.0_r248656_b5 May 5 13:05:13 WAN Connection: WAN was restored. May 5 13:05:13 miniupnpd[238]: shutting down MiniUPnPd May 5 13:05:13 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0) May 5 13:05:14 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0) May 5 13:05:15 ntp: start NTP update Nov 2 23:00:23 kernel: nf_conntrack_rtsp v0.6.21 loading Nov 2 23:00:23 kernel: nf_nat_rtsp v0.6.21 loading Nov 2 23:00:23 rc_service: ntp 330:notify_rc restart_diskmon Nov 2 23:00:23 rc_service: waitting "start_firewall" via ip-up ... Nov 2 23:00:23 miniupnpd[457]: version 1.9 started Nov 2 23:00:23 miniupnpd[457]: HTTP listening on port 33891 Nov 2 23:00:23 miniupnpd[457]: Listening for NAT-PMP/PCP traffic on port 5351 Nov 2 23:00:24 disk_monitor: Finish Nov 2 23:00:25 rc_service: ip-up 284:notify_rc start_upnp Nov 2 23:00:25 rc_service: waitting "stop_upnp" via ip-up ... Nov 2 23:00:25 miniupnpd[457]: shutting down MiniUPnPd Nov 2 23:00:27 miniupnpd[464]: version 1.9 started Nov 2 23:00:27 miniupnpd[464]: HTTP listening on port 44901 Nov 2 23:00:27 miniupnpd[464]: Listening for NAT-PMP/PCP traffic on port 5351 Nov 2 23:00:28 rc_service: zcip 462:notify_rc start_firewall Nov 2 23:00:28 zcip client: configured 169.254.204.217 Nov 2 23:00:29 miniupnpd[464]: shutting down MiniUPnPd Nov 2 23:00:29 disk monitor: be idle Nov 2 23:00:30 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0) Nov 2 23:00:31 miniupnpd[502]: version 1.9 started Nov 2 23:00:31 miniupnpd[502]: HTTP listening on port 55251 Nov 2 23:00:31 miniupnpd[502]: Listening for NAT-PMP/PCP traffic on port 5351 Nov 2 23:01:09 crond[196]: time disparity of 786836 minutes detected Nov 2 23:15:14 acsd: scan in progress ... Nov 2 23:15:14 acsd: scan in progress ... Nov 2 23:15:14 acsd: scan in progress ... Nov 2 23:15:15 acsd: scan in progress ... Nov 2 23:15:15 acsd: scan in progress ... Nov 2 23:15:15 acsd: scan in progress ... Nov 2 23:15:15 acsd: scan in progress ... Nov 2 23:15:16 acsd: scan in progress ... Nov 2 23:15:16 acsd: scan in progress ... Nov 2 23:15:16 acsd: scan in progress ... Nov 2 23:15:17 acsd: selected channel spec: 0x1003 (3) Nov 2 23:15:17 acsd: Adjusted channel spec: 0x1003 (3) Nov 2 23:15:17 acsd: selected channel spec: 0x1003 (3) Nov 2 23:15:17 acsd: acs_set_chspec: 0x1003 (3) for reason APCS_CSTIMER Nov 2 23:30:18 acsd: scan in progress ... Nov 2 23:30:18 acsd: scan in progress ... Nov 2 23:30:18 acsd: scan in progress ... Nov 2 23:30:19 acsd: scan in progress ... Nov 2 23:30:19 acsd: scan in progress ... Nov 2 23:30:19 acsd: scan in progress ... Nov 2 23:30:19 acsd: scan in progress ... Nov 2 23:30:20 acsd: scan in progress ... Nov 2 23:30:20 acsd: scan in progress ... Nov 2 23:30:20 acsd: scan in progress ... Nov 2 23:30:20 acsd: scan in progress ... Nov 2 23:30:21 acsd: selected channel spec: 0x100a (10) Nov 2 23:30:21 acsd: Adjusted channel spec: 0x100a (10) Nov 2 23:30:21 acsd: selected channel spec: 0x100a (10) Nov 2 23:30:21 acsd: acs_set_chspec: 0x100a (10) for reason APCS_CSTIMER Nov 2 23:45:22 acsd: scan in progress ... Nov 2 23:45:22 acsd: scan in progress ... Nov 2 23:45:22 acsd: scan in progress ... Nov 2 23:45:23 acsd: scan in progress ... Nov 2 23:45:23 acsd: scan in progress ... Nov 2 23:45:23 acsd: scan in progress ... Nov 2 23:45:23 acsd: scan in progress ... Nov 2 23:45:24 acsd: scan in progress ... Nov 2 23:45:24 acsd: scan in progress ... Nov 2 23:45:24 acsd: scan in progress ... Nov 2 23:45:24 acsd: scan in progress ... Nov 2 23:45:25 acsd: selected channel spec: 0x100a (10) Nov 2 23:45:25 acsd: Adjusted channel spec: 0x100a (10) Nov 2 23:45:25 acsd: selected channel spec: 0x100a (10) Nov 2 23:45:25 acsd: acs_set_chspec: 0x100a (10) for reason APCS_CSTIMER Nov 3 00:00:26 acsd: scan in progress ... Nov 3 00:00:26 acsd: scan in progress ... Nov 3 00:00:26 acsd: scan in progress ... Nov 3 00:00:27 acsd: scan in progress ... Nov 3 00:00:27 acsd: scan in progress ... Nov 3 00:00:27 acsd: scan in progress ...下面就一直重覆...
5則回覆 5
hoshugon 發表於 2019/11/4 16:30 使用上功能還算正常，但這記錄這樣是不是哪出問題?hoshugon 您好 不知道您覺得異常是指紀錄檔顯示時間為5/5嗎？ 路由器內皆無RTC電路，故無法保留最後同步時間。 每當路由器斷電重開，就會先以系統預設時間(可能變動)先紀錄本次開機log. 待開機完成RTC同步時間後才會逐步恢復目前時間載入，此為正常情形。 如您指的是韌體更新後持續掃port的部分，建議您參考以下進行Hard Factory Reset，並手動重開機一次： https://www.asus.com/tw/support/FAQ/1039077/ 如使用上有其他狀況，再麻煩提供給小編。 謝謝。
好像是WIFI頻道設成自動時系統在掃描最佳頻道的紀錄
https://www.snbforums.com/threads/asus-rt-ac68-offered-3-0-0-4-384_45708.55814/page-2#post-476010
Those messages indicate that the acsd daemon is looking for the best channel to use. They are not error messages, just debugging messages showing up if you set channels to Auto.
