| Hey Dominic,
I'd love to roll the patches in. Unfortunately, they don't apply to trunk, and it'd be a fair amount of work to get them into shape to apply to trunk (it's mainly whitespace differences best I can tell). If someone was able to port it, though, I'd be more than happy to see them applied.
Cheers, Aaron On Mar 27, 2013, at 9:20 AM, Dominic Hamon <> wrote: Hi Aaron Is there any chance that these can be rolled in to trunk? Thanks
- dominic
On Mar 27, 2013 4:57 AM, "Aaron Brown" <> wrote:
Hi Daniel,
As Alan noted, NDT currently only works with web100, and not web10g. However, Richard Sanger has produced a set of patches for using NDT with web10g. I've cc'd Richard who may know the current state of the patches (I've attached the most recent copies I know of), and which version of NDT they apply to.
Cheers,
Aaron
On Mar 26, 2013, at 4:47 PM, Daniel A. Ramaley <> wrote:
> Hello. I'm trying to get NDT working on Debian Wheezy. When i run the
> tests, they seem to start but then nothing else is displayed:
>
>
>
> TCP/Web100 Network Diagnostic tool v3.6.5
> Click START to start the test
>
> ** Starting test 1 of 1 **
> Connection to 'ndt01.drake.edu' [ndt01.drake.edu/10.11.1.5] to run test
> Connected to: ndt01.drake.edu-- Using IPv4 address
>
>
>
> If i run ndtd with "-dddd", this is the output i get from it:
>
>
>
> ANL/Internet2 NDT ver 3.6.5
> Variables file = /usr/local/ndt/web100_variables
> log file = /var/log/web100srv.log
> Admin file = /usr/local/ndt/admin.html
> Debug level set to 4
> server ready on port 3001
> web100_init() read 69 variables from file
> Signal 17 received by process 3822
> successfully locked '/tmp/view.string' for updating
> sending '0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,' to tmp file
> Generated iflist with device=eth0 and if_speed=3
> nothing in queue
> Timer not running, waiting for new connection
> New connection received, waiting for accept() to complete
> New connection received from 0x925280 [10.11.1.18] sockfd=5.
> Child thinks pipe() returned fd0=6, fd1=7 for pid=0
> web100_attach: could not parse /proc/web100/header
> Signal 17 received by process 3822
> Client connect received from :IP 10.11.1.18 to some server on socket 5
> initialize_tests returned old/new client = 1, test_suite = 1 8 2 4 32
> Line just before ChldRdy: label, did't get here via the goto statement!
> ___-------______ client process is ready for testing!
> Telling client 3826 testing will begin now
> Signal 13 received by process 3822
> Dispatch multi-client failed because 'Broken pipe'
> Queue pointer=3826, testing=1, waiting=1, mclients=0, zombie_check=0
> Processing SIGCHLD signal for active web100srv process [0], sig17=1
> wait3() returned status=256 for PID=3826
> wexitstatus = '1'
> Main test process 3826 terminated, remove from queue
> Attempting to clean up child 3826, head pid = 3826
> Removing Child from head, decremented waiting/mclients 0/0
> Timer not running, waiting for new connection
>
>
>
> As for how i set this up, Debian uses a 3.2.x kernel, so i got the
> kernel patch from web10g.org instead of from www.web100.org. After
> installing the patched kernel i installed both the newer Web10g and
> older Web100 userlands. Then i installed NDT. I can provide detailed
> steps on exactly what commands i ran, but i suspect the problem is with
> the kernel patch since the NDT debug output mentions it could not parse
> /proc/web100/header. How can i get the /proc/web100 directory to show up
> with the newer Web10g patches? The Web100 patches don't seem to be
> available for newer kernels, and the Web100 download page even
> specifically says to download the Web10g patch instead. What do i need
> to do differently to make this work?
>
> Thanks in advance for any enlightenment.
> __
> Daniel A. Ramaley
> Network Engineer 2
>
> Dial Center 112, Drake University
> 2407 Carpenter Ave / Des Moines IA 50311 USA
> Tel: +1 515 271-4540
> Fax: +1 515 271-1938
> E-mail:
>
|
