dorgan

Yes, what I am asking though is your system using eth0, or do you utilize a non standard port. Right now I filter the list display so that it only displays interfaces that contain eth, bond or br

I'll try disabling Docker tonight, uninstall, restart and reinstall the plugin and see what happens.

Do you not use ethX, brX or bondX? Right now that’s the only interfaces it will show in the list to select.

Ok yeah it’s very possible the issues found over the weekend resolved that. But again, none of the people I worked with over the weekend had these issues.

What version of network stats were you running? We discovered some patching issues yesterday and those have since been corrected.

What version of unRaid are these people running? Just curious as I’ve been working with numerous people over the weekend and no one reported this...

I'll take care of that tomorrow, need to get the kids to bed and get everyone settled down for the night. Thanks for the help.

What are others using?

@CHBMB please try now. Things should now get created in the right place.

No need to copy it to memory if the filesystem gets created properly. I've release version 2018.10.07d which corrects the pathing issues. Sometimes i was using ${DOCKER_APP_CONFIG_PATH}/networkstats and other times i was using ${DOCKER_APP_CONFIG_PATH}/vnstat. This has now been normalized.

hmmm my DOCKER_APP_CONFIG_PATH has a slash at the end yours doesn't. I need to account for that.

Yeah i have some sloppiness, cleaning that up now.

look at source /boot/config/docker.cfg that will bring them in as variables

There will be another version coming as I introduced an error in the vnstat.conf file and now I need to correct it

I've found a couple issues. Pushing a new release shortly that will fix all of this.

OK founs where it was creating the incorrect path.

What is your DOCKER_APP_CONFIG_PATH set to?

does vnstat exist inside appdata, or is putting everything inside of appdatavnstat?

I am using DOCKER_APP_CONFIG_PATH in the versions I released today. As for the other plugin, I didn’t make a requirement or anything. What happens when that’s not installed?

@Squidactually it seems the MaxBandwidth setting was the possible cause of no data being populated. Version 2018.10.07a has been released and adjusts this setting.

Takes time to populate, also go into settings and select the interfaces you want to track. I’ll work on adding some messaging and a cleaner response for that initial time. I’ll look into the log settings and see what can be done there as well.

Version 2018.10.07 has been released and will use docker appdata path. Please let me know if this gets you back into a working condition.

I think it’s because of the hard coded path. I’ll get a release out in the next day or so.

Definitely will update to this. What’s being stored besides the cfg is the actual data for vnstat, as keeping it in the default location was causing it to be deleted on reboot.

I will work on making this adjustable for the next release.