Barney
1
I'm running OpenWrt SNAPSHOT r14740-0b31713c85 an a NanoPi R1.
Since a few weeks I sporadically get the following error messages from nlbwmon:
logread | grep 'daemon.err nlbwmon'
Tue Jun 22 09:16:13 2021 daemon.err nlbwmon[2485]: Netlink receive failure: Out of memory
Tue Jun 22 09:16:13 2021 daemon.err nlbwmon[2485]: Unable to dump conntrack: No buffer space available
Tue Jun 22 09:26:14 2021 daemon.err nlbwmon[2485]: Netlink receive failure: Object busy
Tue Jun 22 09:26:14 2021 daemon.err nlbwmon[2485]: Unable to dump conntrack: I/O error
Tue Jun 22 09:26:44 2021 daemon.err nlbwmon[2485]: Netlink receive failure: Object busy
Tue Jun 22 09:26:44 2021 daemon.err nlbwmon[2485]: Unable to dump conntrack: I/O error
Tue Jun 22 09:28:15 2021 daemon.err nlbwmon[2485]: Netlink receive failure: Object busy
Tue Jun 22 09:28:15 2021 daemon.err nlbwmon[2485]: Unable to dump conntrack: I/O error
Tue Jun 22 09:30:15 2021 daemon.err nlbwmon[2485]: Netlink receive failure: Object busy
Tue Jun 22 09:30:15 2021 daemon.err nlbwmon[2485]: Unable to dump conntrack: I/O error
Curious the message about having No buffer space available.
free
total used free shared buff/cache available
Mem: 440532 67344 214364 13436 158824 323632
Swap: 327676 0 327676
free shows a lot of free memory.
- What's the meaning of these error messages?
- What's the reason for these error messages?
- How can I get rid of these error messages?
Any further information needed?
Something ate your RAM.
Same as above.
Find out what's eating the RAM.
jow
3
Try increasing the netlink socket buffers by setting option netlink_buffer_size
in /etc/config/nlbwmon. The default is 524288
Barney
4
I think, there is more than enough RAM available.
free
total used free shared buff/cache available
Mem: 440532 67344 214364 13436 158824 323632
Swap: 327676 0 327676
Yeah, after it already crashed, or before it starts to build up.
But jow might be on to something....
Barney
6
I did a search for 'nlbwmon netlink_buffer_size' and found the following thread:
The problem seems still unresolved.
I changed some params in /etc/config/nlbwmon. Will watch the further behaviour of nlbwmon and report about success or failure.
These are my current relevant options:
option netlink_buffer_size '10485760'|
option refresh_interval '30s'|
option database_interval '1'|
option database_limit '0'|
option database_generations '12'|
option commit_interval '60s'|
1 Like
Barney
7
nlbwmon did not crash, it just logged the error messages.
So far no further error message. I'll continue watching.
Barney
10
So far no further error messages since Sat Jul 3 10:38:57 2021. I consider my problem solved.
Thanks to everybody who replied.
system
Closed
11
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.