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

    Error messages from Traffic Sharper

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 3 Posters 541 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.
    • T
      tomli
      last edited by

      Hi All,

      My pfsense have three interfaces (wan, lan and wan2). Wan2 (em2) is standby interface and no cable connect it. After upgrade to version 2.4.5_p1, the pfsense show the below error message:-

      There were error(s) loading the rules: /tmp/rules.debug:136: errors in queue definition - The line in question reads [136]: queue qDefault on em2 priority 3 priq ( ecn , default )
      @ 2020-10-17 17:50:57
      There were error(s) loading the rules: /tmp/rules.debug:136: errors in queue definition - The line in question reads [136]: queue qDefault on em2 priority 3 priq ( ecn , default )
      @ 2020-10-17 17:51:01
      There were error(s) loading the rules: /tmp/rules.debug:136: errors in queue definition - The line in question reads [136]: queue qDefault on em2 priority 3 priq ( ecn , default )
      @ 2020-10-17 17:51:07

      If I remove the traffic sharper configuration for this interface, I cannot see the above messages. Please advise.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Probably going to need to see the ruleset file or at least the traffic shaper section of it with that in place to see what's triggering that.

        1 Reply Last reply Reply Quote 0
        • viktor_gV
          viktor_g Netgate
          last edited by

          Please show /tmp/rules.debug to check these lines

          1 Reply Last reply Reply Quote 0
          • T
            tomli
            last edited by

            FYI. Thanks

            cat -n /tmp/rule.debug

            135 altq on em2 priq queue { qDefault, qVoIP, qACK }
            136 queue qDefault on em2 priority 3 priq ( ecn , default )

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              That in itself doesn't look incorrect but clearly it's invalid in some way. Duplicate line maybe?

              For a reference a ruleset that loads fine might include the altq definitions like:

               altq on vtnet0 priq bandwidth 100Mb queue {  qACK,  qDefault,  qOthersHigh,  qOthersLow  } 
               queue qACK on vtnet0 priority 6 priq (  ecn  )  
               queue qDefault on vtnet0 priority 3 priq (  ecn  , default  )  
               queue qOthersHigh on vtnet0 priority 4 priq (  ecn  )  
               queue qOthersLow on vtnet0 priority 2 priq (  ecn  )  
               
               altq on vtnet1 priq bandwidth 104857.6Kb queue {  qLink,  qACK,  qOthersHigh,  qOthersLow  } 
               queue qLink on vtnet1 priority 2 qlimit 500 priq (  ecn  , default  )  
               queue qACK on vtnet1 priority 6 priq (  ecn  )  
               queue qOthersHigh on vtnet1 priority 4 priq (  ecn  )  
               queue qOthersLow on vtnet1 priority 3 priq (  ecn  ) 
              

              You do not have a root queue bandwidth set which I'm not sure is valid. How did you create that?

              Steve

              1 Reply Last reply Reply Quote 0
              • T
                tomli
                last edited by

                You are right. I configure the bandwidth and then working.

                Thanks.

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