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

    Haproxy-devel v0.23 on 2.2.1 i386 - error writing config file

    Scheduled Pinned Locked Moved Cache/Proxy
    3 Posts 2 Posters 856 Views
    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
      pffan
      last edited by

      So I have a formerly working configuration that, after temporarily disabling my front end, now won't correctly generate a config file.  The first backend has no servers and yet I have two defined.  While I have changed the names for obscurity, there's nothing special about the names I've chosen that should affect parsing of the configuration.  I also notice that "applying" settings takes a long time to complete.  I can't even begin to imagine what I did to cause this.  Thoughts?

      
      backend WEB01_http_ipvANY
      	mode			http
      	timeout connect		30000
      	timeout server		30000
      	retries			3
      	option			httpchk
      
      backend WEB02_http_ipvANY
      	mode			http
      	timeout connect		60000
      	timeout server		60000
      	retries			2
      	option			httpchk OPTIONS / 
      	server			webserver 192.168.xxx.xxx:443 ssl check inter 1000  weight 10 verify none 
      
      
      1 Reply Last reply Reply Quote 0
      • P
        PiBa
        last edited by

        Could you run the following command for your configured servers names on pfsense console? (replace www.google.com)

        drill www.google.com A @127.0.0.1 | grep www.google.com
        

        If that code does not show the server ip's that could explain 'missing' servers, though saving the config taking a long time might indicate a dns problem as well..

        If a cname is returned could try the 'fix' in here?: https://forum.pfsense.org/index.php?topic=93148.msg517620#msg517620

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

          I'm a little late updating, but it was indeed a dns problem.

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