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

    HAProxy-devel crashing regularly

    Scheduled Pinned Locked Moved pfSense Packages
    10 Posts 4 Posters 3.2k 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.
    • J
      josh4trunks
      last edited by

      OS = pfSense 2.1 Release (amd64)
      Package = haproxy-devel 1.5-dev22 pkg v 0.7

      Log Output

      kernel: pid 10779 (haproxy), uid 80: exited on signal 11
      

      Configuration
      I have two frontends, one that runs on my WAN (SSL for my domains), and one that runs one one of my LAN IPs (SSL for pixelserv ad-blocking); both do SSL offloading.  This has been happening for about a month and I know it was also happening on the last haproxy-devel packaged for pfSense (I think version 1.5dev20).  Does anyone have any ideas where I can start debugging this?

      Thanks,

      1 Reply Last reply Reply Quote 0
      • L
        luky37
        last edited by

        Please post gdb backtraces [1] to the haproxy mailinglist (no need to subscribe).

        haproxy - at - formilux - dot - org
        

        [1] http://www.freebsd.org/doc/en/books/developers-handbook/debugging.html

        1 Reply Last reply Reply Quote 0
        • J
          josh4trunks
          last edited by

          @luky37:

          Please post gdb backtraces [1] to the haproxy mailinglist (no need to subscribe).

          haproxy - at - formilux - dot - org
          

          [1] http://www.freebsd.org/doc/en/books/developers-handbook/debugging.html

          I've never posted directly to a mailing list before.  Do I just send an email to that address?  Thanks,

          1 Reply Last reply Reply Quote 0
          • L
            luky37
            last edited by

            Yes, just email to that address. When you respond to someone on the ML, use "respond to all", don't just respond to that guy, so your reply is seen on the mailing list.

            Also, provide the output of "haproxy -vv" and explain what your configuration tries to do (perhaps with some relevant part of the configuration).

            1 Reply Last reply Reply Quote 0
            • J
              josh4trunks
              last edited by

              Awesome, thanks

              1 Reply Last reply Reply Quote 0
              • G
                Gisa
                last edited by

                did you find a solution for this Probelm? we have the same issue. Haproxy simply stopps

                Log Message: kernel: pid 15125 (haproxy), uid 80: exited on signal 11

                Our version:

                2.1.4-RELEASE (amd64) built on Fri Jun 20 12:59:50 EDT 2014 FreeBSD 8.3-RELEASE-p16

                1 Reply Last reply Reply Quote 0
                • J
                  josh4trunks
                  last edited by

                  this got fixed in later versions of 1.5. pfsense stopped updating this for some reason but one they do update it, it should be fixed.

                  a workaround is using the service watchdog plugin to watch and restart haproxy.

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

                    Hi guys,

                    New haproxy-devel 1.5.3 package just became available, big thanks to Jim-p how compiled the binaries for files.pfsense.org, first tests seems to indicate it 'works', despite that it is not part of the official 8.3 compatible ports tree..

                    Still a few small improvements to be made to the webgui side, and then package as a whole should be ready to replace the old haproxy packages..

                    Let me/us know if if this package indeed fixes the crashing issues some people experienced.

                    Also let me know if there are some 'important' features that should be added to this package. Currently im thinking about a few checkboxes for options in the primary-frontend like: log-tcp log-http dontlognull dontlog-normal.. and also a setting for tune.ssl.default-dh-param, another thing i want to try is to be able to link a backend to a frontend through a 'unix socket', i havnt checked if that already works, but if it can work the gui should support that.

                    I know there are probably a lot of things that aren't possible, and i don't intend to implement everything.. But if you think some option 'should' be available for common scenario's please let me know. Remember that for your very specific&advanced usecases you can most of the time be written in the 'advanced' textboxes which are included into the configfile..

                    Greets PiBa-NL

                    1 Reply Last reply Reply Quote 0
                    • J
                      josh4trunks
                      last edited by

                      Awesome glad to here it!

                      I mentioned a change before (I think in a PM) to simplify the proxymodes dropdown.

                      1 Reply Last reply Reply Quote 0
                      • G
                        Gisa
                        last edited by

                        Thanks a lot for both !!! For the workarround (it was a real good idea) and for the new version - we will test it next days.

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