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

    Rebooting WLAN AP brings back Internet

    Scheduled Pinned Locked Moved General pfSense Questions
    14 Posts 3 Posters 553 Views 3 Watching
    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.
    • stephenw10S Offline
      stephenw10 Netgate Administrator
      last edited by

      It's in /var/crash if it was created correctly.

      M 1 Reply Last reply Reply Quote 0
      • M Offline
        michmoor LAYER 8 Rebel Alliance @stephenw10
        last edited by

        @stephenw10

        I’m afraid there’s no report at least with a correct timestamp

        7896b131-6724-4602-89f0-efcecb3b088d-image.jpeg

        Firewall: NetGate,Palo Alto-VM,Juniper SRX
        Routing: Juniper, Arista, Cisco
        Switching: Juniper, Arista, Cisco
        Wireless: Unifi, Aruba IAP
        JNCIP,CCNP Enterprise

        1 Reply Last reply Reply Quote 0
        • stephenw10S Offline
          stephenw10 Netgate Administrator
          last edited by

          Hmm, well it may have been unable to create one. Or there may not have been a full report. The system logs should show some errors at that time though. Anything beyond that php-fpm.socket logs? That looks like php stopped for some reason.

          M 1 Reply Last reply Reply Quote 0
          • M Offline
            michmoor LAYER 8 Rebel Alliance @stephenw10
            last edited by michmoor

            @stephenw10 i pulled the logs from July 15. Incident started around 5:40am ET

            Just looking at the logs for whatever reason the WAN interface got a private WAN address. tshoot.txt

            The file is uploaded in this post.

            The logs are flooded with the check reload status script. Not sure what it does but I've had numerous problems with it in the past.

            Jul 15 10:31:24 790CCV-FW nginx: 2024/07/15 10:31:24 [crit] 71318#100224: *264 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443"
            Jul 15 10:31:24 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:25 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:26 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:27 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:28 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:28 790CCV-FW nginx: 2024/07/15 10:31:28 [crit] 71318#100224: *267 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/"
            Jul 15 10:31:29 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:29 790CCV-FW nginx: 2024/07/15 10:31:29 [crit] 71318#100224: *267 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/"
            Jul 15 10:31:30 790CCV-FW nginx: 2024/07/15 10:31:30 [crit] 71318#100224: *267 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/"
            Jul 15 10:31:30 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:31 790CCV-FW nginx: 2024/07/15 10:31:31 [crit] 71318#100224: *267 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET /crash_reporter.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/"
            Jul 15 10:31:31 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:32 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:33 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:34 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:35 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:36 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:37 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:38 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:39 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:40 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:41 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:42 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:43 790CCV-FW nginx: 2024/07/15 10:31:43 [crit] 71318#100224: *273 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443"
            Jul 15 10:31:43 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:44 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:45 790CCV-FW nginx: 2024/07/15 10:31:45 [crit] 71318#100224: *273 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET /crash_reporter.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/"
            Jul 15 10:31:45 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:46 790CCV-FW nginx: 2024/07/15 10:31:46 [crit] 71318#100224: *277 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET /crash_reporter.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/crash_reporter.php"
            Jul 15 10:31:46 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:47 790CCV-FW nginx: 2024/07/15 10:31:47 [crit] 71318#100224: *277 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET /crash_reporter.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/crash_reporter.php"
            Jul 15 10:31:47 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:47 790CCV-FW nginx: 2024/07/15 10:31:47 [crit] 71318#100224: *277 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET /crash_reporter.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/crash_reporter.php"
            Jul 15 10:31:48 790CCV-FW nginx: 2024/07/15 10:31:48 [crit] 71318#100224: *277 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET /crash_reporter.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/crash_reporter.php"
            Jul 15 10:31:48 790CCV-FW nginx: 2024/07/15 10:31:48 [crit] 71318#100224: *277 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET /crash_reporter.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/crash_reporter.php"
            Jul 15 10:31:48 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:49 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:50 790CCV-FW nginx: 2024/07/15 10:31:50 [crit] 71318#100224: *277 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET /crash_reporter.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/crash_reporter.php"
            Jul 15 10:31:50 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:50 790CCV-FW nginx: 2024/07/15 10:31:50 [crit] 71318#100224: *277 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/crash_reporter.php"
            Jul 15 10:31:51 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:51 790CCV-FW nginx: 2024/07/15 10:31:51 [crit] 71318#100224: *277 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or directory) while connecting to upstream, client: 192.168.70.103, server: , request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "192.168.70.254:10443", referrer: "https://192.168.70.254:10443/"
            Jul 15 10:31:52 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:53 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            Jul 15 10:31:54 790CCV-FW check_reload_status[665]: Could not connect to /var/run/php-fpm.socket
            
            

            Firewall: NetGate,Palo Alto-VM,Juniper SRX
            Routing: Juniper, Arista, Cisco
            Switching: Juniper, Arista, Cisco
            Wireless: Unifi, Aruba IAP
            JNCIP,CCNP Enterprise

            GertjanG 1 Reply Last reply Reply Quote 0
            • GertjanG Offline
              Gertjan @michmoor
              last edited by

              @michmoor

              For a reason yet to be determined, PHP stopped.

              This :

              Rebooting WLAN AP brings back Internet

              will take down the (a) LAN interface, and when it comes back, this will trigger the restart of many processes, and among them, PHP.

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 1
              • stephenw10S Offline
                stephenw10 Netgate Administrator
                last edited by

                Hmm, all of that is probably because php has stopped. Is there an initial log showing why php might have stopped?

                M 1 Reply Last reply Reply Quote 0
                • M Offline
                  michmoor LAYER 8 Rebel Alliance @stephenw10
                  last edited by

                  @stephenw10 Been scanning the log files of the 15th and i don't see anything sticking out at all.
                  Based on what @Gertjan it makes sense why connectivity was restored - LAN interface went down and most processes restarted. However as a troubleshooting step i did log into the firewall and restart PHP and that had no effect.

                  Curious @stephenw10 Why does a port bounce trigger so many processes restarts? Assuming no 3rd party packages.

                  Firewall: NetGate,Palo Alto-VM,Juniper SRX
                  Routing: Juniper, Arista, Cisco
                  Switching: Juniper, Arista, Cisco
                  Wireless: Unifi, Aruba IAP
                  JNCIP,CCNP Enterprise

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S Offline
                    stephenw10 Netgate Administrator
                    last edited by

                    Because anything listening on that interface will be restarted and that includes a lot of things (DHCP, DNS etc). Even more things because some of those processes will restart other processes.

                    M 1 Reply Last reply Reply Quote 0
                    • M Offline
                      michmoor LAYER 8 Rebel Alliance @stephenw10
                      last edited by

                      @stephenw10 interesting. Is this architecturally done on purpose?

                      Firewall: NetGate,Palo Alto-VM,Juniper SRX
                      Routing: Juniper, Arista, Cisco
                      Switching: Juniper, Arista, Cisco
                      Wireless: Unifi, Aruba IAP
                      JNCIP,CCNP Enterprise

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S Offline
                        stephenw10 Netgate Administrator
                        last edited by

                        Yes, many things must be restarted if they are listening directly on an interface that goes down. Otherwise they just throw errors and stop listening on any other interface.

                        M 1 Reply Last reply Reply Quote 1
                        • M Offline
                          michmoor LAYER 8 Rebel Alliance @stephenw10
                          last edited by

                          @stephenw10 gotcha. Thanks for taking the time out to explain. Much appreciated.

                          Firewall: NetGate,Palo Alto-VM,Juniper SRX
                          Routing: Juniper, Arista, Cisco
                          Switching: Juniper, Arista, Cisco
                          Wireless: Unifi, Aruba IAP
                          JNCIP,CCNP Enterprise

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.