vnStat [Release] vnStat-on-Merlin - UI, CLI and email - data use and data limit monitoring - R1 and R2

[kfahoo]

ok, just noticed that with your script is launched with noadd parameter, I'll read man and test

 

[elorimer]

I think I have resolved my issue with vnstat stopping unexpectedly. It coincides with a scheduled reboot, and at that time dn-vnstat starts but vnstat itself doesn't. I couldn't find out where in the starting sequence precisely it failed, but the S33 starting code is not necessary for me after the initial installation, I think, so I hard-coded the choice of jffs or usb storage location and removed the S32 tests. Now it starts on a reboot.

I seem to recall other instances where a lot of Sxx code created a race condition or some other starting issue. Not sure why, as other add-ons seems to run ok even with a lot; Scribe has a lot offloaded to another file that gets called, for example.

 

[jb68]

Hi,

Is there a way to transfer the stats across to a newer model of router ? I have it currently stored in jffs.

Please advise thanks

 

[Zim]

I think I have resolved my issue with vnstat stopping unexpectedly. It coincides with a scheduled reboot, and at that time dn-vnstat starts but vnstat itself doesn't. I couldn't find out where in the starting sequence precisely it failed, but the S33 starting code is not necessary for me after the initial installation, I think, so I hard-coded the choice of jffs or usb storage location and removed the S32 tests. Now it starts on a reboot.

I seem to recall other instances where a lot of Sxx code created a race condition or some other starting issue. Not sure why, as other add-ons seems to run ok even with a lot; Scribe has a lot offloaded to another file that gets called, for example.

Hey @elorimer I'm having a similar issue with the stats. I've checked and it appears dn-vnstat runs after reboot, but vnstat is "dead" based on running this command:

/opt/etc/init.d/S33vnstat check

After starting vnstat using this command:

/opt/etc/init.d/S33vnstat start

the stats are updating just fine.

Can you please post what you modified in /opt/etc/init.d/s33vnstat file?

Thanks.

 

[dev_null]

Hi,

Is there a way to transfer the stats across to a newer model of router ? I have it currently stored in jffs.

Please advise thanks

Please see https://www.snbforums.com/goto/post?id=817919

Note: there is no guarantee that it will work, this is an unsupported hack. I have, however, successfully done so at least twice in a test environment.

 

[dev_null]

Hey @elorimer I'm having a similar issue with the stats. I've checked and it appears dn-vnstat runs after reboot, but vnstat is "dead" based on running this command:

/opt/etc/init.d/S33vnstat check

After starting vnstat using this command:

/opt/etc/init.d/S33vnstat start

the stats are updating just fine.

Can you please post what you modified in /opt/etc/init.d/s33vnstat file?

Thanks.

Please also see: https://www.snbforums.com/goto/post?id=910373 and https://www.snbforums.com/goto/post?id=910422 (recent posts on this issue) and https://www.snbforums.com/goto/post?id=892704.

It would be helpful for you to add your configuration (router, firmware version, scripts) to your signature and describe your topology (setup).

 

[Zim]

Please also see: https://www.snbforums.com/goto/post?id=910373 and https://www.snbforums.com/goto/post?id=910422 (recent posts on this issue) and https://www.snbforums.com/goto/post?id=892704.

It would be helpful for you to add your configuration (router, firmware version, scripts) to your signature and describe your topology (setup).

@dev_null thanks! I've gone through those threads but no luck.

My setup:
Router: AXE16K
FW: 3004.388.7
Scripts: Skynet, Unbound, AdGuard, dn-vnstat, spdMerlin, scMerlin

 

[dev_null]

For those reading this thread instead of the other, please see this: https://www.snbforums.com/goto/post?id=910841

I've created a script (also posted in post #3 on page 1 of this thread) that will check the status of the S33vnstat daemon and if there are other than isolated reports of the daemon crashing/not starting, I may add this check to the dn-vnstat script.

I acknowledge it's treating the symptom not the disease, and will continue to try to identify why the daemon stops in a small number of cases.