Bandwidthd: Difference between revisions

From MediaWiki
Jump to navigationJump to search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Overview =
Bandwidthd is a bandwidth trending tool.  See http://bandwidthd.sf.net
Bandwidthd is a bandwidth trending tool.  See http://bandwidthd.sf.net
You can gain access to the bandwidthd management page by selecting
NSTWUI > Networking > Monitors > bandwidthd.
Choose an interface to monitor, and start the process.


= Troubleshooting =
= Troubleshooting =
== bandwidthd will not start ==


== bandwidthd crashing ==
== bandwidthd crashing ==
Line 9: Line 18:
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...
bandwidthd IP_NUM is too low, dropping ip...
kernel: Out of memory: Killed process 9183 (bandwidthd)</div>
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.

Latest revision as of 16:22, 24 April 2007

Overview

Bandwidthd is a bandwidth trending tool. See http://bandwidthd.sf.net

You can gain access to the bandwidthd management page by selecting

NSTWUI > Networking > Monitors > bandwidthd.

Choose an interface to monitor, and start the process.

Troubleshooting

bandwidthd will not start

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.