-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No data" Issue on LEDE 17.01.04 #23
Comments
Thanks for the report. I am able to reproduce it as well. Will investigate |
Something to do with the socket file - trace reveals:
|
|
It's there somewhere
snip
|
|
Can you run |
Not sure what kind of answer you were expecting here, but yes, I can. I occasionally see epoll_pwait going past, and occasionally a flood of data rolls by. |
here's a 30-second output. |
And another when I did two page refreshes for http://..../cgi-bin/luci/admin/nlbw/display |
Could this be something to do with the inodes changing?
proc reports something different to what the socket file actually has. So perhaps the nlbwmon has run away... |
Curiously, after a reboot - I go to display, still "grey". Run |
Any residual logread messages? Is it the |
Yep:
|
Just not when |
I have noticed this problem for a while. Only thing I have found that helps is to delete the database and start fresh, after that it will run smoothly again for a few days... |
I had this. I ended up finding that restarting nlbwmon did the trick to get it behaving. AFAICT, it doesn't affect data capture, only display. Not sure if it's related, but I'm finding that the graphical display won't show old data. It works fine for current period, but when requesting old periods, it displays the current period instead. |
I had the same problem on openwrt cc(15.05),and I try it on openwrt 18.06 ,it works okay. |
I got it, the kernel config must be selected "CONFIG_NF_CONNTRACK_EVENTS". openwrt cc default no select it |
I seem to have the same problem on 18.06-rc1 on ipq8064. However i have CONFIG_NF_CONNTRACK_EVENTS=y in build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/linux-ipq806x/linux-4.14.50/.config |
I still get this issue intermittently. I am on OpenWrt 18.06.0 |
As reported by @systemcrash running |
I got this issue too after move the path database to usr/lib/nlbwmon Hope u have solution for next update |
I believe this issue has been addressed by ef3fa58. Please open a new issue if you still see this. |
The issue persists even after ef3fa58 |
Running for a few days and I get this in syslog when the GUI shows 'No data recorded yet.' and 'Force reload' for MAC data:
Wed Jan 17 15:17:55 2018 daemon.err nlbwmon[9277]: Unable to handle 'dump' command: Resource temporarily unavailable
Wed Jan 17 15:17:55 2018 daemon.err uhttpd[1293]: Error while processing command: No data available
Wed Jan 17 15:17:59 2018 daemon.err nlbwmon[9277]: Unable to handle 'dump' command: Resource temporarily unavailable
Wed Jan 17 15:17:59 2018 daemon.err uhttpd[1293]: Error while processing command: No data available
running under console completes fine:
./usr/sbin/nlbwmon dump
(lots of data)
Have relocated storage to /opt onto removable USB which is accessible and fine.
The text was updated successfully, but these errors were encountered: