This used to work, dunno what cjaged?
TypeError
result.stdout is undefined
I have removed, forcing, and re-installed, same error.
Anyone experience this before?
Not a lot of info here. Any logs?
What does logread -e vnstat return?
Also try logread -e procd
2 Likes
Thank you for your reply.
Wow, nothing in those logs.
Checking to see if it is even running via, ps w|grep vnstat
2867 root 2612 S /usr/sbin/vnstatd --nodaemon --noadd --noexit
1 Like
root@OpenWrt:~# service vnstat restart
root@OpenWrt:~# logread -e vnstat
Tue Dec 5 15:33:44 2023 daemon.info vnstatd[2867]: Info: SIGTERM received, exiting.
Tue Dec 5 15:33:44 2023 daemon.info vnstatd[16443]: Info: vnStat daemon 2.11 (pid:16443 uid:0 gid:0 64-bit, SQLite 3.41.2)
Tue Dec 5 15:33:44 2023 daemon.info vnstatd[16443]: Info: Data retention: 48 5MinuteHours, 4 HourlyDays, 62 DailyDays, 25 MonthlyMonths, -1 YearlyYears, 20 TopDayEntries
Both replies are normal.
Where did this come from.
TypeError
result.stdout is undefined
A type error happens for example when an operation receives a different type of data than it expected.
Are you seeing data in vnstat gui?
It looks like I introduced a bug with this recent change, so the config page doesn't work anymore when the database is empty.
I'll work on a fix later!
2 Likes
Wow, thank you!
BTW, I am running the vnstat logs, and the other logged data of the collectd logs, on eMMC 'media'.
Does this activity actually 'wear out' the eMMC?
I created a pull request with a fix:
2 Likes
They tick a nice bunch of boxes, but since they tend to use NAND . . . probably.