2.2.5 BandwidthD Error: Please start bandwidthd… But other files work?



  • I have a new installation of PfSense and it's really nice.

    I am trying to figure out why the BandwidthD package is not working correctly.  I installed BandwidthD (and I've removed it and reinstalled) and I constantly get the error of "Please start bandwidthd to populate this directory." when it goes to https://IP/bandwidthd/index.html

    What puzzles me is BandwidthD works if I remove index.html and visit https://IP/bandwidthd/ - things work normally and I can see charts.  The issue comes back when I click on the "Daily" or "Yearly" link.  The "Weekly" (Index2) and "Monthly" (Index3) both work as anticipated.

    I have verified "Enable Bandwidthd" is checked and the system logs show it's running:

    Nov 10 12:07:01 bandwidthd: Packet Encoding: Ethernet
    Nov 10 12:07:01 bandwidthd: Opening igb1
    Nov 10 12:07:01 bandwidthd: Monitoring subnet 255.255.255.255 with netmask 255.255.255.255

    Did I do something wrong?  Any ideas or tips on how to fix or troubleshoot this?



  • It looks like this may be a common issue - as BandwidthD is not being actively maintained… https://redmine.pfsense.org/issues/3986

    I'm going to poke around and see if I can figure out the cause...



  • I made some changes to pfBlockerNG and I noticed the functionality of BandwidthD changed so I would make the assumption there's a conflict between pfBlockerNG and BandwidthD.  I'm going to uninstall pfBlockerNG to see if this fixes the issue.

    I used pfBlockerNG to block both incoming and outgoing traffic to countries I do not normally do traffic with.  When some strange issues came up, I noticed some of the games the kids play on go to the country that I thought I didn't even need to reach.  I changed the pfBlockerNG functionality to only deny inbound traffic, rather than denying both flows.

    I checked BandwidthD and I noticed the functionality changed.  As I reported previously, the index.html (daily) page didn't work.  Now it's working as expected. Whats odd is the three other indexes (weekly, monthly, and yearly) all result in a message that there's nothing to graph - even though Bandwidthd has been running for days.  I will continue to experiment further and report back.

    If it helps any, pfSense was a new installation about two weeks ago.

    Version:

    2.2.5-RELEASE (amd64)
    built on Wed Nov 04 15:49:37 CST 2015
    FreeBSD 10.1-RELEASE-p24

    CPU Type:

    Intel(R) Atom(TM) CPU C2338 @ 1.74GHz
    Current: 1225 MHz, Max: 2100 MHz
    2 CPUs: 1 package(s) x 2 core(s)

    Packages installed:

    arpwatch
    bandwidthd
    darkstat
    pfBlockerNG

    I removed all packages and re-installed bandwidthd.  I'll give it a couple of hours to let bandwidthd populate the graphs.  Update (more than 18 hours later): All graphs are working as expected.

    The dashboard currently shows the following services running:

    pinger
    bandwidthd
    dhcpd
    miniupnpd
    ntpd
    sushi
    unbound


  • Moderator

    @BasketCase:

    I'm going to uninstall pfBlockerNG to see if this fixes the issue.

    I used pfBlockerNG to block both incoming and outgoing traffic to countries I do not normally do traffic with.  When some strange issues came up, I noticed some of the games the kids play on go to the country that I thought I didn't even need to reach.  I changed the pfBlockerNG functionality to only deny inbound traffic, rather than denying both flows.

    Hi,

    I don't expect there to be any conflict between BandwidthD and pfBlockerNG.

    As for you comment about Blocking, please see the following links for some additional details.

    https://forum.pfsense.org/index.php?topic=86212.msg548324#msg548324
    https://forum.pfsense.org/index.php?topic=86212.msg553921#msg553921
    https://forum.pfsense.org/index.php?topic=102071.0


Log in to reply