ndt-users list created

[Rob Brown <>]

Yeah, I thought disabling the client side firewall (windows box) would have been enough, but there must be something in the middle preventing access, because it worked against a different (public) server.

I ran the web100clt locally on the server machine and it worked fine.

I'll have to ping the network engineers on this.

Thanks.

On Wed, May 23, 2012 at 12:48 PM, Kavitha Kumar <> wrote:

Hi Rob,

   The return code -100 is indicative of the server timing out while waiting for client to connect to its ephemeral port. Your client side message of "Unable to create connect socket." indicates the same too.

There are probably some firewalls ?

Kavitha

 

On May 23, 2012, at 2:41 PM, Rob Brown wrote:

Thanks, that was helpful.

I enabled max debugging and here is a snippet of the failed s2c part of the log:

[server]

Starting s2c throughput test

 <-- 3671 - S2C throughput test -->

Send buffer initialized to 87380, Receive buffer initialized to 87380

  -- s2c 3671 port: 3003

3671 waiting for data on testOptions->s2csockfd

Finished reading pkt-pair data from network, process 3680 should terminate now

pcap_loop exited recvfrom: Bad file descriptor

Pkt-Pair data collection ended, waiting for signal to terminate process

Signal 17 received by process 3671

Timer expired while waiting for a new connection

Queue pointer=3671, testing=1, waiting=1, mclients=0, zombie_check=0

Waiting for new connection, timer running

Timer expired while waiting for a new connection

Queue pointer=3671, testing=1, waiting=1, mclients=0, zombie_check=0

Waiting for new connection, timer running

S2C test failed with rc=-100

S2C throughput test FAILED!, rc=-100

Child 3671 returned non-zero (-100) from run_test() results some test failed!

[client]

 <-- S2C throughput test -->

  -- port: 3003

Send buffer initialized to 65535, Receive buffer initialized to 65535

Unable to create connect socket.

Connect() for Server to Client failed

S2C throughput test FAILED!

Protocol error - expected results!  got ' 1', msgtype=2

On Tue, May 22, 2012 at 5:08 PM, Scott Bertilson <> wrote:

Might be worthwhile to try some number of "-d"s to see if you can get some useful hints (you can set the startup parameters in /etc/sysconfig/ndt and then do /etc/init.d/ndt restart):

[root@perfsonar-10g store]# web100srv --help

ANL/Internet2 NDT version 3.6.4 (server)


 Basic options:

  -a, --adminview        - generate administrator view html page
  -d, --debug            - print additional diagnostic messages
                           Note: add multiple d's (-ddd) for more details
  -h, --help             - print help message (this message)
  -m, --multiple         - select single or multi-test mode
  -o, --old              - use old Duplex Mismatch heuristic
  -q, --disable-queue    - disable FIFO queuing of client requests
  -r, --record           - record client to server Web100 variables
  -s, --syslog           - use the syslog() to log some information
  -t, --tcpdump          - write tcpdump formatted file to disk
  -v, --version          - print version number
  -x, --max_clients      - maximum numbers of clients permited in FIFO queue (default=50)
  -z, --gzip         - disable compression of tcptrace, snaplog, and cputime files

 Configuration:

  -c, --config #filename - specify the name of the file with configuration
  -b, --buffer #size     - set TCP send/recv buffers to user value
  -f, --file variable_FN - specify alternate 'web100_variables' file
  -i, --interface device - specify network interface (libpcap device)
  -l, --log Log_FN       - specify alternate 'web100srv.log' file
  -p, --port #port       - specify primary port number (default 3001)
  --midport #port        - specify Middlebox test port number (default 3003)
  --c2sport #port        - specify C2S throughput test port number (default 3002)
  --s2cport #port        - specify S2C throughput test port number (default 3003)
  -T, --refresh #time    - specify the refresh time of the admin page
  --mrange #range        - set the port range used in multi-test mode
                           Note: this enables multi-test mode
  -A, --adminfile #FN    - specify atlernate filename for Admin web page
                           Note: this doesn't enable 'adminview'
  -L, --log_dir DIR      - specify the base directory for snaplog and tcpdump files
                           (default /usr/ndt/serverdata)
  -S, --logfacility #F   - specify syslog facility name
                           Note: this doesn't enable 'syslog'

 Experimental code:

  --avoidsndblockup      - enable code to avoid send buffers blocking in the S2C test
  --snaplog              - enable the snaplog writing
  --snapdelay #msec      - specify the delay in the snaplog thread (default 5 msec)
                           Note: this doesn't enable 'snaplog'
  --cwnddecrease         - enable analyzing of the cwnd changes during the S2C test
                           Note: this automatically enables 'snaplog'
  --cputime              - enable the cputime writing
  -y, --limit #limit     - enable the throughput limiting code

 Database support:

  --enableDBlogging      - enable the test results logging to the database
  --dbDSN #dsn           - specify the DSN to use (this doesn't enable DBlogging)
  --dbUID #uid           - specify the UID to use (this doesn't enable DBlogging)
  --dbPWD #pwd           - specify the PWD to use (this doesn't enable DBlogging)

 IP family:

  -4, --ipv4             - use IPv4 addresses only
  -6, --ipv6             - use IPv6 addresses only

On Tue, May 22, 2012 at 6:47 PM, Scott Bertilson <> wrote:

http://psps.perfsonar.net/toolkit/FAQs.html#Q6

On Tue, May 22, 2012 at 6:40 PM, <> wrote:

Hi,
I am new to NDT, so bear with me. I have set up a server running the
netinstall of pS-Performance Toolkit, which includes NDT. I am trying the NDT
test but it is failing with the following message on the client:

Checking for middleboxes......Done.
Checking for firewalls......Done.
running 10s outbound test (client-to-server[C2S])......434.0kb/s
running 10s inbound test (server-to-client[S2C])......Server Failed while
receiving data
S2C throughput test FAILED!

I am testing across a VPN with pvt IPs and am fairly sure there are no
firewalls blocking anything, but it would be helpful to know what ports it is
trying to connect on, etc.
When I ran the test against a different (publicly available) NDT server, the
S2C test runs fine, so I don't think it's anything on the client side.
Is there a way to enable additional debugging to see what is going wrong?
I don't see anything useful in /var/log/ndt/web100srv.log

--

Rob Brown | Sr Systems Engineer | Rhapsody International Inc.

1420 Fifth Ave, Suite 1500 | Seattle | WA | 98101

Office: (415) 934-2032

Mobile: (619) 846-2416

 
All the music you want. 10 bucks a month
Listen to over 14 million songs on your PC, iPhone®, iPod Touch®, BlackBerry®, Windows Phone 7 

 

®

 

  or Android™ 

More at www.rhapsody.com

PRIVILEGED & CONFIDENTIAL COMMUNICATION. This e-mail is intended only for the use of the persons to whom it is addressed, and may contain information that is privileged, confidential, or otherwise protected under applicable law. If you are not the intended recipient, or authorized by the recipient to read this, you are hereby notified that you are prohibited from using, copying, disseminating, or replying to this e-mail. 

--

Rob Brown | Sr Systems Engineer | Rhapsody International Inc.

1420 Fifth Ave, Suite 1500 | Seattle | WA | 98101

Office: (415) 934-2032

Mobile: (619) 846-2416

 
All the music you want. 10 bucks a month
Listen to over 14 million songs on your PC, iPhone®, iPod Touch®, BlackBerry®, Windows Phone 7 

 

®

 

  or Android™ 

More at www.rhapsody.com

PRIVILEGED & CONFIDENTIAL COMMUNICATION. This e-mail is intended only for the use of the persons to whom it is addressed, and may contain information that is privileged, confidential, or otherwise protected under applicable law. If you are not the intended recipient, or authorized by the recipient to read this, you are hereby notified that you are prohibited from using, copying, disseminating, or replying to this e-mail.