1. Home
  2. pfSense® Software
  3. Traffic Shaping
  4. Queues RRD no plot data / Queues multiple times listed in on status page

Queues RRD no plot data / Queues multiple times listed in on status page

  • M

    Hello

    I'm running version 1.2-RC4 and have a strange behaviour with RRD queues (had the same already with RC3).

    • On the queues status page some queues are listed multiple times (see attachment)
    • On the RRD graphs page the queues plots are generated, but do not contain any data (see attachment).

    Actions taken:

    • RRD Database files removed for queues and queues drop & reinitialized, but still the same problem

    Q: Could there be a problem with the queues itself? E.g. why are some queues listed multiple times
    on the status page, for which only 1 per queuename (eg. penaltydown) lists traffic? Probably the RRD graph
    is working well, but somehow takes the 'empty data' from the same queue showing no values.

    I must say that the traffic shaper is working fully normally, besides the behaviour of queues listed multiple times
    on status and empty RRD graphs.

    I would appreciate any help in order to resolve this. If I shall provide any files, please contact me.

    Thanks
    Marcel

    PS: The attached image shows only queues drop on the last queue (this due to the fact that the screenshot was taken shortly after the traffic shaper was reset). In any event the result is the same when other queues have also queue-drops.



    0
  • F

    @manzmarcel:

    I'm running version 1.2-RC4 and have a strange behaviour with RRD queues.

    I've been using the embedded one.

    • On the queues status page some queues are listed multiple times (see attachment)

    I haven't this issue.

    • On the RRD graphs page the queues plots are generated, but do not contain any data (see attachment).

    Any advice to solve this issue?

    0
  • E

    Have you customized the shaper yourself after running the wizard, especially queue names?!

    0
  • F

    @eri--:

    Have you customized the shaper yourself after running the wizard, especially queue names?!

    I've done some changes in rules and queues, then I rerun the shaper wizard and I wiped the old config. Is this the cause? What can I do now?

    0
  • E

    Do you have any error messages on the log about rrd?!

    0
  • F

    @eri--:

    Do you have any error messages on the log about rrd?!

    I've just taken a look at System logs and there is nothing strange by filtering "rrd":

    Feb 24 16:52:10 	php: /interfaces_opt.php: Creating rrd update script
Feb 24 13:44:54 	php: : Creating rrd update script
Feb 24 13:44:36 	php: : Creating rrd update script
    0
  • E

    From the picture you have posted about realtime queue watching(aka Status->queues)
    It seems that you have not the queues created by the wizard!

    0
  • F

    eri,
    firestar !=  manzmarcel ;D

    Now I've also noticed that in Queue Status there are some items shown multiple times.
    What can I do? How can I really wipe Shaper configuration?

    0
  • E

    The wizard will wipe your config, be sure of it.

    From the run commands tab issue:
    rm /var/db/rrd/queue.rrd

    and then run the wizard of the traffic shaper again.

    P.S. Didn't notice the different user posting :)

    0
  • M

    Eri,

    @eri--:

    From the picture you have posted about realtime queue watching(aka Status->queues)
    It seems that you have not the queues created by the wizard!

    In my case I could only use the wizard to generate the initial base configuration. The wizard does not provide me with all the necessary options I require in order to shape additional VLANs etc. That's why I had to manually add queues to the traffic shaper.

    In any event however, manually added queues should not lead to any of the described problems in pfSense.

    0
  • E

    The rrd graphs for queues in 1.2 depend on the names of the queues.
    It is fixed in upcoming versions.

    The trick is to use the same name for the queue and add to it at the end 'up' and 'down' in them. Up for wan and down for lan.

    0
  • M

    @eri--:

    The trick is to use the same name for the queue and add to it at the end 'up' and 'down' in them. Up for wan and down for lan.

    In my configuration I have named the queues already exactly like that (based on the qVOIPUp/qVOIPDown example as generated by the wizard):

    qVOIPUp   
    qVOIPDown 
    qSCINETUp 
    qSCINETDown 
    qCLIENTSUp 
    qCLIENTSDown 
    qSNUp 
    qSNDown 
    qPenaltyUp 
    qPenaltyDown

    All the queue names appear in the plot-legend of the RRD graph, but the graph itself doesn't plot any values - unfortunately ;-(

    0
  • E

    Then i think you need to remove the rrd queue database:
    rm /var/db/rrd/queue.rrd

    0
  • M

    That doesn't help neither. I've done this already multiple times.

    I erased the files wan-queues.rrd, wan-queuesdrop.rrd and had them recreated.

    The problem remains the same all the time. As from the log output, no error is reported while the update script regenerates them.

    0
  • E

    Do you see any traffic from Status->Queues passing on queues?!

    0
  • M

    Absolutely. See my first two screenshots on the first posting.

    For some reason the queues appear on the status page up to 3 times the same (as user firestar is also seeing it).

    I assume there must be some kind of error here, as the RRD plot might simply take the null values of a such 'multiple listed' queue, for which only one shows values, whereas the other bars remain on 0.

    0
  • E

    Then you have a corrupted config mostly.

    Check it by getting your config.xml and verify it is not corrupted.

    0
  • M

    I have just checked the config.xml and it looks fine to me (queues are correctly listed once there, as seen in traffic shaper web gui).

    Have no clue why they show multiple times on status page. Are queues / rrd config exported to some other config files, so I could check them as well?

    0
  • F

    @eri--:

    The rrd graphs for queues in 1.2 depend on the names of the queues.
    It is fixed in upcoming versions.

    What do you mean for 'upcoming versions': 1.3 or final 1.2?
    Has the final 1.2 version this fix?

    0
  • E

    It is not an issue on pfSense.
    It is just your issue. For upcoming i say that the rrd building does not depend on names that's all.

    Please post an output of pfctl -vsq a screen shot from Status->queue and an output from running /var/db/rrd/update.sh or updatedb.sh

    Thx.

    0
  • F

    Output of pfctl -vsq:

    
queue root_vr1 bandwidth 250Kb priority 0 {qwanRoot}
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue  qwanRoot bandwidth 250Kb priority 0 {qwandef, qwanacks, qVOIPUp, qPenaltyUp, qP2PUp, qOthersUpH, qOthersUpL}
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qwandef bandwidth 2.50Kb qlimit 500 hfsc( default realtime 2.50Kb )
  [ pkts:      13640  bytes:    6969697  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue   qwanacks bandwidth 62.50Kb priority 7 hfsc( realtime 25Kb )
  [ pkts:     375009  bytes:   24062222  dropped pkts:    409 bytes:  25802 ]
  [ qlength:   0/ 50 ]
queue   qVOIPUp bandwidth 62.50Kb priority 6 hfsc( realtime 64Kb )
  [ pkts:       4648  bytes:    2711671  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qPenaltyUp bandwidth 2.50Kb priority 2 qlimit 500 hfsc( red ecn upperlimit 100Kb )
  [ pkts:       1691  bytes:     886699  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue   qP2PUp bandwidth 15Kb hfsc( red ecn realtime 1Kb upperlimit 130Kb )
  [ pkts:     911473  bytes:  264851465  dropped pkts:   7283 bytes: 2233843 ]
  [ qlength:   0/ 50 ]
queue   qOthersUpH bandwidth 62.50Kb priority 4 hfsc( red ecn realtime 1Kb )
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qOthersUpL bandwidth 2.50Kb priority 2 qlimit 500 hfsc( red ecn realtime 1Kb )
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue root_vr0 bandwidth 1.70Mb priority 0 {qlanRoot}
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue  qlanRoot bandwidth 1.70Mb priority 0 {qlandef, qlanacks, qVOIPDown, qPenaltyDown, qP2PDown, qOthersDownH, qOthersDownL}
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qlandef bandwidth 17Kb qlimit 500 hfsc( default realtime 17Kb )
  [ pkts:      40642  bytes:   30806889  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue   qlanacks bandwidth 425Kb priority 7 hfsc( realtime 170Kb )
  [ pkts:     811068  bytes:   45836177  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qVOIPDown bandwidth 425Kb priority 6 hfsc( realtime 64Kb )
  [ pkts:     250586  bytes:  330159182  dropped pkts:    115 bytes: 143466 ]
  [ qlength:   0/ 50 ]
queue   qPenaltyDown bandwidth 17Kb priority 2 qlimit 500 hfsc( red ecn upperlimit 640Kb )
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue   qP2PDown bandwidth 17Kb qlimit 500 hfsc( red ecn realtime 1Kb upperlimit 800Kb )
  [ pkts:     343647  bytes:  239599299  dropped pkts:   1273 bytes: 774445 ]
  [ qlength:   0/500 ]
queue   qOthersDownH bandwidth 425Kb priority 4 hfsc( red ecn realtime 1Kb )
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qOthersDownL bandwidth 17Kb priority 2 qlimit 500 hfsc( red ecn realtime 1Kb )
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue root_ath0 bandwidth 1.70Mb priority 0 {qlanRoot}
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue  qlanRoot bandwidth 1.70Mb priority 0 {qlandef, qlanacks, qVOIPDown, qPenaltyDown, qP2PDown, qOthersDownH, qOthersDownL}
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qlandef bandwidth 17Kb qlimit 500 hfsc( default realtime 17Kb )
  [ pkts:      13429  bytes:    3232640  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue   qlanacks bandwidth 425Kb priority 7 hfsc( realtime 170Kb )
  [ pkts:       1691  bytes:      93558  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qVOIPDown bandwidth 425Kb priority 6 hfsc( realtime 64Kb )
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qPenaltyDown bandwidth 17Kb priority 2 qlimit 500 hfsc( red ecn upperlimit 640Kb )
  [ pkts:       3388  bytes:    3548265  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue   qP2PDown bandwidth 17Kb qlimit 500 hfsc( red ecn realtime 1Kb upperlimit 800Kb )
  [ pkts:         15  bytes:       1676  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]
queue   qOthersDownH bandwidth 425Kb priority 4 hfsc( red ecn realtime 1Kb )
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/ 50 ]
queue   qOthersDownL bandwidth 17Kb priority 2 qlimit 500 hfsc( red ecn realtime 1Kb )
  [ pkts:          0  bytes:          0  dropped pkts:      0 bytes:      0 ]
  [ qlength:   0/500 ]

    Screen shot from Status->queue: see attachment

    Output from running /var/db/rrd/update.sh or updatedb.sh says Command not found


    0
  • E

    Can you please tell me how did you manage to do from the wizard or shaper interface in 1.2 create shaper on 3 interfaces?!

    the command is /var/db/rrd/updaterrd.sh

    0
  • F

    @ermal:

    Can you please tell me how did you manage to do from the wizard or shaper interface in 1.2 create shaper on 3 interfaces?!

    I used the Traffic Shaper Wizard. I didn't create rules or queues by hand, only edited some parameters in them. I don't understand what is the problem. Be clear.

    the command is /var/db/rrd/updaterrd.sh

    Output is:

    /var/db/rrd/updaterrd.sh
/var/db/rrd/updaterrd.sh: Permission denied.

    I need to chmod +x it, then:

    /var/db/rrd/updaterrd.sh
ERROR: tmplt contains more DS definitions than RRD
ERROR: tmplt contains more DS definitions than RRD

    …the script doesn't return to the shell. I have to press CTRL+C to logout from SSH.

    0
  • E

    I do not know what you have done, but it does not seem to me as a config created from a 1.2 shaper wizard.

    So you are on your own.

    0
  • H

    Download your config.xml from diagnostics>backup/restore. Strip the trafficshaper section from it and replace it by a virgin part of the default config.xml. Reupload the modified config.xml and restart from scratch.

    0
  • F

    @hoba:

    Download your config.xml from diagnostics>backup/restore. Strip the trafficshaper section from it and replace it by a virgin part of the default config.xml. Reupload the modified config.xml and restart from scratch.

    Just tried to do it, but RRD's queue graphs are still empty, whilst in queue status there are multiple items.
    Don't understand why this happens.
    If there aren't any files to edit/remove, I will update to final 1.2. It is an embedded install and I need to reflash it completely and reupload config with no shaper section in it.

    0
Log in to reply
 

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

© 2020 Rubicon Communications, LLC | Privacy Policy