Forums

Home › Forums › Troubleshooting › Bug report: System error lines and crashes during Wi-Fi timer re-activation

Bug report: System error lines and crashes during Wi-Fi timer re-activation

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #7486
    Casino
    Participant

    I am writing to report specific error lines and process crashes extracted from my system logs on pcWRT PW-AX1800 (v2.8.8).
    These events occur every morning right after 07:00 AM, which is the time my scheduled Wi-Fi timer turns back ON. Please note that I do not use and have never used either DNS or VPN and at the moment they are turned off.

    Below is the chronological list of the exact log lines showing errors:

    1. DDNS Configuration Error and Unrequested VPN Profile Loading

    The DDNS script triggers a critical exit error at 07:00:41 AM even though the feature is toggled OFF. Simultaneously, strongSwan automatically attempts to load non-existent profiles for NordVPN, Surfshark, and ProtonVPN.

    10/12 7:00:41 user.crit ddns-scripts: wan: CRITICAL ERROR – Service Configuration not correctly configured – EXITING
    10/12 7:00:41 authpriv.info ipsec_starter: Starting strongSwan 5.9.2 IPsec [starter]…
    10/12 7:00:41 daemon.info : 00[CFG] loaded ca certificate “C=PA, O=NordVPN, CN=NordVPN Root CA” from ‘/etc/ipsec.d/cacerts/NordVPN.pem’
    10/12 7:00:41 daemon.info : 00[CFG] loaded ca certificate “C=CH, O=ProtonVPN AG, CN=ProtonVPN Root CA” from ‘/etc/ipsec.d/cacerts/ProtonVPN_ike_root.pem’
    10/12 7:00:41 daemon.info : 00[CFG] loaded ca certificate “C=VG, O=Surfshark, CN=Surfshark Root CA” from ‘/etc/ipsec.d/cacerts/surfshark_ikev2.pem’

    2. Repeated dnsmasq SIGTERM Loop

    Between 07:00:58 AM and 07:01:13 AM, the dnsmasq service receives multiple termination signals and enters a loop, exiting 3 consecutive times within seconds.

    10/12 7:00:58 daemon.info dnsmasq: exiting on receipt of SIGTERM
    10/12 7:01:02 daemon.info dnsmasq: exiting on receipt of SIGTERM
    10/12 7:01:09 daemon.info dnsmasq: exiting on receipt of SIGTERM

    3. Forced Process Terminations (mp::instance1 SIGKILL)

    The procd process manager encounters hangs with mp::instance1. The process fails to respond to SIGTERM and the system is forced to terminate it via SIGKILL at 07:01:17 AM, 07:02:06 AM.

    10/12 7:01:17 daemon.info procd: Instance mp::instance1 pid 6031 not stopped on SIGTERM, sending SIGKILL instead
    10/12 7:02:06 daemon.info procd: Instance mp::instance1 pid 19431 not stopped on SIGTERM, sending SIGKILL instead

    Could you please verify why these errors?

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.