Skynet No data to display in Skynet Statistics

[dave14305]

Not sure it will work, but you can try

ln -s /jffs/syslog.log /tmp/syslog.log
ln -s /jffs/syslog.log-1 /tmp/syslog.log-1

And see if stats start to accumulate in Skynet.

 

[qy2009]

they are different logs.
When I check /tmp/syslog.log. it's

May  4 05:01:59 syslog: wlceventd_proc_event(527): wl0.1: Auth C4:60:35:16:F1:2D, status: Successful (0), rssi:0
May  4 05:01:59 syslog: wlceventd_proc_event(556): wl0.1: Assoc C4:60:35:16:F1:2D, status: Successful (0), rssi:0
May  4 05:02:00 Diversion: Mounting Diversion WebUI page
May  4 05:02:01 kernel: ip_set: protocol 6
May  4 05:02:02 Diversion: Mounted Diversion WebUI as user1.asp in LAN/Diversion
May  4 05:02:02 syslog: wlceventd_proc_event(491): eth2: Deauth_ind 30:D1:6B:80:63:1D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
May  4 05:02:02 syslog: wlceventd_proc_event(508): eth2: Disassoc 30:D1:6B:80:63:1D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May  4 05:02:03 connmon: Mounting WebUI tab for connmon
May  4 05:02:03 connmon: Mounted connmon WebUI page as user2.asp
May  4 05:02:03 Diversion: restarted Dnsmasq to apply settings
May  4 05:02:04 uiDivStats: dnsmasq has restarted, restarting taildns
May  4 05:02:04 kernel: br1: topology change detected, propagating
May  4 05:02:04 kernel: br1: port 2(eth0.501) entering forwarding state
May  4 05:02:04 custom_script: Running /jffs/scripts/service-event (args: start dnsmasq)
May  4 05:02:05 rc_service: udhcpc 1705:notify_rc stop_samba
May  4 05:02:05 rc_service: waitting "start_dnsmasq" via udhcpc ...
May  4 05:02:05 rc_service: skip the event: restart_nasapps.
May  4 05:02:05 scMerlin: NTP synced, scMerlin will now continue
May  4 05:02:06 custom_config: Appending content of /jffs/configs/hosts.add.
May  4 05:02:06 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
May  4 05:02:07 syslog: wlceventd_proc_event(527): eth2: Auth 30:D1:6B:80:63:1D, status: Successful (0), rssi:0
May  4 05:02:07 syslog: wlceventd_proc_event(556): eth2: Assoc 30:D1:6B:80:63:1D, status: Successful (0), rssi:0
May  4 05:02:08 Diversion: restarted Dnsmasq to apply settings

When I check /jffs/syslog.log, it's

May 21 14:22:37 syslog: wlceventd_proc_event(508): wl0.1: Disassoc 10:52:1C:4F:79:55, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 21 14:22:38 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=xxx SRC=138.99.216.227 DST=xxx LEN=44 TOS=0x00 PREC=0x00 TTL=235 ID=56727 PROTO=TCP SPT=6
May 21 14:22:46 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=xxx SRC=185.156.73.109 DST=xxx LEN=40 TOS=0x00 PREC=0x00 TTL=237 ID=57740 PROTO=TCP SPT=5
May 21 14:23:19 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=xxx SRC=195.133.40.231 DST=xxx LEN=40 TOS=0x00 PREC=0x00 TTL=237 ID=54321 PROTO=TCP SPT=5
May 21 14:23:36 syslog: wlceventd_proc_event(527): wl0.1: Auth 10:52:1C:4F:79:55, status: Successful (0), rssi:0
May 21 14:23:36 syslog: wlceventd_proc_event(556): wl0.1: Assoc 10:52:1C:4F:79:55, status: Successful (0), rssi:0
May 21 14:28:36 syslog: wlceventd_proc_event(527): wl0.1: Auth 10:52:1C:4F:79:55, status: Successful (0), rssi:0
May 21 14:28:36 syslog: wlceventd_proc_event(527): wl0.1: Auth 10:52:1C:4F:79:55, status: Successful (0), rssi:0
May 21 14:28:36 syslog: wlceventd_proc_event(556): wl0.1: Assoc 10:52:1C:4F:79:55, status: Successful (0), rssi:0
May 21 14:28:37 syslog: wlceventd_proc_event(508): wl0.1: Disassoc 10:52:1C:4F:79:55, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 21 14:28:53 syslog: wlceventd_proc_event(508): eth2: Disassoc F6:2B:2F:08:3B:F9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 21 14:28:53 syslog: wlceventd_proc_event(508): eth2: Disassoc F6:2B:2F:08:3B:F9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 21 14:29:17 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=xxx SRC=185.191.34.91 DST=xxx LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=49658 PROTO=TCP SPT=52
May 21 14:29:35 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=xxx SRC=45.227.253.102 DST=xxx LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=35772 PROTO=TCP SPT=5
May 21 14:29:36 syslog: wlceventd_proc_event(527): wl0.1: Auth 10:52:1C:4F:79:55, status: Successful (0), rssi:0
May 21 14:29:36 syslog: wlceventd_proc_event(556): wl0.1: Assoc 10:52:1C:4F:79:55, status: Successful (0), rssi:0
May 21 14:29:39 syslog: wlceventd_proc_event(508): wl0.1: Disassoc 10:52:1C:4F:79:55, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 21 14:29:49 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=xxx SRC=194.26.29.169 DST=xxx LEN=40 TOS=0x00 PREC=0x00 TTL=234 ID=39638 PROTO=TCP SPT=52
May 21 14:30:03 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=xxx SRC=89.248.163.239 DST=xxx LEN=40 TOS=0x00 PREC=0x00 TTL=236 ID=54321 PROTO=TCP SPT=5
May 21 14:30:09 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=xxx SRC=91.240.118.245 DST=xxx LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=64749 PROTO=TCP SPT=4

 

[dave14305]

they are different logs.

I forgot that Skynet supports custom syslog locations. Try to run:

firewall settings syslog /jffs/syslog.log
firewall settings syslog1 /jffs/syslog.log-1

or go through the Skynet Settings menu, option 10.

 

[qy2009]

wow. you are genius. it worked after I typed those two commands

thanks so much @dave14305

 

[null_]

Just wanted to add that I also needed to run dave14305's steps above (post #23) in order to get logging to work on my GT-AX6000 (menu option 10 didn't work; had to run the SSH commands). No weird configs, running Diversion + Skynet, never got log data to show until now. Thanks!

 

[Adamm]

I just caught wind of this, is this new syslog location universal or distinguishable via some method @dave14305 @RMerlin

 

[dave14305]

I just caught wind of this, is this new syslog location universal or distinguishable via some method @dave14305 @RMerlin

You could check the parameters of the running syslogd daemon in ps.

/sbin/syslogd -m 0 -S -O /jffs/syslog.log -s 256 -l 7

/sbin/syslogd -m 0 -S -O /tmp/syslog.log -s 256 -l 7

 

[RMerlin]

I just caught wind of this, is this new syslog location universal or distinguishable via some method @dave14305 @RMerlin

No idea when that was changed. There is now a libshared function that returns the path to the syslog, and it gets used by rc when starting syslogd.

 

[dave14305]

No idea when that was changed. There is now a libshared function that returns the path to the syslog, and it gets used by rc when starting syslogd.

It came with HND 5.04 with PSISTLOG=y in target.mak.

 

[RMerlin]

It came with HND 5.04 with PSISTLOG=y in target.mak.

PSISTLOG has been there for years, it's what made the log get copied to /jffs/ in the past.

 

[dave14305]

PSISTLOG has been there for years, it's what made the log get copied to /jffs/ in the past.

It is only set to y in HND-94912_BASE, however. Defaults to n everywhere else, if I understand it correctly,

I believe RTCONFIG_JFFS2LOG controls the syslog copying to /jffs.

 

[RMerlin]

It is only set to y in HND-94912_BASE, however. Defaults to n everywhere else, if I understand it correctly,

I believe RTCONFIG_JFFS2LOG controls the syslog copying to /jffs.

I might have confused the two settings indeed. The PSISTLOG setting itself still isn't new, it has existed for over 5 years in the list of available config options (2017 is when the NG repo was created, so the setting is even older than that):

2e104e83cd1 (Eric Sauvageau      2017-08-27 01:27:50 -0400 1305) config RTCONFIG_PSISTLOG
2e104e83cd1 (Eric Sauvageau      2017-08-27 01:27:50 -0400 1306)        bool "Persistent syslog"
2e104e83cd1 (Eric Sauvageau      2017-08-27 01:27:50 -0400 1307)        default n

So it's possible it was unused until now by any of the supported models.

 

[Ouss23]

Not sure it will work, but you can try

ln -s /jffs/syslog.log /tmp/syslog.log
ln -s /jffs/syslog.log-1 /tmp/syslog.log-1

And see if stats start to accumulate in Skynet.

I had the same problem for several days without finding a solution. I uninstalled and reinstalled Skynet without it solving the problem until I found this discussion. Thank you @dave14305 it works great for me.