Bandwidthd: Difference between revisions
From MediaWiki
Jump to navigationJump to search
| Line 9: | Line 9: | ||
PeteHoffswell has seen that running bandwidthd in it's default network of 0.0.0.0 can lead to a | PeteHoffswell has seen that running bandwidthd in it's default network of 0.0.0.0 can lead to a | ||
<div class="screen">bandwidthd IP_NUM is too low, dropping ip...</div> | <div class="screen">bandwidthd IP_NUM is too low, dropping ip... | ||
kernel: Out of memory: Killed process 9183 (bandwidthd)</div> | |||
followed by memory overflows and the killing of the bandwidthd process. | followed by memory overflows and the killing of the bandwidthd process. | ||
To fix, simply define the local networks with the -s directive in the NST bandwidthd page. | To fix, simply define the local networks with the -s directive in the NST bandwidthd page. | ||
Revision as of 15:13, 24 April 2007
Bandwidthd is a bandwidth trending tool. See http://bandwidthd.sf.net
Troubleshooting
bandwidthd crashing
If you see that bandwidthd will not stay up, you should check your /var/log/messages log for any warnings.
PeteHoffswell has seen that running bandwidthd in it's default network of 0.0.0.0 can lead to a
bandwidthd IP_NUM is too low, dropping ip...
kernel: Out of memory: Killed process 9183 (bandwidthd)
followed by memory overflows and the killing of the bandwidthd process.
To fix, simply define the local networks with the -s directive in the NST bandwidthd page.
