CaptnDanLKW
Senior Member
Since 386.2_2 things have been stable with my setup since a fresh install with the latest. I've ignored my router for 4-5 days, I went in this morning just to scan the logs and see if any issues were logged.
Logging Stopped 5 days ago. So frustrating.
I was away on Saturday, we had a number of power outages but my equipment is on battery backup, nothing rebooted. I suspect the ISP equipment at the street also went down since the logs show eth0 bounce a number of times, probably when the Arris Cable modem ran its internal reconnect routines causing the ethernet link to bounce, as indicated by the logs.
ps shows this:
so I guess syslog-ng died but the scribe script shows the daemon is still alive
And after running 's' status
And logging started again
TL;DR - Logging died for no reason, looks like syslog-ng failed. Simply checking its status 'fixed' it.
Any ideas?
Logging Stopped 5 days ago. So frustrating.
I was away on Saturday, we had a number of power outages but my equipment is on battery backup, nothing rebooted. I suspect the ISP equipment at the street also went down since the logs show eth0 bounce a number of times, probably when the Arris Cable modem ran its internal reconnect routines causing the ethernet link to bounce, as indicated by the logs.
Code:
Apr 24 13:53:16 RTAC86U kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Apr 24 13:53:25 RTAC86U kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
Apr 24 13:53:29 RTAC86U kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Apr 24 13:53:37 RTAC86U DualWAN: skip single wan wan_led_control - WANRED off
Apr 24 13:53:42 RTAC86U WAN_Connection: WAN(0) link down.
Apr 24 13:53:48 RTAC86U kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
Apr 24 13:53:52 RTAC86U WAN_Connection: WAN(0) link up.
Apr 24 13:53:52 RTAC86U rc_service: wanduck 1054:notify_rc restart_wan_if 0
Apr 24 13:53:52 RTAC86U custom_script: Running /jffs/scripts/service-event (args: restart wan_if)
Apr 24 13:53:52 RTAC86U wsdd2[10693]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Apr 24 13:53:53 RTAC86U wsdd2[10693]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Apr 24 13:53:53 RTAC86U wan: finish adding multi routes
Apr 24 13:53:54 RTAC86U start_ddns: update WWW.ASUS.COM update@asus.com, wan_unit 0
Apr 24 13:53:54 RTAC86U inadyn[14171]: In-a-dyn version 2.8.1 -- Dynamic DNS update client.
Apr 24 13:53:59 RTAC86U BWDPI: fun bitmap = 47f
Apr 24 13:54:00 RTAC86U wsdd2[10693]: Terminated received.
Apr 24 13:54:00 RTAC86U wsdd2[10693]: terminating.
Apr 24 13:54:01 RTAC86U Samba_Server: smb daemon is stopped
Apr 24 13:54:01 RTAC86U Samba_Server: daemon is started
Apr 24 13:54:01 RTAC86U wsdd2[14394]: starting.
Apr 24 13:54:33 RTAC86U sd-idle-2.6[1692]: spinning down /dev/sdb after 30 mins 31 secs
Apr 24 13:54:50 RTAC86U WAN_Connection: WAN was restored.
Apr 24 13:54:50 RTAC86U rc_service: wanduck 1054:notify_rc stop_ntpd
Apr 24 13:54:50 RTAC86U rc_service: wanduck 1054:notify_rc start_ntpd
Apr 24 13:54:50 RTAC86U rc_service: waitting "stop_ntpd" via wanduck ...
Apr 24 13:54:50 RTAC86U custom_script: Running /jffs/scripts/service-event (args: stop ntpd)
Apr 24 13:54:50 RTAC86U ntpd: Stopped ntpd
Apr 24 13:54:51 RTAC86U custom_script: Running /jffs/scripts/service-event (args: start ntpd)
Apr 24 13:54:51 RTAC86U ntpd: Started ntpd
Apr 24 13:56:22 RTAC86U kernel: nf_conntrack: expectation table full
Apr 24 13:56:27 RTAC86U kernel: net_ratelimit: 20 callbacks suppressed
Apr 24 13:56:27 RTAC86U kernel: nf_conntrack: expectation table full
Apr 24 13:56:28 RTAC86U kernel: nf_conntrack: expectation table full
Apr 24 23:59:02 RTAC86U dn-vnstat: dn-vnstat relies on Diversion to send email summaries, and Diversion is not installed
Apr 24 23:59:02 RTAC86U dn-vnstat: Diversion can be installed using amtm
ps shows this:
so I guess syslog-ng died but the scribe script shows the daemon is still alive
And after running 's' status
And logging started again
Code:
Apr 28 07:44:40 RTAC86U kernel: xxxxxxxxx not mesh client, can't update it's ip
Apr 28 07:44:40 RTAC86U kernel: xxxxxxxxx not mesh client, can't update it's ip
TL;DR - Logging died for no reason, looks like syslog-ng failed. Simply checking its status 'fixed' it.
Any ideas?