ndt-users list created

[Tom Throckmorton <>]

Hello Peter - comments inline below.

On 11/17/10 1:54 PM, Peter Charbonneau wrote:
> Good afternoon,
> 
>   I am new to NDT and new to the list.
> 
>   I installed the I2 Performance Toolkit on two different sets of Dell
> hardware - a 1550 pizza box and an OptiPlex 745 with 8G of memory.

Which installation method did you follow - LiveCD or net install?

>   When I run the NDT tests, I see two types of errors -- protocol errors
> and server busy errors.
> 
>   The server is running v3.4.4a of web100srv; I got frustrated with the
> java applet/client, so I downloaded, configured, and made v3.4.4a ndt
> from source.
> 
>   Here are console messages from both the server and client showing the
> interaction.  It looks like one of the issues MAY be not being able to
> stat /proc/web100/header, but I haven't been able to find the server
> source to follow that logic.

Yes, it does appear that way, based in particular on this error:

> web100_attach: could not parse /proc/web100/header

What do the following on your installed toolkit instances return?

  uname -a
  head -1 /proc/web100/header

-tt

>   Any help pointing me in the right direction would be greatly appreciated.
> 
>   I would prefer to use the I2Performance ToolKit - strictly for ease of
> use of the java applet for the clients, but, I'll take what I can get.
> 
> ****************************************************************
> Server:
> 
> [root@i2perf2
>  init.d]# web100srv -ddddd -p3001
> ANL/Internet2 NDT ver 3.4.4a
>     Variables file = /usr/ndt/web100_variables
>     log file = /usr/ndt/web100srv.log
>     Debug level set to 5
> server ready on port 3001
> web100_init() read 69 variables from file
> nothing in queue
> Timer not running, waiting for new connection
> New connection received, waiting for accept() to complete
> New connection received from [137.165.224.49].
> Child thinks pipe() returned fd0=5, fd1=6 for pid=0
> web100_attach: could not parse /proc/web100/header
> Signal 17 received by process 21874
> Parent process spawned child = 21876
> Parent thinks pipe() returned fd0=5, fd1=6
> Incrementing waiting variable now = 1
> Telling client 21876 testing will begin now
>>>> send_msg: type=1, len=1
> Signal 13 received by process 21874
> Queue pointer = 21876, testing = 1, waiting = 1
> Received SIGCHLD signal for active web100srv process [21874]
> wait3() returned 256 for PID=21876
> wexitstatus = '1'
> Waiting for new connection, timer running
> now = 1290017016 Process started at 1290017013, run time = 3
> Timer expired while waiting for a new connection
> Queue pointer = 21876, testing = 1, waiting = 1
> Waiting for new connection, timer running
> 
> ****************************************************************
> Client:
> 
> porthos2:~/Downloads/ndt-3.4.4a/src pcharbon2-13:01:58$ ./web100clt
> -ddddd -n 137.165.224.118 -p3001
> Testing network path for configuration and performance problems  -- 
> Using IPv4 address
> Requesting test suite:
>  > Middlebox test
>  > Simple firewall test
>  > C2S throughput test
>  > S2C throughput test
>>>> send_msg: type=2, len=1
> Protocol error!
> porthos2:~/Downloads/ndt-3.4.4a/src pcharbon2-13:03:05$ ./web100clt -v
> ANL/Internet2 NDT version 3.4.4a (client)
> 
> ****************************************************************
> 
> 
> 
> ****************************************************************
> 
> 
> 
> PeteC
> 
> 
> Peter Charbonneau
> Sr. Network and Systems Administrator
> Williams College
> (413) 597-3408 (office)
> (413) 822-2922 (cell)
> OIT will NEVER ask for your password!
> 
> 


-- 
Tom Throckmorton
MCNC
919.248.1448

"Connecting North Carolina's future today"