So the solution to this would to update the Debian package to use vnstat
2.1 (the update is detected by https://tracker.debian.org/pkg/vnstat). It
would be nice to have this in Debian before the buster freeze, but
https://release.debian.org/buster/freeze_policy.html states that
> Starting
On Sat, 9 Feb 2019 20:40:56 +
nodiscc wrote:
> We had a discussion on IRC on how to best fix this. At first there was an
> attempt to use DaemonUser "vnstat" DaemonGroup "vnstat" and removing
> User=vnstat from the systemd unit file. But even then you have to systemctl
> restart vnstat for
Hi, this is a reply to bug 749019 and bug 881811, which stem from the same
problem in the vnstat Debian package:
- /lib/systemd/system/vnstat.service defines User=vnstat as the user to
run run vnstat under
- The recommended way to start tracking a network interface and create its
database file
Dear Maintainer,
I installed vnstat on a fresh Debian 9 and ran into the above bug. The
solution outlined by the original submitter worked for me as well.
Regards
Prashant L Rao
tags -1 moreinfo unreproducible
Hi,
please check if this issue still exists in version 1.17.
The permissions for the directory /var/lib/vnstat should be set correctly now.
Regards,
Christian Göttsche
I think I still get this, at least with ubuntu (FWIW)
ref: http://askubuntu.com/questions/500663/vnstat-not-updating/502667#502667
On 2014-05-23 03:57, Adam Brenner wrote:
Package: vnstati
Version: 1.11-2
Severity: important
Howdy,
Upon installing vnstat using the following command:
$ apt-get install vnstati
the vnstat daemon is able to create its own database for each
interface.
However, when trying to update its
Package: vnstati
Version: 1.11-2
Severity: important
Howdy,
Upon installing vnstat using the following command:
$ apt-get install vnstati
the vnstat daemon is able to create its own database for each interface.
However, when trying to update its own database, it attempts to create
a backup
8 matches
Mail list logo
