id summary reporter owner description type status priority milestone component version resolution keywords cc 4 useless error message when ns fails to parse mikeryan somebody "{{{ users ~ $ fedd_ns2topdl.py --url http://localhost:23235/ --file=line.ns Error: Connection Error (8) Description: Too many failures: }}} From /var/log/fedd.log: {{{ 01 Nov 10 13:59:34 fedd [fedd] Error on incoming connection: ('127.0.0.1', 57542) wrong # args: should be ""ns self class proc n1 n2 bw delay type args"" (Simulator duplex-link line 49) invoked from within ""$ns duplex-link $left $middle 100mb 0ms"" invoked from within ""set link0 [$ns duplex-link $left $middle 100mb 0ms]"" (file ""/tmp/ns2topdl-Zynywq/experiment.tcl"" line 8) invoked from within ""real_source ${GLOBALS::nsfile}"" invoked from within ""if { ${GLOBALS::errors} != 1 } { file copy -force ${GLOBALS::tbcompat} . real_source ${GLOBALS::nsfile} if {${GLOBALS::ran} == 0} { perr..."" (file ""/usr/testbed/lib/ns2ir/parse.tcl"" line 694) 01 Nov 10 13:59:34 fedd [fedd] Error on incoming connection: ('127.0.0.1', 52443) }}} will attach bad NS file" enhancement major component1 fixed