ndt-users list created

[Aaron Brown <>]

Hey Adel,

Could you try using the source tarball from 
http://ndb1.internet2.edu/~aaron/ndt-3.6.5.2-rc2.i386/ndt-3.6.5.2.tar.gz and 
see if it fixes the issue you're seeing?

Cheers,
Aaron

On Jan 27, 2013, at 5:48 AM, Adel Marzouq Riyad 
<>
 wrote:

> 
> Sure. It is on 
> anonymous@ftp://81.21.98.15/ndtd
>  .
> 
> Thanks,
> Adel M. Riyad
> 
> 
> 
> -----Original Message-----
> From: 
> 
>  on behalf of Aaron Brown
> Sent: Thu 1/24/2013 8:41 PM
> To: Adel Marzouq Riyad
> Cc: 
> 
> Subject: Re: NDT Question..
> 
> Hey Adel,
> 
> Would it be possible to get the binary you ran that crashed as well?
> 
> Cheers,
> Aaron
> 
> On Jan 23, 2013, at 8:33 AM, Adel Marzouq Riyad 
> <>
>  wrote:
> 
>> 
>> Aaron:
>> 
>> I configured the system to allow core dumps, but still didn't get a code 
>> dump by ndt..
>> 
>> I checked the code of src/web100srv.c and found that SIGSEGV is handled 
>> hence a core dump is not created.
>> 
>> I modified the function cleanup() in src/web100srv.c as follows:
>> [adel@ndt
>>  src]# diff web100srv.c web100srv.c.patched
>> 450a451,452
>>>             signal(SIGSEGV, SIG_DFL);
>>>             kill(getpid(),SIGSEGV);
>> [adel@ndt
>>  src]#
>> 
>> Replaced the original with the patched web100srv.c, compiled, installed, 
>> and ran and core dump is created now.
>> 
>> The core dump is 17MB though, I put it on 
>> anonymous@ftp://81.21.98.15/core.24884
>>  with empty password.
>> another core is core.26004 is generated if used abort() instead of the 2 
>> functions above.
>> 
>> Want to mention that SIGSEGV is received by a child process, not the main 
>> parent ndt process.
>> I am using ndt-3.6.5
>> 
>> Please let me know if I am missing anything..
>> 
>> Thanks again,
>> Adel M. Riyad
>> 
>> 
>> 
>> -----Original Message-----
>> From: Aaron Brown 
>> [mailto:]
>> Sent: Tue 1/22/2013 9:51 PM
>> To: Adel Marzouq Riyad
>> Cc: 
>> 
>> Subject: Re: NDT Question..
>> 
>> Hey Adel,
>> 
>> Looks like it's crashing (Signal 11 received by process 27493). Is there a 
>> way to get a core dump?
>> 
>> Cheers,
>> Aaron
>> 
>> On Jan 22, 2013, at 4:31 AM, Adel Marzouq Riyad 
>> <>
>>  wrote:
>> 
>>> 
>>> Hi Aaron, here it is:
>>> 
>>> [root@ndt
>>>  ndt]# /usr/local/ndt/sbin/fakewww -dddd -l /usr/local/ndt/access.log -e 
>>> /usr/local/ndt/error.log -4 -b/usr/local/ndt/ndt &  
>>> /usr/local/ndt/sbin/ndtd -dddd -a --snaplog --tcpdump &
>>> 
>>> [1] 27486
>>> [2] 27487
>>> [root@ndt
>>>  ndt]# ANL/Internet2 NDT ver 3.6.5
>>>      Variables file = /usr/local/ndt/ndt/web100_variables
>>>      log file = /usr/local/ndt/ndt/web100srv.log
>>>      Admin file = /usr/local/ndt/ndt/admin.html
>>>      Debug level set to 4
>>> Jan 22 11:20:13 fakewww server started (NDT version 3.6.5)
>>>      port = 7123
>>>      federated mode = off
>>>      access log = /usr/local/ndt/access.log
>>>      error log = /usr/local/ndt/error.log
>>>      basedir = /usr/local/ndt/ndt
>>>      debug level set to 4
>>> server ready on port 3001
>>> web100_init() read 69 variables from file
>>> Signal 17 received by process 27487
>>> 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=7
>>> Generated iflist with device=usbmon1 and if_speed=121
>>> nothing in queue
>>> Timer not running, waiting for new connection
>>> Received connection from [10.0.0.70]
>>> Jan 22 11:20:21 [10.0.0.70] requested file '/tcpbw100.html' - sent to 
>>> client
>>> Jan 22 11:20:21 [10.0.0.70] requested file '/favicon.ico' - access denied
>>> New connection received, waiting for accept() to complete
>>> New connection received from 0x978f80 [10.0.0.70] sockfd=5.
>>> Client connect received from :IP 10.0.0.70 to some server on socket 5
>>> initialize_tests returned old/new client = 1, test_suite = 1 8 2 4 32
>>> Child thinks pipe() returned fd0=6, fd1=7 for pid=0
>>> Line just before ChldRdy: label, did't get here via the goto statement!
>>> ___-------______  client process is ready for testing!
>>> Telling client 27493 testing will begin now
>>> Queue pointer=27493, testing=1, waiting=1, mclients=0, zombie_check=0
>>> Waiting for new connection, timer running
>>> Valid test sequence requested, run test for client=27493
>>> Child process 27493 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
>>> <-- 27493 - Middlebox test -->
>>> -- port: 3003
>>> Looking for Web100 data on socketid 6
>>> Server: ndt;3003 Client: 10.0.0.70;49675 1456;10;10;
>>> Sending 1456 Byte packets over the network, and data=10;
>>> Signal 17 received by process 27493
>>> Timer expired while waiting for a new connection
>>> Queue pointer=27493, 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=27493, testing=1, waiting=1, mclients=0, zombie_check=0
>>> Waiting for new connection, timer running
>>> CWND limited throughput = 60082 kbps (60082.003999272856)
>>> <--------- 27493 ----------->
>>> <-- 27493 - Simple firewall test -->
>>> -- port: 34744
>>> -- SFW time: 1
>>> -- oport: 49676
>>> <-------------------------->
>>> <-- 27493 - C2S throughput test -->
>>> -- port: 3002
>>> listening for Inet connection on testOptions->c2ssockfd, fd=3
>>> Sending 'GO' signal, to tell client 27493 to head for the next test
>>> C2S test calling init_pkttrace() with pd=0x18657320
>>> Unknown address family=17 found
>>> IPv4 interface found address=10.0.0.15
>>> IPv4 address match, setting device to 'eth0'
>>> Opening network interface 'eth0' for packet-pair timing
>>> pcap_open_live() returned pointer 0x97edc0
>>> installing pkt filter for 'host 10.0.0.70 and port 49678'
>>> Initial pkt src data = 62b204
>>> end named_log_create 
>>> /usr/local/ndt/ndt/serverdata/2013/01/22/20130122T09:20:30.721051000Z_10.0.0.70:49678.c2s_ndttrace
>>> Opening 
>>> '/usr/local/ndt/ndt/serverdata/2013/01/22/20130122T09:20:30.721051000Z_10.0.0.70:49678.c2s_ndttrace'
>>>  log fine
>>> --tracefile after packet_trace 
>>> 20130122T09:20:30.721051000Z_10.0.0.70:49678.c2s_ndttrace
>>> end named_log_create 
>>> /usr/local/ndt/ndt/serverdata/2013/01/22/20130122T09:20:30.721051000Z_10.0.0.70:49678.c2s_snaplog
>>> Timer expired while waiting for a new connection
>>> Queue pointer=27493, testing=1, waiting=1, mclients=0, zombie_check=0
>>> Waiting for new connection, timer running
>>> Snaplog file: 
>>> /usr/local/ndt/ndt/serverdata/2013/01/22/20130122T09:20:30.721051000Z_10.0.0.70:49678.c2s_snaplog
>>> 
>>> New IPv4 packet trace started -- initializing counters
>>> Timer expired while waiting for a new connection
>>> Queue pointer=27493, 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=27493, 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=27493, testing=1, waiting=1, mclients=0, zombie_check=0
>>> Waiting for new connection, timer running
>>> Signal 11 received by process 27493
>>> Signal 17 received by process 27487
>>> Timer expired while waiting for a new connection
>>> Queue pointer=27493, testing=1, waiting=1, mclients=0, zombie_check=0
>>> Processing SIGCHLD signal for active web100srv process [0], sig17=1
>>> wait3() returned status=65024 for PID=27493
>>> wexitstatus = '254'
>>> Main test process 27493 terminated, remove from queue
>>> Attempting to clean up child 27493, head pid = 27493
>>> Removing Child from head, decremented waiting/mclients 0/0
>>> Timer not running, waiting for new connection
>>> Signal 14 received by process 27496
>>> 
>>> 
>>> 
>>> Adel M. Riyad
>>> Thanks and Best Regards,
>>> 
>>> 
>>> -----Original Message-----
>>> From: Aaron Brown 
>>> [mailto:]
>>> Sent: Fri 1/18/2013 10:27 PM
>>> To: Adel Marzouq Riyad
>>> Cc: 
>>> 
>>> Subject: Re: NDT Question..
>>> 
>>> Hi Adel,
>>> 
>>> Would it be possible to run the ndt server in debug mode? (add -dddd to 
>>> the command-line). Also, could you run it from the command-line and have 
>>> it not background (to see if any segfaulting is going on).
>>> 
>>> Cheers,
>>> Aaron
>>> 
>>> On Jan 16, 2013, at 5:34 AM, Adel Marzouq Riyad 
>>> <>
>>>  wrote:
>>> 
>>>> 
>>>> Hi Aaron, thanks for your response :-). Here is the info you requested:
>>>> 
>>>> Console output:
>>>> ----------------------------------------------------
>>>> CacheEntry[http://10.0.0.15:7123/Tcpbw100.jar]: 
>>>> updateAvailable=false,lastModified=Thu Jan 01 02:00:00 EET 1970,length=-1
>>>> Couldn't set system property. Check your security settings.
>>>> wait flag received = 0
>>>> Server version: 3.6.5
>>>> 40496288 bytes 58892.98382112343 kb/s 5.501 secs
>>>> Sending '58892.98382112343' back to server
>>>> calling in2Socket.getLocalAddress()
>>>> SFW: port=57092
>>>> SFW: testTime=1
>>>> Asking security manager for listen permissions...
>>>> SFW: oport=49503
>>>> ******Send buffer size =8192
>>>> SocketException while writing to serverjava.net.SocketException: Socket 
>>>> closed
>>>> 10007.0 millisec test completed,65536,17034
>>>> 34054.881582891976 kb/s outbound
>>>> Exception in thread "Thread-15" java.lang.NumberFormatException: For 
>>>> input string: "
>>>> 
>>>> web100srv.log:
>>>> Jan 16 12:08:54  10.0.0.70 port 49501
>>>> Snaplog file: 
>>>> /usr/local/ndt/ndt/serverdata/2013/01/16/20130116T10:08:54.847227000Z_10.0.0.70:49505.c2s_snaplog
>>>> [C2S throughput test]
>>>> 
>>>> 
>>>> Service are running like this: #pgrep -lf | grep -i ndt
>>>> /usr/local/ndt/sbin/ndtd -a --snaplog --tcpdump
>>>> /usr/local/ndt/sbin/fakewww -d -l /usr/local/ndt/access.log -e 
>>>> /usr/local/ndt/error.log -4 -b/usr/local/ndt/ndt
>>>> Both are running as root.
>>>> 
>>>> BEst Regards,
>>>> Adel M. Riyad
>>>> 
>>>> 
>>>> 
>>>> -----Original Message-----
>>>> From: Aaron Brown 
>>>> [mailto:]
>>>> Sent: Tue 1/15/2013 11:08 PM
>>>> To: Adel Marzouq Riyad
>>>> Cc: 
>>>> 
>>>> Subject: Re: NDT Question..
>>>> 
>>>> Hi Adel,
>>>> 
>>>> Would you be able to send the web100srv log file, and the java console 
>>>> output?
>>>> 
>>>> Cheers,
>>>> Aaron
>>>> 
>>>>> -----Original Message-----
>>>>> From: Adel Marzouq Riyad 
>>>>> [mailto:]
>>>>>  
>>>>> Sent: Wednesday, December 19, 2012 8:35 AM
>>>>> To: 
>>>>> 
>>>>> Subject: NDT Question..
>>>>> Good day Mr.Carlson,
>>>>> 
>>>>> I have installed NDT 3.6.5 on a CentOS 6 machine with kernel 2.6.35 
>>>>> patch with Web100.
>>>>> 
>>>>> head -1 /proc/web100/header shows: 2.5.30 201008181640 net100
>>>>> 
>>>>> Either I test from a machine inside the same LAN or from outside, the 
>>>>> C2S test doesn't finish and the output on the applet doesn't change 
>>>>> from the attached picture.
>>>>> 
>>>>> iptables is off, no firewall is running on server.
>>>>> 
>>>>> I followed the installation steps in the document bundled with NDT code.
>>>>> 
>>>>> Do you have any hint what this problem could be??
>>>>> 
>>>>> Adel M. Riyad
>>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
> 
> 
> 
>