ndt-users - Re: NDT 3.6.5 on a 3.2.x kernel
Subject: ndt-users list created
List archive
- From: "Daniel A. Ramaley" <>
- To:
- Subject: Re: NDT 3.6.5 on a 3.2.x kernel
- Date: Mon, 8 Apr 2013 13:59:40 -0500
- Authentication-results: sfpop-ironport02.merit.edu; dkim=neutral (message not signed) header.i=none
- Organization: Drake University
I have NDT compiled and installed now, with the web10g patches. And it
gets a little further than it did before, but still is not working
correctly. Here's what is displayed in the web browser:
TCP/Web100 Network Diagnostic Tool v3.6.5.2
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
Checking for Middleboxes . . . . . . . . . . . . . . . . . .
Before doing any of the Web10g patches, it didn't display the
Middleboxes line. Now it does that and then hangs.
I've pasted the output below from running ndtd with "-dddd"; i
think the relevant bit is "failed to get web10g connection data".
Any ideas on what i should try next?
ANL/Internet2 NDT ver 3.6.5.2
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 (family 0)
Reading line: Signal 17 received by process 3805
Reading line: Web100srv (ver 3.6.5) process (3805) started Mar 26 15:21:28
Reading line: Signal 17 received by process 3805
Reading line: Signal 13 received by process 3805
Reading line: Signal 17 received by process 3822
Reading line: Web100srv (ver 3.6.5) process (3822) started Mar 26 15:22:25
Reading line: Signal 17 received by process 3822
Reading line: Signal 13 received by process 3822
Reading line: Signal 2 received by process 3822
Reading line: Web100srv (ver 3.6.5) process (3834) started Mar 26 15:26:08
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Unexpected signal (18) received, process (3834) may terminate
Reading line: Web100srv (ver 3.6.5) process (2859) started Mar 27 10:14:40
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Unexpected signal (18) received, process (2859) may terminate
Reading line: Web100srv (ver 3.6.5) process (2792) started Apr 5 14:51:11
Reading line: Web100srv (ver 3.6.5) process (2825) started Apr 7 13:13:48
Reading line: Web100srv (ver 3.6.5) process (2791) started Apr 7 13:32:42
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Unexpected signal (18) received, process (2791) may terminate
Reading line: Web100srv (ver 3.6.5.2) process (2838) started Apr 8 10:17:18
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Unexpected signal (18) received, process (2838) may terminate
Reading line: Web100srv (ver 3.6.5.2) process (2825) started Apr 8 11:15:09
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Unexpected signal (18) received, process (2825) may terminate
Reading line: Web100srv (ver 3.6.5.2) process (2829) started Apr 8 12:54:58
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Unexpected signal (18) received, process (2829) may terminate
Reading line: Web100srv (ver 3.6.5.2) process (2795) started Apr 8 13:09:44
Reading line: Apr 8 13:10:56 10.11.1.18 port 52134
Reading line: Apr 8 13:36:10 10.11.1.25 port 49564
Reading line: Apr 8 13:40:10 10.11.1.25 port 49893
Signal 17 received by process 3284
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 0x67c280 [10.11.1.18] sockfd=5.
Child thinks pipe() returned fd0=6, fd1=7 for pid=0
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 3288 testing will begin now
Queue pointer=3288, testing=1, waiting=1, mclients=0, zombie_check=0
Waiting for new connection, timer running
Valid test sequence requested, run test for client=3288
Child process 3288 started
run_test() routine, asking for test_suite = 1 8 2 4 32
Starting test suite:
> Middlebox test
> Simple firewall test
> C2S throughput test
> S2C throughput test
> META test
<-- 3288 - Middlebox test -->
-- port: 3003
test_min() failed to get web10g connection data, rc=0
Middlebox test FAILED!, rc=-3
Child 3288 returned non-zero (-3) from run_test() results some test failed!
Processing SIGCHLD signal for active web100srv process [0], sig17=0
Signal 17 received by process 3284
Timer expired while waiting for a new connection
Queue pointer=3288, testing=1, waiting=1, mclients=0, zombie_check=0
Processing SIGCHLD signal for active web100srv process [0], sig17=1
wait3() returned status=0 for PID=3288
wexitstatus = '0'
Main test process 3288 terminated, remove from queue
Attempting to clean up child 3288, head pid = 3288
Removing Child from head, decremented waiting/mclients 0/0
Timer not running, waiting for new connection
__
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:
- Re: NDT 3.6.5 on a 3.2.x kernel, Jon Kåre Hellan, 04/05/2013
- <Possible follow-up(s)>
- Re: NDT 3.6.5 on a 3.2.x kernel, Aaron Brown, 04/05/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Richard Sanger, 04/05/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Aaron Brown, 04/09/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Richard Sanger, 04/05/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/05/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Aaron Brown, 04/05/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/08/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/08/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/08/2013
- Message not available
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/08/2013
- Message not available
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/08/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Aaron Brown, 04/05/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/08/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Richard Sanger, 04/08/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/09/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Richard Sanger, 04/10/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/10/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Richard Sanger, 04/10/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Daniel A. Ramaley, 04/09/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Richard Sanger, 04/08/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Aaron Brown, 04/09/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Dominic Hamon, 04/09/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Dominic Hamon, 04/10/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Dominic Hamon, 04/10/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Aaron Brown, 04/10/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Dominic Hamon, 04/10/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Aaron Brown, 04/10/2013
- Re: NDT 3.6.5 on a 3.2.x kernel, Dominic Hamon, 04/10/2013
Archive powered by MHonArc 2.6.16.