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

    Haproxy and Syslog after upgrade to 2.3.3

    Scheduled Pinned Locked Moved Cache/Proxy
    7 Posts 3 Posters 1.6k 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.
    • I
      IB
      last edited by

      Hi !

      I see one problem after upgrade pfSense from 2.3.2 to 2.3.3 (and 2.3.3_1). Haproxy upgraded from 0.48 to 0.52_6 and:

      • there is a new lines in packet description about logging
       <logging><logsocket>/tmp/haproxy_chroot/var/run/log</logsocket>
      	<facilityname>haproxy</facilityname>
      	<logfilename>haproxy.log</logfilename></logging> 
      
      • so, in syslog.conf generated two lines in top of file:
      !haproxy
      *.*						 %/var/log/haproxy.log
      
      • and new options on start syslogs
      -l /tmp/haproxy_chroot/var/run/log
      
      • when server start, I see messages from syslogd "Operation not supported by device" about /var/log/Haproxy.log

      • and /var/log/Haproxy.log grow up to 200 GB(!) with hex zero

      How I can fix this problem? After several reboot disk overloaded…

      1 Reply Last reply Reply Quote 0
      • I
        IB
        last edited by

        Some addition.

        I have two cluster by two servers. One cluster on x64 platform, other on x86. Situation with configs and messages is same on all 4 servers . But giant haproxy.log generates on x64 platforms only. On x86 platforms this files have a small size - 24 bytes of hex zero.

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          Works just fine here - 2.3.3_1, 2.3.4 snapshots, 2.4 snapshots.

          1 Reply Last reply Reply Quote 0
          • I
            IB
            last edited by

            @doktornotor:

            Works just fine here - 2.3.3_1, 2.3.4 snapshots, 2.4 snapshots.

            
            2.3.3-RELEASE-p1 (amd64)
            
            

            Sequentially upgraded from 2.2.x

            1 Reply Last reply Reply Quote 0
            • I
              IB
              last edited by

              … to be continued:

              1. /var/log/haproxy.log 3 Gb. Run

              
              truncate -s 0 /var/log/haproxy.log
              
              

              size 0
              2. Reboot. System booted, but syslog not started
              3. Remove file

              
              rm /var/log/haproxy.log
              
              

              and reboot
              4. System hang up on syslog start
              5. Ctrl+C, single user mode

              
              touch /var/log/haproxy.log
              reboot
              
              

              6. All right, system booted, syslog started, /var/log/haproxy.log size 600 Mb
              7. Another reboot - all right, log has same size

              Any ideas?

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

                It's a clog file, binary circular log. Don't use touch, truncate, or anything else on it that alters the log.

                If it's not in clog format, syslog will barf on it.

                /usr/local/sbin/clog -i -s 511488 /var/log/haproxy.log
                

                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
                • I
                  IB
                  last edited by

                  Sorry, I was absent and haven't access to forum

                  I find source of problem. It's appear when in field "Remote syslog host" I fill "/var/run/log", recommended for local logging. And after I clear this field - no problem with log files. But I not see any messages from Haproxy in local log.//

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