The standard syslog-ng output is this:Hi, can anyone post a snippet of one of their logs that goes through scribe? I modded the message format ages back and don't remember how it used to look...I have ideas for a uiScribe update
Jun 12 15:42:01 RT-AC86U spdMerlin: Starting speedtest using using auto-selected server for WAN interface
Jun 12 15:42:29 RT-AC86U spdMerlin: Speedtest results - Download: 200.41 Mbps (data used: 366.0 MB) - Upload: 36.54 Mbps (data used: 29.2 MB)
Jun 12 15:42:29 RT-AC86U spdMerlin: Connection quality - Latency: 14.14 ms (0.53 ms jitter) - Packet Loss: 0.0%
destination messages {
file("/opt/var/log/messages" template("${R_DATE} ${HOST} ${MSGHDR}${MESSAGE}\n") );
};
Jun 11 22:00:01 RT-AC86U uiDivStats: Starting stat update
Jun 11 22:00:28 RT-AC86U uiDivStats: Stats updated successfully
Jun 11 23:00:01 RT-AC86U uiDivStats: Starting stat update
Jun 11 23:00:30 RT-AC86U uiDivStats: Stats updated successfully
Jun 11 23:59:03 RT-AC86U dn-vnstat: Attempting to send summary statistic email
Jun 11 23:59:05 RT-AC86U dn-vnstat: Email sent successfully
May 5 01:05:09 syslogd started: BusyBox v1.25.1
May 5 01:05:09 kernel: klogd started: BusyBox v1.25.1 (2021-05-19 23:12:52 EDT)
May 5 01:05:09 kernel: Booting Linux on physical CPU 0x0
May 5 01:05:09 kernel: Linux version 4.1.27 (merlin@ubuntu-dev) (gcc version 5.3.0 (Buildroot 2016.02) ) #2 SMP PREEMPT Wed May 19 23:52:54 EDT 2021
May 5 01:05:09 kernel: CPU: AArch64 Processor [420f1000] revision 0
May 5 01:05:09 kernel: Detected VIPT I-cache on CPU0
May 5 01:05:09 kernel: alternatives: enabling workaround for ARM erratum 845719
Jun 12 17:13:37 RT-AC86U debug networkmap: Error unlocking 0: 9 Bad file descriptor
Jun 12 17:13:42 RT-AC86U warning YazFi: YazFi v4.2.1 completed successfully
Jun 12 17:16:34 RT-AC86U warning YazFi: Downloading latest version (v4.2.1) of YazFi
Jun 12 17:16:36 RT-AC86U warning YazFi: YazFi successfully updated - restarting firewall to apply update
Jun 12 17:16:36 RT-AC86U notice rc_service: service 32272:notify_rc restart_firewall
Jun 7 12:18:10 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(534): eth6: Assoc B2:C2:E1:BA:CF:D0, status: Successful (0)
Jun 7 12:18:31 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(486): eth6: Disassoc B2:C2:E1:BA:CF:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 7 12:18:31 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(486): eth6: Disassoc B2:C2:E1:BA:CF:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 7 12:18:52 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(505): eth6: Auth B2:C2:E1:BA:CF:D0, status: Successful (0)
Jun 7 12:18:52 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(534): eth6: Assoc B2:C2:E1:BA:CF:D0, status: Successful (0)
Jun 7 12:19:11 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(486): eth6: Disassoc B2:C2:E1:BA:CF:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 7 12:19:11 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(486): eth6: Disassoc B2:C2:E1:BA:CF:D0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 7 12:23:15 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(505): eth6: Auth B2:C2:E1:BA:CF:D0, status: Successful (0)
Jun 7 12:23:15 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(534): eth6: Assoc B2:C2:E1:BA:CF:D0, status: Successful (0)
Jun 7 13:12:58 RT-AX88U-26A8 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 5C:41:5A:40:D7:F3, status: 0, reason: Disassociated due to inactivity (4)
Mar 27 23:37:26 RT-AX58U-E058 syslog-ng[2033]: Log statistics; processed='src.internal(src#2)=89', stamp='src.internal(src#2)=1616881046', dropped='global(internal_source)=0', queued='global(internal_source)=0', dropped='dst.udp(log_server#0,udp,192.168.1.1:514)=70', processed='dst.udp(log_server#0,udp,192.168.1.1:514)=12312', queued='dst.udp(log_server#0,udp,192.168.1.1:514)=0', written='dst.udp(log_server#0,udp,192.168.1.1:514)=12242', processed='global(msg_clones)=0', processed='global(payload_reallocs)=5657', processed='destination(d_syslogng)=54', processed='destination(log_server)=12382', processed='global(sdata_updates)=0', processed='destination(messages)=5276', queued='global(scratch_buffers_count)=2', processed='source(s_lr_daily)=0', processed='center(queued)=19505', processed='destination(d_logrotate)=42', processed='source(s_lr_status)=42', processed='center(received)=7148', processed='destination(d_firewall)=0', processed='global(internal_queue_length)=0', processed='destination(d_wlceventd)=1751', processed='source(src)=7106', queued='global(scratch_buffers_bytes)=512'
Mar 27 23:39:01 RT-AX58U-E058 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Mar 27 23:39:01 RT-AX58U-E058 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Mar 27 23:39:01 RT-AX58U-E058 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 68:72:C3:6E:2E:F4, status: 0, reason: Unspecified reason (1)
Mar 27 23:39:01 RT-AX58U-E058 wlceventd: wlceventd_proc_event(505): wl1.1: Auth 68:72:C3:6E:2E:F4, status: Successful (0)
Mar 27 23:39:01 RT-AX58U-E058 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc 68:72:C3:6E:2E:F4, status: Successful (0)
Mar 27 23:39:01 RT-AX58U-E058 hostapd: wl1.1: STA 68:72:c3:6e:2e:f4 IEEE 802.11: associated
Mar 27 23:39:01 RT-AX58U-E058 hostapd: wl1.1: STA 68:72:c3:6e:2e:f4 IEEE 802.11: associated
Mar 27 23:39:01 RT-AX58U-E058 hostapd: wl1.1: STA 68:72:c3:6e:2e:f4 RADIUS: starting accounting session 9190B8A13FC7A2A4
Mar 27 23:39:01 RT-AX58U-E058 hostapd: wl1.1: STA 68:72:c3:6e:2e:f4 RADIUS: starting accounting session 9190B8A13FC7A2A4
Mar 27 23:39:01 RT-AX58U-E058 hostapd: wl1.1: STA 68:72:c3:6e:2e:f4 WPA: pairwise key handshake completed (RSN)
Mar 27 23:39:01 RT-AX58U-E058 hostapd: wl1.1: STA 68:72:c3:6e:2e:f4 WPA: pairwise key handshake completed (RSN)
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!