Well, you have already found the offending process name. You might check the documentation of vnstat and see how it works. For example in the INSTALL file provided along with the source code you see:
Code:
There are two way
for updating interface data, daemon and cron. It is suggested to use daemon
based updating because it generated less disk access and is more accurate
especially when monitoring interfaces that aren't always available. Select
ONLY ONE of these two:
1) daemon based updating
::::::::::::::::::::::::
Configure init scripts so that the following command is executed once
during system start:
vnstatd -d
The examples/init.d directory contains suitable init.d scripts for
some commonly used distributions. An alternative option is to just add
the command to an already existing script that gets executed during
startup. In many distributions /etc/rc.local can be used for that.
2) cron based updating
::::::::::::::::::::::
Copy the example cron file to /etc/cron.d
cp examples/vnstat.cron /etc/cron.d/vnstat
and edit the cron file if the default 5 minute update interval is too
long. See the vnStat man page 'restrictions' section for limitations
regarding fast interfaces and 32 bit interface traffic counters. Devices
like ppp0 also require vnStat enable and disable commands to be added
to suitable script file when cron based updating is used. Example scripts
can be found in the 'examples' directory.
Case two seems to be the issue here, anyway from the output of ps it looks like the software has not been properly installed, since the command:
Code:
/bin/bash /usr/sbin/vnstat.cron
does not make any sense. If you're not aware of who and why installed this software or if you simply don't need it anymore, you might totally remove it (provided you can find out the installation method). In that case, first check if by chance the vnstat daemon is running and switch it off. Hope this helps.
