From: Rich Brown <notifications@github.com> To: tohojo/flent <flent@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [Flent-users] [tohojo/flent] `ss: command not found` on macOS (#177) Date: Thu, 05 Sep 2019 05:48:34 -0700 [thread overview] Message-ID: <tohojo/flent/issues/177@github.com> (raw) [-- Attachment #1.1: Type: text/plain, Size: 2341 bytes --] Spurred on by Dave's [Coffee Shop Bloat Test](https://lists.bufferbloat.net/pipermail/bloat/2019-September/009336.html) script, I decided to try it on my Mac (10.12.6) with Flent 1.3.0. This command seemed to work fine: `flent -x -H flent-fremont.bufferbloat.net -t Rich_Test --te=upload_streams=4 tcp_ndown` But I got a ton of error messages when I tried the second command using the `--socket-stats` option: there were none if I left that off. What other information could I provide? Thanks. ``` bash bash-3.2$ flent -x -H flent-fremont.bufferbloat.net -t Rich_Test --te=upload_streams=4 --socket-stats tcp_nup Started Flent 1.3.0 using Python 2.7.15. Starting tcp_nup test. Expected run time: 70 seconds. WARNING: Command produced no valid data. Runner class: SsRunner Command: /bin/bash /usr/local/lib/python2.7/site-packages/flent/scripts/ss_iterate.sh -I 0.20 -c 300 -H localhost -t '23.239.20.41' -f ' and dport != 12865' Return code: 0 Stdout: Time: 1567685642.N --- Time: 1567685642.N --- Time: 1567685642.N ... a zillion of these lines, followed by ... Time: 1567685705.N --- Time: 1567685706.N --- Time: 1567685706.N --- Stderr: /usr/local/lib/python2.7/site-packages/flent/scripts/ss_iterate.sh: line 55: ss: command not found /usr/local/lib/python2.7/site-packages/flent/scripts/ss_iterate.sh: line 55: ss: command not found ... a zillion of these lines, and finally ... /usr/local/lib/python2.7/site-packages/flent/scripts/ss_iterate.sh: line 55: ss: command not found Data file written to ./tcp_nup-2019-09-05T081356.815453.Rich_Test.flent.gz. Summary of tcp_nup test run from 2019-09-05 12:13:56.815453 Title: 'Rich_Test' avg median # data pts Ping (ms) ICMP : 100.69 101.00 ms 349 TCP upload avg : 0.18 0.18 Mbits/s 101 TCP upload sum : 0.31 0.30 Mbits/s 101 TCP upload::1 : 0.15 0.13 Mbits/s 7 TCP upload::2 : 0.23 0.21 Mbits/s 11 TCP upload::3 : 0.17 0.17 Mbits/s 8 TCP upload::4 : 0.23 0.21 Mbits/s 11 bash-3.2$ ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/tohojo/flent/issues/177 [-- Attachment #1.2: Type: text/html, Size: 4319 bytes --] [-- Attachment #2: Type: text/plain, Size: 151 bytes --] _______________________________________________ Flent-users mailing list Flent-users@flent.org http://flent.org/mailman/listinfo/flent-users_flent.org
next reply other threads:[~2019-09-05 12:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-05 12:48 Rich Brown [this message] 2019-09-05 12:57 ` Toke Høiland-Jørgensen 2019-09-05 13:00 ` Rich Brown 2019-09-05 13:00 ` Rich Brown 2019-09-06 1:03 ` Dave Täht
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=tohojo/flent/issues/177@github.com \ --to=notifications@github.com \ --cc=flent@noreply.github.com \ --cc=reply+AHVNJP6ADJBJRFDV3MQQSHN3PZCLFEVBNHHB2MFPQ4@reply.github.com \ --cc=subscribed@noreply.github.com \ --subject='Re: [Flent-users] [tohojo/flent] `ss: command not found` on macOS (#177)' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox