Vnstat2 not working on nanobsd and alix
-
either vnstat or any other package, from the time it started giving problems it has never worked correctly on alix and later on i never bothered installing any more packages and so lately i didnt try any other package and this reinstall issue is froma very long time so i though over time it will get solved as lot of development work was going on but on the 8th jun snap it worked fine, atleast the reinstall after upgrade but the package never worked ever for me, didnt last more that a few mins and never after a reboot and the reason y i need this package is to keep track of data transfer rather than have all that data of RRD.
-
Made some changes to the package that should help with the vnstat database being saved on nanobsd.
-
yes i saw the change but the issue is still with the package manager, after upgrade, it doesn't sync the package and even clicking reinstall just shows deinstall and doesn't do anything yet so could u give me some commands to get it to reinstall properly from console etc till the package installer is fixed?
-
To install
/etc/rc.conf_mount_rw
pkg_add -r vnstat
rehash
/etc/rc.conf_mount_roIf there already is a vnstat installed use pkg_info to get the full name and pkg_delete -r to delete it
-
vnstat wasnt installed so i went to console and typed out the commands and it finished, so then i returned to the web GUI and the package didnt appear anywhere so i went back to package manager and clicked install and then again it downloaded and installed and worked for like a min or so then again loggin into the web GUI gave me the below stuff
Removing pacakge instructions…done.
Auxiliary files... done.
Package XML... done.
Configuration... done.
Downloading package configuration file... done.
Saving updated package information... done.
Downloading vnstat2 and its dependencies... done.
Checking for successful package installation... of vnstat-1.10_2 failed!Installation aborted.
then it shows under packages as installed but the menu doesnt appear nor manually typing out the link works and if i go abck to package manager and try to click reinstall, just shows the below stuff and thats it
Loading package instructions... Deinstall commands...
-
I think you need to reflash your card with the latest image.
I can install vnstat it on my test 2g nanobsd image installed in virtualbox. -
first time install is fine but it all dies out once u upgrade, try this out, once installed and working, upgrade with a newer snapshot and ull see it doesnt sync the package again but just keeps showing under installed packages and nor will it let u remove it or reinstall.
-
currently on the 3rd july snap, reset to factory and resetup from scratch on reboot, went to packages and clicked install and this happens
Downloading package configuration file… done.
Saving updated package information... done.
Downloading vnstat2 and its dependencies... done.
Checking for successful package installation... of vnstat-1.10_2 failed!Installation aborted.
but after this an entry comes in instaleld packages but actually its not installed at all
-
currently on the 13th july nanobsd snap and finally got the vnstat2 package to install and now atleast it works even after a reboot but one issue might be there is that suppose if i upgrade then the vnstat2 db is not stored in the config xml and there isnt any way to backup and restore it all using the gui so this would mean those traffic values would be lost of it upgrade so could there be a solution to this similar to how there is option to backup RRD stats?
-
any1 to tell me what files to backup and restore manually to keep the stats even on upgrades?
-
any1 to tell me what files to backup and restore manually to keep the stats even on upgrades?
Currently I don't know a way for those data to survive a nanobsd update. Alternatively would be to save your vnstat DB folder on your local pc with winscp (windows) or ctrl+l (ubuntu) sftp://root@your_pfsense_ip/usr/local/pkg/
-
Perry,
Have a look at the shutdown/startup code for the RRD graphs, you could probably do the same thing they do. At shutdown, they are tarred up and saved under /conf/ and at startup they are untarred and restored to the proper location.
