Jump to content

dorgan

Community Developer
  • Posts

    351
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by dorgan

  1. Just now, CHBMB said:

    Other thing, did you remember to put stats.page in your source as suggested by Squid?

    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.

  2. 7 minutes ago, Squid said:

    Actually I have a completely different thought on this whole thing.

    Why not store it in ram instead. At array start copy it from flash to ram. At array stop copy it from ram to flash.

    That way everything survives a reboot if so desired

    No need to worry about strange paths, and there is no requirement that the appdata path is even valid

    Sent from my LG-D852 using Tapatalk
     

    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.

  3. Just now, CHBMB said:

    Actually you must be somewhere as now I'm getting two folders created on plugin install. 

     

    /mnt/user/appdata/....

    and /mnt/disks/virtualisation/appdatanetworkstats/

     

    So there's still a trailing slash missing.

    Yeah i have some sloppiness, cleaning that up now.

  4. Nice work, just installed this and it's cool.  I got a couple of suggestions though.
     
    1.  Probably need to make it clearer that a prerequisite is having Dynamix System Statistics installed, or perhaps install it as part of your own install routine.
    2.  I don't use /mnt/user/appdata/ on my array.  Instead I use a SSD mounted via unassigned devices, so by installing your plugin I've now got an appdata share on my array of which the only subfolder is vnstat, so I think this should be either configurable by the user, or even grab their current appdata location with something like this.
    cat /boot/config/docker.cfg | grep DOCKER_APP_CONFIG_PATH | cut -d'"' -f 2

     


    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?
  5. Allows to start / stop now, but it's not populating the page with anything other than 2 "broken pictures".  (let it sit for awhile).  the appdata does have *something* in the various interfaces (docker, etc) there. Beyond that, you might want to consider silencing this from being logged:

    Oct  7 18:02:10 ServerA vnstatd[25705]: Traffic rate for "vnet1" higher than set maximum 10 Mbit (30->42, r0 t117), syncing.

    With a line logged every 30seconds, the log will fairly quickly fill up.

     

    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.

  6. 4 hours ago, Wayne66 said:

    I have the 9/29/2018 version running and then did the 2018.10.06c update. Not the vnstat is no longer running. 

     

    I did go to the plugin settings and tried to click "Start". No luck.

    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.

  7. I have the 9/29/2018 version running and then did the 2018.10.06c update. Not the vnstat is no longer running. 
     
    I did go to the plugin settings and tried to click "Start". No luck.

    I think it’s because of the hard coded path. I’ll get a release out in the next day or so.
  8. If you must store within appdata, then your best bet would be the default appdata location that can be found within /boot/config/docker.cfg


    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.
  9. [mention=78375]dorgan[/mention]I just uninstalled, did not restart server and installed the new version. It's not working for me yet. I have to enable the vnstat again. I went to the terminal and it looks like there's a new one? I Don't know
    image.png.a101e484f7c53614279bd495b2808ffb.png

    Try the manual copy, let me know if that works. Very odd
  10. 4 minutes ago, dukiethecorgi said:

    manually copied from from /usr/local/emhttp/plugins/networkstats/vnstat.conf to /etc/vnstat.conf and it started working. (the b version)

     

    then saw the update to c version and still working

     

    Thanks!

    Yup should be rock solid now. ::knock on wood::

×
×
  • Create New...