`daemon.info events_reporting` appears to fail multiple times according to `logread -f`, maybe in context with WireGuard?

Hello!

The Send test email action under Administration > Recipients > Email Users > Account name is successful, but daemon.info events_reporting appears to fail multiple times according to logread -f, maybe in context with WireGuard?

19006 Tue Feb 25 18:19:08 2025 daemon.err rms_mqtt[10639]: Mosquitto disconnected: Keepalive exceeded
19007 Tue Feb 25 18:19:08 2025 daemon.err rms_mqtt[10639]: Connection timeout (60), retrying
19008 Tue Feb 25 18:19:08 2025 daemon.err rms_mqtt[10639]: Mosquitto reconnecting
19009 Tue Feb 25 18:19:11 2025 daemon.err rms_mqtt[10639]: Mosquitto connected
19010 Tue Feb 25 18:19:27 2025 daemon.notice wpa_supplicant[2143]: wlan0-2: RSN: Group rekeying completed with --:--:--:--:--:-- [GTK=CCMP]
19011 Tue Feb 25 18:20:00 2025 cron.err crond[10564]: USER root pid 9326 cmd /usr/bin/wireguard_watchdog
19012 Tue Feb 25 18:21:00 2025 cron.err crond[10564]: USER root pid 9577 cmd /usr/bin/wireguard_watchdog
19013 Tue Feb 25 18:21:39 2025 daemon.notice hostapd: wlan0-1: AP-STA-DISCONNECTED --:--:--:--:--:--
19014 Tue Feb 25 18:21:39 2025 kern.notice ----------------: WiFi client disconnected: --:--:--:--:--:--
19015 Tue Feb 25 18:21:39 2025 daemon.info hostapd: wlan0-1: STA --:--:--:--:--:-- IEEE 802.1X: unauthorizing port
19016 Tue Feb 25 18:21:39 2025 daemon.info hostapd: wlan0-1: STA --:--:--:--:--:-- IEEE 802.11: disassociated
19017 Tue Feb 25 18:21:40 2025 daemon.info hostapd: wlan0-1: STA --:--:--:--:--:-- IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
19018 Tue Feb 25 18:21:50 2025 daemon.info hostapd: wlan0-1: STA --:--:--:--:--:-- IEEE 802.11: associated (aid 2)
19019 Tue Feb 25 18:21:50 2025 daemon.info hostapd: wlan0-1: STA --:--:--:--:--:-- IEEE 802.1X: unauthorizing port
19020 Tue Feb 25 18:21:51 2025 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED --:--:--:--:--:-- auth_alg=sae
19021 Tue Feb 25 18:21:51 2025 kern.notice ----------------: WiFi client connected: --:--:--:--:--:--
19022 Tue Feb 25 18:21:51 2025 daemon.info hostapd: wlan0-1: STA --:--:--:--:--:-- IEEE 802.1X: authorizing port
19023 Tue Feb 25 18:21:51 2025 daemon.info hostapd: wlan0-1: STA --:--:--:--:--:-- RADIUS: starting accounting session ----------------
19024 Tue Feb 25 18:21:51 2025 daemon.info hostapd: wlan0-1: STA --:--:--:--:--:-- WPA: pairwise key handshake completed (RSN)
19025 Tue Feb 25 18:21:51 2025 daemon.notice hostapd: wlan0-1: EAPOL-4WAY-HS-COMPLETED --:--:--:--:--:--
19026 Tue Feb 25 18:22:00 2025 cron.err crond[10564]: USER root pid 9811 cmd /usr/bin/wireguard_watchdog
19027 Tue Feb 25 18:22:02 2025 daemon.notice wpa_supplicant[2143]: wlan0-2: SME: Trying to authenticate with --:--:--:--:--:-- (SSID='----------------' freq=2412 MHz)
19028 Tue Feb 25 18:22:03 2025 kern.info kernel: [195198.335788] wlan0-2: disconnect from AP --:--:--:--:--:-- for new auth to --:--:--:--:--:--
19029 Tue Feb 25 18:22:03 2025 daemon.notice netifd: Network device 'wlan0-2' link is down
19030 Tue Feb 25 18:22:03 2025 daemon.notice netifd: Interface 'ifWan2' has link connectivity loss
19031 Tue Feb 25 18:22:03 2025 daemon.notice netifd: ifWan2 (577): udhcpc: received SIGTERM
19032 Tue Feb 25 18:22:03 2025 daemon.notice netifd: ifWan2 (577): udhcpc: unicasting a release of 192.168.178.64 to 192.168.178.1
19033 Tue Feb 25 18:22:03 2025 daemon.notice netifd: ifWan2 (577): udhcpc: sending release
19034 Tue Feb 25 18:22:03 2025 daemon.notice netifd: ifWan2 (577): udhcpc: entering released state
19035 Tue Feb 25 18:22:03 2025 daemon.notice netifd: ifWan2 (577): Command failed: Permission denied
19036 Tue Feb 25 18:22:03 2025 daemon.notice netifd: Interface 'ifWan2' is now down
19037 Tue Feb 25 18:22:03 2025 kern.warn kernel: [195198.437183] ath10k_ahb a000000.wifi: peer-unmap-event: unknown peer id 175
19038 Tue Feb 25 18:22:03 2025 kern.warn kernel: [195198.437260] ath10k_ahb a000000.wifi: peer-unmap-event: unknown peer id 175
19039 Tue Feb 25 18:22:03 2025 kern.warn kernel: [195198.443974] ath10k_ahb a000000.wifi: peer-unmap-event: unknown peer id 175
19040 Tue Feb 25 18:22:03 2025 kern.info kernel: [195198.459252] wlan0-2: authenticate with --:--:--:--:--:--
19041 Tue Feb 25 18:22:03 2025 kern.info kernel: [195198.459365] wlan0-2: 80 MHz not supported, disabling VHT
19042 Tue Feb 25 18:22:03 2025 kern.info kernel: [195198.469860] wlan0-2: send auth to --:--:--:--:--:-- (try 1/3)
19043 Tue Feb 25 18:22:03 2025 kern.info kernel: [195198.477279] wlan0-2: authenticated
19044 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: reading /tmp/resolv.conf.d/resolv.conf.auto
19045 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using nameserver 1.1.1.1#53
19046 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using nameserver 10.74.---.---#53
19047 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using nameserver 10.74.---.---#53
19048 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using nameserver 1.1.1.1#53
19049 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for test
19050 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for onion
19051 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for localhost
19052 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for local
19053 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for invalid
19054 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for bind
19055 Tue Feb 25 18:22:03 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for lan
19056 Tue Feb 25 18:22:03 2025 daemon.notice wpa_supplicant[2143]: wlan0-2: Trying to associate with --:--:--:--:--:-- (SSID='----------------' freq=2412 MHz)
19057 Tue Feb 25 18:22:03 2025 kern.info kernel: [195198.486122] wlan0-2: associate with --:--:--:--:--:-- (try 1/3)
19058 Tue Feb 25 18:22:03 2025 kern.info kernel: [195198.493766] wlan0-2: RX ReassocResp from --:--:--:--:--:-- (capab=0x1431 status=0 aid=2)
19059 Tue Feb 25 18:22:03 2025 kern.warn kernel: [195198.495913] ath10k_ahb a000000.wifi: pdev param 0 not supported by firmware
19060 Tue Feb 25 18:22:03 2025 kern.warn kernel: [195198.501128] ath10k_ahb a000000.wifi: failed to enable peer stats info: -95
19061 Tue Feb 25 18:22:03 2025 kern.info kernel: [195198.508365] wlan0-2: associated
19062 Tue Feb 25 18:22:03 2025 daemon.notice netifd: Network device 'wlan0-2' link is up
19063 Tue Feb 25 18:22:03 2025 daemon.notice netifd: Interface 'ifWan2' has link connectivity
19064 Tue Feb 25 18:22:03 2025 daemon.notice netifd: Interface 'ifWan2' is setting up now
19065 Tue Feb 25 18:22:03 2025 kern.debug kernel: [195198.565067] wlan0-2: Limiting TX power to 20 (20 - 0) dBm as advertised by --:--:--:--:--:--
19066 Tue Feb 25 18:22:03 2025 daemon.notice wpa_supplicant[2143]: wlan0-2: Associated with --:--:--:--:--:--
19067 Tue Feb 25 18:22:03 2025 daemon.notice netifd: ifWan2 (9876): udhcpc: started, v1.34.1
19068 Tue Feb 25 18:22:03 2025 daemon.notice wpa_supplicant[2143]: wlan0-2: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
19069 Tue Feb 25 18:22:03 2025 daemon.notice netifd: ifWan2 (9876): udhcpc: broadcasting discover
19070 Tue Feb 25 18:22:03 2025 user.notice mwan3-hotplug[9833]: Execute ifdown event on interface ifWan2 (unknown)
19071 Tue Feb 25 18:22:03 2025 daemon.notice wpa_supplicant[2143]: wlan0-2: WPA: Key negotiation completed with --:--:--:--:--:-- [PTK=CCMP GTK=CCMP]
19072 Tue Feb 25 18:22:03 2025 daemon.notice wpa_supplicant[2143]: wlan0-2: CTRL-EVENT-CONNECTED - Connection to --:--:--:--:--:-- completed [id=1 id_str=]
19073 Tue Feb 25 18:22:03 2025 user.info mwan3track[3202]: Detect ifdown event on interface ifWan2 (wlan0-2)
19074 Tue Feb 25 18:22:04 2025 user.info mwan3track[3202]: Check (ping) failed for target "1.1.1.1" on interface ifWan2 (wlan0-2). Current score: 6
19075 Tue Feb 25 18:22:04 2025 daemon.notice wpa_supplicant[2143]: wlan0-2: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-43 noise=-109 txrate=1000
19076 Tue Feb 25 18:22:04 2025 user.info mwan3track[3202]: Check (ping) failed for target "8.8.8.8" on interface ifWan2 (wlan0-2). Current score: 6
19077 Tue Feb 25 18:22:04 2025 user.notice mwan3track[3202]: Interface ifWan2 (wlan0-2) is disconnecting
19078 Tue Feb 25 18:22:05 2025 user.notice mwan3track[3202]: Interface ifWan2 (wlan0-2) is offline
19079 Tue Feb 25 18:22:05 2025 user.notice mwan3-hotplug[10325]: Execute disconnected event on interface ifWan2 (wlan0-2)
19080 Tue Feb 25 18:22:06 2025 kern.info WAN (ifWan2) is down, switched to backup WAN (mob1s1a1)
19081 Tue Feb 25 18:22:06 2025 daemon.info events_reporting: Sending email to "--------@----------------.com "
19082 Tue Feb 25 18:22:06 2025 daemon.notice netifd: ifWan2 (9876): udhcpc: broadcasting discover
19083 Tue Feb 25 18:22:06 2025 daemon.notice netifd: ifWan2 (9876): udhcpc: broadcasting select for 192.168.178.64, server 192.168.178.1
19084 Tue Feb 25 18:22:06 2025 daemon.notice netifd: ifWan2 (9876): udhcpc: lease of 192.168.178.64 obtained from 192.168.178.1, lease time 86400
19085 Tue Feb 25 18:22:07 2025 daemon.notice netifd: Interface 'ifWan2' is now up
19086 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: reading /tmp/resolv.conf.d/resolv.conf.auto
19087 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using nameserver 1.1.1.1#53
19088 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using nameserver 192.168.178.21#53
19089 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using nameserver 10.74.---.---#53
19090 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using nameserver 10.74.---.---#53
19091 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using nameserver 1.1.1.1#53
19092 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for test
19093 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for onion
19094 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for localhost
19095 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for local
19096 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for invalid
19097 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for bind
19098 Tue Feb 25 18:22:07 2025 daemon.info dnsmasq[9684]: using only locally-known addresses for lan
19099 Tue Feb 25 18:22:07 2025 daemon.err events_reporting: Failed to send email to "--------@----------------.com "
19100 Tue Feb 25 18:22:07 2025 user.notice mwan3-hotplug[10580]: Execute ifup event on interface ifWan2 (wlan0-2)
19101 Tue Feb 25 18:22:08 2025 kern.info Switched to main WAN (ifWan2)
19102 Tue Feb 25 18:22:08 2025 user.info mwan3track[3202]: Detect ifup event on interface ifWan2 (wlan0-2)
19103 Tue Feb 25 18:22:09 2025 user.info mwan3track[3202]: Check (ping) success for target "1.1.1.1" on interface ifWan2 (wlan0-2). Current score: 0
19104 Tue Feb 25 18:22:09 2025 user.notice mwan3track[3202]: Interface ifWan2 (wlan0-2) is connecting
19105 Tue Feb 25 18:22:09 2025 daemon.info events_reporting: Sending email to "--------@----------------.com "
19106 Tue Feb 25 18:22:09 2025 daemon.err events_reporting: Failed to send email to "--------@----------------.com "
19107 Tue Feb 25 18:22:10 2025 user.info mwan3track[3202]: Lost 2 ping(s) on interface ifWan2 (wlan0-2). Current score: 0
19108 Tue Feb 25 18:22:10 2025 user.notice mwan3track[3202]: Interface ifWan2 (wlan0-2) is online
19109 Tue Feb 25 18:23:00 2025 cron.err crond[10564]: USER root pid 11668 cmd /usr/bin/wireguard_watchdog

I do not know what exactly triggers these attempts to send an email, and I have no idea why they fail. If they are supposed to warn me about connectivity issues, then the way via email seems to be futile.

Further suggestions are very much appreciated - thank you! :+1:

Hello,

Most likely, you have configured Event Reporting, which can be found in Services → Event Reporting in the WebUI.

Please let me know if you need any further assistance.

Best regards,

Yes, I have done that, as I described above:

The Send test email action under Administration > Recipients > Email Users > Account name is successful

I wonder why the log shows failed attempts to send emails, despite the Send test email is successful.

In detail:

(same for the other events)

Could you please let me know which email provider you are using (e.g., Gmail)?

Best regards,

Vodafone - set up as follows under email recipients:

The Send test email successfully sends a test email. And it does, too, when sending a test email from the 3 defined events reporting configurations that I showed in an earlier screenshot.

Could it be that in case of e.g. WAN failover, no email can be sent, because the failover (mob1s11 or another interface) is not ready in time? Then it might help (in a future FW update) that the router retries sending an alert email asap.

Hello,

I have sent you a form to fill out. Once completed, I will contact you privately regarding this issue. For the ticket ID, please use “12465”.

Best regards,

@Marija Thanks! I have received two emails, one with a link to the form that I have filled and submitted.

Hello,

Thank you. You will receive a response from us shortly.

Best regards,