To correct myself, fping did not die prematurely, it was getting no responses from the remote host because its p parameter was too short at default for an RTT of 600ms. After looking at the source, I realized that it is affected but the s parameter of flent, and changed that instead. On Nov 30, 2017 4:11 PM, "Georgios Amanakis" wrote: > I still got results but did not trust them. > The error occurred at the end of the run. > > ===========8<=========== > NetperfDemoRunner TCP upload CS5 finished > NetperfDemoRunner TCP upload EF finished > TimerRunner Watchdog [Ping (ms) ICMP] finished > NetperfDemoRunner TCP upload BK finished > WARNING: Program exited non-zero. > Runner class: PingRunner > Command: /usr/bin/fping -D -p 200 -c 350 10.10.0.1 > Return code: 1 > Stdout: > Stderr: > 10.10.0.1 : xmt/rcv/%loss = 350/0/100% > > WARNING: Command produced no valid data. > Runner class: PingRunner > Command: /usr/bin/fping -D -p 200 -c 350 10.10.0.1 > Return code: 1 > Stdout: > Stderr: > 10.10.0.1 : xmt/rcv/%loss = 350/0/100% > > PingRunner Ping (ms) ICMP finished > CpuStatsRunner cpu_stats_localhost finished > ===========8<=========== > > George > > On Thu, Nov 30, 2017 at 4:03 PM, Toke Høiland-Jørgensen > wrote: > >> Georgios Amanakis writes: >> >> > I had to run flent with "-s 0.61" in order to avoid errors with fping >> dying >> > prematurely. >> >> When did fping die, and did you still get results? There's a watchdog >> timer to keep it from running too long, but maybe that is a bit too >> aggressive? >> >> -Toke >> > >