Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Hot Plug Event / Watchdog on LAN - help

    General pfSense Questions
    4
    12
    2933
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rbrooks8 last edited by

      Hello,

      I'm running 2.0.3-RELEASE version.  Simple setup  with LAN, WAN, and openVPN.

      Plagued with following log issues and disconnects on LAN starting a month or so ago:

      Nov 5 09:40:21 apinger: Exiting on signal 15.
      Nov 5 09:40:22 check_reload_status: Reloading filter
      Nov 5 09:40:23 apinger: Starting Alarm Pinger, apinger(5162)
      Nov 5 09:42:42 kernel: sk1: watchdog timeout
      Nov 5 09:42:42 kernel: sk1: can not stop transfer of Tx descriptor
      Nov 5 09:42:42 kernel: sk1: link state changed to DOWN
      Nov 5 09:42:42 check_reload_status: Linkup starting sk1
      Nov 5 09:42:44 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.168.1)
      Nov 5 09:42:46 check_reload_status: Linkup starting sk1
      Nov 5 09:42:46 kernel: sk1: link state changed to UP
      Nov 5 09:42:48 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.168.1)
      Nov 5 09:42:49 check_reload_status: rc.newwanip starting sk1
      Nov 5 09:42:51 php: : rc.newwanip: Informational is starting sk1.
      Nov 5 09:42:51 php: : rc.newwanip: on (IP address: 192.168.168.1) (interface: lan) (real interface: sk1).
      Nov 5 09:42:51 apinger: Exiting on signal 15.
      Nov 5 09:42:52 check_reload_status: Reloading filter
      Nov 5 09:42:52 apinger: Starting Alarm Pinger, apinger(31660)
      Nov 5 09:45:08 kernel: sk1: watchdog timeout
      Nov 5 09:45:08 kernel: sk1: can not stop transfer of Tx descriptor
      Nov 5 09:45:08 kernel: sk1: link state changed to DOWN
      Nov 5 09:45:08 check_reload_status: Linkup starting sk1
      Nov 5 09:45:10 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.168.1)

      Diagnostic attempts:

      -Relocated box to a different environment (it was warm in the original location)
      -Replaced LAN NIC

      The LAN card is connected to one of a couple of simple (But large) switches.  This seems to come out of nowhere and be problematic for a few hours and then goes away for a couple of weeks.  Currently I'm offsite hundreds of miles away and a rather unknowledgeable person is having issues and pestering me.  I'm thinking switch or cable at this point.  Is there anything other than trying cable and switch at this point?  Does any of that look like pfsense/local hardware?

      Thanks in advance.

      1 Reply Last reply Reply Quote 0
      • M
        muswellhillbilly last edited by

        @rbrooks8:

        I'm running 2.0.3-RELEASE version.  Simple setup  with LAN, WAN, and openVPN.

        I would upgrade to the newest release (2.2.4) and see if that solves the problem. 2.0.3 was released over 2 and a half years ago.

        1 Reply Last reply Reply Quote 0
        • R
          rbrooks8 last edited by

          @muswellhillbilly:

          @rbrooks8:

          I'm running 2.0.3-RELEASE version.  Simple setup  with LAN, WAN, and openVPN.

          I would upgrade to the newest release (2.2.4) and see if that solves the problem. 2.0.3 was released over 2 and a half years ago.

          Now I seem to have that problem AND it reboots every 5 or 10 minutes for no apparent reason.

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned last edited by

            I think that hardware is ready for its final travel to garbage.

            1 Reply Last reply Reply Quote 0
            • M
              muswellhillbilly last edited by

              I agree with Dok. Give it a vikings funeral.

              1 Reply Last reply Reply Quote 0
              • R
                rbrooks8 last edited by

                I'm ok with that if that's the case, but should I be looking at switches or cables as well?

                1 Reply Last reply Reply Quote 0
                • M
                  muswellhillbilly last edited by

                  If the hardware is rebooting itself every 5 minutes, then I'd be inclined to blame the tin. I've yet to see a dodgy network cable that could cause a firewall to reboot itself every few minutes. Ask yourself how old the machine is. If the answer is 'over 5 years', then it's time to change it.

                  1 Reply Last reply Reply Quote 0
                  • R
                    rbrooks8 last edited by

                    I got a crash dump.  Any interest in looking at it?

                    1 Reply Last reply Reply Quote 0
                    • R
                      rbrooks8 last edited by

                      Well, swapping out the hardware in full (just popped the hard drive into a whole new chassis) sure helped.  I still got one random drop in the middle of the night tonight, but prior to that from midday Friday until then the only other issue was an ISP modem reboot.

                      Nov 8 00:15:01 kernel: sk1: link state changed to DOWN
                      Nov 8 00:15:01 kernel: sk1: link state changed to UP
                      Nov 8 00:15:01 check_reload_status: Linkup starting sk1
                      Nov 8 00:15:01 check_reload_status: Linkup starting sk1
                      Nov 8 00:15:02 php-fpm: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.168.1 )
                      Nov 8 00:15:02 php-fpm: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.168.1 )
                      Nov 8 00:15:02 php-fpm: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.168.1 )
                      Nov 8 00:15:02 php-fpm: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.168.1 )
                      Nov 8 00:15:02 check_reload_status: rc.newwanip starting sk1
                      Nov 8 00:15:03 php-fpm: /rc.newwanip: rc.newwanip: Info: starting on sk1.
                      Nov 8 00:15:03 php-fpm: /rc.newwanip: rc.newwanip: Info: starting on sk1.
                      Nov 8 00:15:03 php-fpm: /rc.newwanip: rc.newwanip: on (IP address: 192.168.168.1) (interface: LAN[lan]) (real interface: sk1).
                      Nov 8 00:15:03 php-fpm: /rc.newwanip: rc.newwanip: on (IP address: 192.168.168.1) (interface: LAN[lan]) (real interface: sk1).
                      Nov 8 00:15:03 check_reload_status: Reloading filter

                      What do you think could be causing 4 hotplug events within seconds like that?

                      1 Reply Last reply Reply Quote 0
                      • R
                        rbrooks8 last edited by

                        More of the same, about every half hour the hotplug alert.  At least no more kernel crashes and it comes back online quickly.  I'm swapping out the switches in the next day or so.  Hoping until then that it maintains.

                        1 Reply Last reply Reply Quote 0
                        • D
                          divsys last edited by

                          Did you ever bring that up to the latest release (2.2.5)?

                          Well worth the effort and would get you on a solid footing for troubleshooting (if required at all).

                          -jfp

                          1 Reply Last reply Reply Quote 0
                          • R
                            rbrooks8 last edited by

                            @divsys:

                            Did you ever bring that up to the latest release (2.2.5)?

                            Well worth the effort and would get you on a solid footing for troubleshooting (if required at all).

                            Yes, I did that before I swapped the hardware.  Still had the kernel crashes and watchdog nonsense until I swapped the chassis.  Now the only remaining symptom is the LAN hotplug event (and my android clients for OpenVPN quit working).

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post