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

    PoolDown problem, no connection on HTTP?

    General pfSense Questions
    2
    3
    1.4k
    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.
    • P
      pingulino
      last edited by

      I'm setting up inbound load-balancing, one pfsense and 2 webservers (both OpenSuse).
      webb1 = normal, webb2 = PoolDown.
      I'm using 4 ports (441-444) so I have set up one Pool & one PoolDown for each port.
      It works fine as long as "Monitor" is set to ICMP - I shut down webb1 and traffic immediately goes to webb2.
      However, changing "Monitor" to HTTP redirecting does not happen.
      In the logs and in Status->Load Balancing webb1 shows as down on all ports, but as said, the only active PoolDown server is the ones I've set to Monitor ICMP.

      Reading the logs, problem seems to be that pfSense doesn't get any connection to port 80 at all - the port is open, I can connect from outside to port80 on both webbservers.
      Snippet from System Logs -> System:

      3 lines for each webserver, HTTP monitored  (Muliplied 3 times of course): 
      relayd[47139]: host 172.16.4.2, check http code (9ms), state unknown -> down, availability 0.00%
      relayd[47139]: host 172.16.4.102, check http code (9ms), state unknown -> down, availability 0.00%
      And the 4:th line, for working PoolDown-server:
      relayd[47139]: host 172.16.4.2, check icmp (0ms), state unknown -> up, availability 100.00%
      relayd[47139]: host 172.16.4.102, check icmp (0ms), state unknown -> up, availability 100.00%
      
      

      As it's a webserver I do want to monitor http.
      Also, this is a testing scenario I've set up in VirtualBox.
      (Not sure under which category to post, feel free to move it elsewhere.)

      1 Reply Last reply Reply Quote 0
      • P
        pingulino
        last edited by

        Changing Monitor to TCP works fine.
        Maybe I can use that - only need to be sure then exactly what is monitored as "Generic TCP" isn't a very clear expression.

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          When you have it set to TCP it just tries to connect to the port, it doesn't check that a response is proper, only that a connection can be established.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

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