Strange log messages - then a crash



  • We noticed some strange log messages today for about 5 hrs today. Then, the system crashed. The messages below repeated up until the crash. I've pasted a copy of the messages that continually repeated up until the crash.

    I've confirmed no one was using nor attempting to use the OVPN service today. The messages combined with a crash (first crash in years) make my spidey senses tingle, and I'm hopeful someone can give me a clue what might have been happening.

    Thanks, FS

    Jan  5 14:50:59 pfSense php: rc.start_packages: Restarting/Starting all packages.
    Jan  5 14:51:01 pfSense check_reload_status: updating dyndns WAN_DHCP
    Jan  5 14:51:01 pfSense check_reload_status: Restarting ipsec tunnels
    Jan  5 14:51:01 pfSense check_reload_status: Restarting OpenVPN tunnels/interfaces
    Jan  5 14:51:03 pfSense php: rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.
    Jan  5 14:51:03 pfSense php: rc.openvpn: OpenVPN: Resync server1 OpenVPN Server
    Jan  5 14:51:03 pfSense php: rc.dyndns.update: phpDynDNS (xxxx.dyndns.org): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
    Jan  5 14:51:03 pfSense kernel: in6_purgeaddr: link-local all-nodesmulticast address deletion error
    Jan  5 14:51:03 pfSense kernel: in6_purgeaddr: node-local all-nodesmulticast address deletion error
    Jan  5 14:51:03 pfSense kernel: ovpns1: link state changed to DOWN
    Jan  5 14:51:03 pfSense kernel: ovpns1: link state changed to UP
    Jan  5 14:51:03 pfSense check_reload_status: rc.newwanip starting ovpns1
    Jan  5 14:51:06 pfSense php: rc.newwanip: rc.newwanip: Informational is starting ovpns1.
    Jan  5 14:51:06 pfSense php: rc.newwanip: rc.newwanip: on (IP address: 10.XXX.XXX.1) (interface: []) (real interface: ovpns1).
    Jan  5 14:51:06 pfSense php: rc.newwanip: pfSense package system has detected an ip change  ->  10.XXX.XXX.1 … Restarting packages.
    Jan  5 14:51:06 pfSense check_reload_status: Starting packages



  • @fatsailor:

    We noticed some strange log messages today for about 5 hrs today. Then, the system crashed. The messages below repeated up until the crash. I've pasted a copy of the messages that continually repeated up until the crash.

    I've confirmed no one was using nor attempting to use the OVPN service today. The messages combined with a crash (first crash in years) make my spidey senses tingle, and I'm hopeful someone can give me a clue what might have been happening.

    Thanks, FS

    Jan  5 14:50:59 pfSense php: rc.start_packages: Restarting/Starting all packages.
    Jan  5 14:51:01 pfSense check_reload_status: updating dyndns WAN_DHCP
    Jan  5 14:51:01 pfSense check_reload_status: Restarting ipsec tunnels
    Jan  5 14:51:01 pfSense check_reload_status: Restarting OpenVPN tunnels/interfaces
    Jan  5 14:51:03 pfSense php: rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.
    Jan  5 14:51:03 pfSense php: rc.openvpn: OpenVPN: Resync server1 OpenVPN Server
    Jan  5 14:51:03 pfSense php: rc.dyndns.update: phpDynDNS (xxxx.dyndns.org): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
    Jan  5 14:51:03 pfSense kernel: in6_purgeaddr: link-local all-nodesmulticast address deletion error
    Jan  5 14:51:03 pfSense kernel: in6_purgeaddr: node-local all-nodesmulticast address deletion error
    Jan  5 14:51:03 pfSense kernel: ovpns1: link state changed to DOWN
    Jan  5 14:51:03 pfSense kernel: ovpns1: link state changed to UP
    Jan  5 14:51:03 pfSense check_reload_status: rc.newwanip starting ovpns1
    Jan  5 14:51:06 pfSense php: rc.newwanip: rc.newwanip: Informational is starting ovpns1.
    Jan  5 14:51:06 pfSense php: rc.newwanip: rc.newwanip: on (IP address: 10.XXX.XXX.1) (interface: []) (real interface: ovpns1).
    Jan  5 14:51:06 pfSense php: rc.newwanip: pfSense package system has detected an ip change  ->  10.XXX.XXX.1 … Restarting packages.
    Jan  5 14:51:06 pfSense check_reload_status: Starting packages

    This appears to be related to apinger. We turned off gateway monitoring, and that solved the problem.


Log in to reply