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

    Haproxy-devel 1.5.9 pkg v0.20 won't start after upgrade 2.1.5 to 2.2 i386

    Scheduled Pinned Locked Moved Cache/Proxy
    3 Posts 2 Posters 1.1k 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

      I copied my production config to my test rig and upgraded to pfsense 2.2 i386 but haproxy-devel won't start.

      I found this in the system log during the upgrade:

      
      Mar 3 14:45:57 	php-fpm[44963]: /rc.start_packages: XML error: Invalid document end at line 150 in /usr/local/pkg/haproxy_xmlrpcsyncclient.inc
      

      Removing and reinstalling the package made no difference but strangely enough, this error didn't recur.  Reinstalling or restarting the package only begets this:

      Mar 3 15:06:34 	php: haproxy: started new pid:none
      Mar 3 15:06:34 	php: haproxy: starting old pid:none
      Mar 3 15:06:13 	check_reload_status: Reloading filter
      Mar 3 15:06:13 	php-fpm[60011]: /pkg_mgr_install.php: Successfully installed package: haproxy-devel.
      

      The file in question looks fine.  Line 150 happens to be the very end and shows correctly in my ssh console so I'm not sure what the problem could be.

      Any suggestions or reading material would be greatly appreciated.

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

        My own stupid fault.  In the advanced pass through options I manually bound haproxy to port 80 to facilitate http > https redirection and specified the public ip of my production environment which is inaccessible from my test bench.

        I am not a smart man.

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

          f.y.i. in (somewhat) recent versions of the package its possible to create multiple 'binds' using the normal webgui options. So its possible to have 1 frontend listen on both :443(with ssl-offloading) and :80. So you don't need the bind in 'advanced pass through' anymore.

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