Bandwidthd - Revision history

Petehoffswell: /* bandwidthd crashing */

2007-04-24T20:22:23Z

bandwidthd crashing

← Older revision		Revision as of 16:22, 24 April 2007
Line 18:		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...~~<br>~~		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.

Petehoffswell: /* Overview */

2007-04-24T20:22:06Z

Overview

← Older revision		Revision as of 16:22, 24 April 2007
Line 2:		Line 2:
	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.		You can gain access to the bandwidthd management page by selecting

			NSTWUI > Networking > Monitors > bandwidthd.

	Choose an interface to monitor, and start the process.		Choose an interface to monitor, and start the process.

Petehoffswell at 20:19, 24 April 2007

2007-04-24T20:19:07Z

← Older revision		Revision as of 16:19, 24 April 2007
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 ==

Petehoffswell: /* bandwidthd crashing */

2007-04-24T20:16:58Z

bandwidthd crashing

← Older revision		Revision as of 16:16, 24 April 2007
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 class="screen">bandwidthd IP_NUM is too low, dropping ip...<br>
	kernel: Out of memory: Killed process 9183 (bandwidthd)</div>		kernel: Out of memory: Killed process 9183 (bandwidthd)</div>

Petehoffswell: /* bandwidthd crashing */

2007-04-24T20:13:49Z

bandwidthd crashing

← Older revision		Revision as of 16:13, 24 April 2007
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.

Petehoffswell: /* bandwidthd crashing */

2007-04-24T20:12:17Z

bandwidthd crashing

← Older revision		Revision as of 16:12, 24 April 2007
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

	bandwidthd IP_NUM is too low, dropping ip...		<div class="screen">bandwidthd IP_NUM is too low, dropping ip...</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.

Petehoffswell: /* bandwidthd crashing */

2007-04-24T20:09:45Z

bandwidthd crashing

← Older revision		Revision as of 16:09, 24 April 2007
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

	~~{{{~~bandwidthd IP_NUM is too low, dropping ip...~~}}}~~		bandwidthd IP_NUM is too low, dropping ip...

	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.

Petehoffswell: New page: 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 /...

2007-04-24T20:07:36Z

New page: 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 /...

New page

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...}}}

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.