Unable to install vnstat2
-
I have updated the package and it has been merged and pulled into the github master but the 1.5.1-updated file hasn't been uploaded yet to files.pfsense.org. The old package was broken as well mind you. I have reached out to the devs again.
Need to update file on http://files.pfsense.org (vnstat2 php front end)
When this does get pushed will bring vnstat2 back up to speed? Does the graphing work correctly again?
-
I have updated the package and it has been merged and pulled into the github master but the 1.5.1-updated file hasn't been uploaded yet to files.pfsense.org. The old package was broken as well mind you. I have reached out to the devs again.
Need to update file on http://files.pfsense.org (vnstat2 php front end)
When this does get pushed will bring vnstat2 back up to speed? Does the graphing work correctly again?
Everything should work correctly! Still waiting on a dev to merge in the new pull request.
-
Thank you! Hopefully it will work again. It was a nice check against my provider's accounting and it gave more detail.
Hopefully a dev will publish it and we can be back in business.
-
Thank you! Hopefully it will work again. It was a nice check against my provider's accounting and it gave more detail.
Hopefully a dev will publish it and we can be back in business.
Yes. It has been the weekend after all.
-
bump.. waiting for update to bring this package back to life…
-
Yup, still not working…
Additional files... vnstat_php_frontend-1.5.1-updated.tar.gz failed. -
Shameless bump.
Still not working…. -
I am also waiting for this to be working. Hopefully soon.
-
based on the other active thread it's not the app developers fault, he's waiting on the pfsense devs to merge his changes into the code repo..
-
We know. I am thankful that the developer fixed the package. Just bumping so a dev might see it and know we are all waiting also..
-
today I did run into the same issue …
-
Waiting for the code to be accepted into the repo as well…
-
So updated to 2.1.1 and now since can not install the vnstat2 package I am without vnstat2..
-
So updated to 2.1.1 and now since can not install the vnstat2 package I am without vnstat2..
same here bud…. there is a push to fix it but waiting on the dev's to approve it.. week waiting for a few weeks...
-
It is like pulling teeth around here to get this second pull merged since they merged my original and failed to update an archive. It has been 24 days since the 2nd pull request was made and not a single person has commented/communicated with me about any problems. They want me to sign a Contributor license agreement before any code is merged. Yet they broke the package completely by merging and not reading. They have failed to send me said license to sign.
I don't know how this kind attitude is supposed to encourage contributors.
-
have you emailed anyone - or you just waiting around?
-
I gave up waiting for them to update the front end to this package and just manually installed the vnstat2 pbi from the pfSense repo and then grabbed the php front end from http://www.sqweek.com/sqweek/?p=1 .
There are some minor steps needed to get it working you have to manually initialized the databases for each interface and add them to the config.php in the frontend. I didn't bother adding a link to the pfSense GUI. The frontend should be placed in the /usr/local/www/vnstat2 and when they finally fix this it should over write the existing files or you can choose to delete them before installing from the pfSense package manager. Then you can simply navigate to https://yourrouter/vnstat2 and you will have the vnstat interface.
-
have you emailed anyone - or you just waiting around?
Mailing list
Github
PM
Emails - jim, jim, cmb, coreteamLast I got was from jim at netgate saying he should be able to get me the license agreement to sign last weekend.
-
We have a contributor agreement up now.
https://www.pfsense.org/ESF_Individual_Contributor_License_Agreement.pdfSorry this has delayed things, just one of those things we have to do to ensure the legal status of the project.
-
@cmb:
We have a contributor agreement up now.
https://www.pfsense.org/ESF_Individual_Contributor_License_Agreement.pdfSorry this has delayed things, just one of those things we have to do to ensure the legal status of the project.
Signed and sent back.
Thanks
