perfSONAR User Q&A and Other Discussion

[Gaetano Vocca <>]

This I can try for sure but the ping executable is in the same path both on working and in non-working machines. Additionally this path in in the $PATH in both cases. 

Thanks

Gaetano

Il giorno 26/gen/2015, alle ore 19:46, Eli Dart <> ha scritto:

What path is bwctl using?  Are we sure it can find the ping binary?

If we know that ping is in the path that bwctl is using, how about move the ping binary aside for a moment and replace ping with a one-line shell script that does something like 'echo "Here I am!!!" ' - if that generates output that bwctl can see, we've learned something.  If it does not, we have learned something else.

Thanks,

Eli

On Mon, Jan 26, 2015 at 7:54 AM, Brian Tierney <> wrote:

I dont think building from source will help, but I'm stumped. Anyone else have any ideas?

On Mon, Jan 26, 2015 at 1:48 AM, Gaetano Vocca <> wrote:

Hi,

do you think it makes sense to recompile from the sources, instaed of using the prebuilt package?

If yes, which sources should I take?

 

Thank you in advance

Gaetano

 

Da: Gaetano Vocca [mailto:]
Inviato: giovedì 22 gennaio 2015 14:58
A: ''
Cc: 'Aaron Brown'; ''
Oggetto: R: [perfsonar-user] Ping test failing on Centos 6.x

 

Hi Brian,

yes, ping works also as non-privileged user, hereafter the output:

 

pi@rhnan ~ $ ping -c 10 -i 1.000000 -W 1 -I 192.168.3.195 192.168.12.103

PING 192.168.12.103 (192.168.12.103) from 192.168.3.195 : 56(84) bytes of data.

64 bytes from 192.168.12.103: icmp_seq=1 ttl=61 time=60.9 ms

64 bytes from 192.168.12.103: icmp_seq=2 ttl=61 time=59.2 ms

64 bytes from 192.168.12.103: icmp_seq=3 ttl=61 time=61.7 ms

64 bytes from 192.168.12.103: icmp_seq=4 ttl=61 time=60.6 ms

64 bytes from 192.168.12.103: icmp_seq=5 ttl=61 time=60.4 ms

64 bytes from 192.168.12.103: icmp_seq=6 ttl=61 time=59.2 ms

64 bytes from 192.168.12.103: icmp_seq=7 ttl=61 time=60.5 ms

64 bytes from 192.168.12.103: icmp_seq=8 ttl=61 time=106 ms

64 bytes from 192.168.12.103: icmp_seq=9 ttl=61 time=60.0 ms

64 bytes from 192.168.12.103: icmp_seq=10 ttl=61 time=225 ms

 

--- 192.168.12.103 ping statistics ---

10 packets transmitted, 10 received, 0% packet loss, time 9239ms

rtt min/avg/max/mdev = 59.261/81.507/225.852/50.034 ms

 

Please note that although the user is pi this machine is not a Raspberry.

 

Thanks

Gaetano

 

Da: Brian Tierney []
Inviato: giovedì 22 gennaio 2015 14:54
A: Gaetano Vocca
Cc: Aaron Brown;

Oggetto: Re: [perfsonar-user] Ping test failing on Centos 6.x

 

 

Perhaps is a problem with the permission on the ping executable?

 

bwctl runs as user 'bwctl', but I noticed you are running ping as root.

 

Does you ping work as a regular user?

 

 

On Thu, Jan 22, 2015 at 7:47 AM, Gaetano Vocca <> wrote:

Here it is Aaron, it looks like the output is available. Maybe an unexpected structure?

 

root@rhnan ~ # ping -c 10 -i 1.000000 -W 1 -I 192.168.3.195 192.168.12.103

PING 192.168.12.103 (192.168.12.103) from 192.168.3.195 : 56(84) bytes of data.

64 bytes from 192.168.12.103: icmp_seq=1 ttl=61 time=64.3 ms

64 bytes from 192.168.12.103: icmp_seq=2 ttl=61 time=61.0 ms

64 bytes from 192.168.12.103: icmp_seq=3 ttl=61 time=62.1 ms

64 bytes from 192.168.12.103: icmp_seq=4 ttl=61 time=62.8 ms

64 bytes from 192.168.12.103: icmp_seq=5 ttl=61 time=59.5 ms

64 bytes from 192.168.12.103: icmp_seq=6 ttl=61 time=58.7 ms

64 bytes from 192.168.12.103: icmp_seq=7 ttl=61 time=61.2 ms

64 bytes from 192.168.12.103: icmp_seq=8 ttl=61 time=59.6 ms

64 bytes from 192.168.12.103: icmp_seq=9 ttl=61 time=60.1 ms

64 bytes from 192.168.12.103: icmp_seq=10 ttl=61 time=59.9 ms

 

--- 192.168.12.103 ping statistics ---

10 packets transmitted, 10 received, 0% packet loss, time 9073ms

rtt min/avg/max/mdev = 58.721/60.945/64.323/1.664 ms

 

Cheers

Gaetano

 

-----Messaggio originale-----
Da: Aaron Brown [mailto:]
Inviato: giovedì 22 gennaio 2015 14:40

A: Gaetano Vocca
Cc:
Oggetto: Re: [perfsonar-user] Ping test failing on Centos 6.x

 

Hey Gaetano,

 

It looks like the ping command isn’t outputting anything, can you try running the following by hand:

 

ping -c 10 -i 1.000000 -W 1 -I 192.168.3.195 192.168.12.103

 

Cheers,

Aaron

 

> On Jan 22, 2015, at 8:33 AM, Gaetano Vocca <> wrote:

>

> Hi Aaron,

> here is the result:

> 

> root@rhnan ~ # bwping -T ping -v -c 192.168.12.103 Messages being sent

> to syslog(user,err)

> bwping: Using 192.168.3.195 as the address for local sender

> bwping: Using 192.168.12.103 as the address for remote receiver

> bwping: Available in-common: ping owamp

> bwping: Using tool: ping

> bwping: Server '192.168.12.103' accepted test request at time

> 1421933525.644205

> bwping: Client 'localhost' accepted test request at time

> 1421933525.644205

> bwping: 20 seconds until test results available

> 

> SENDER START

> bwctl: start_endpoint: 3630922321.037754

> bwctl: run_endpoint: receiver: 192.168.12.103

> bwctl: run_endpoint: sender: 192.168.3.195

> bwctl: exec_line: ping -c 10 -i 1.000000 -W 1 -I 192.168.3.195

> 192.168.12.103

> bwctl: run_tool: tester: ping

> bwctl: run_tool: receiver: 192.168.12.103

> bwctl: run_tool: sender: 192.168.3.195

> bwctl: start_tool: 3630922325.644361

> bwctl: stop_tool: 3630922334.728373

> bwctl: stop_endpoint: 3630922336.800635

> 

> SENDER END

> 

> Thanks

> Gaetano

> 

> Da: Aaron Brown []

> Inviato: giovedì 22 gennaio 2015 14:30

> A: Gaetano Vocca

> Cc:

> Oggetto: Re: [perfsonar-user] Ping test failing on Centos 6.x

> 

> Hey Gaetano,

> 

> Could you try running bwping with the “-v” flag?

> 

> Cheers,

> Aaron

> 

>> On Jan 22, 2015, at 7:50 AM, Gaetano Vocca <> wrote:

>> 

>> Hi all,

>> I tried to use bwping for a round trip delay test from a Centos 6 machine towards a Debian (Raspbian) one and it fails with the following output:

>> 

>> pi@rhnan ~ $ bwping -T ping -c 192.168.12.103

>> bwping: Using tool: ping

>> bwping: 21 seconds until test results available

>> 

>> SENDER START

>> 

>> SENDER END

>> 

>> Checking the logs I noticed this error

>> 

>> <RECV_OUTPUT>';

>> Jan 22 13:42:33 rhnan bwctld (INPUT): $VAR1 = 'bwctl: nothing to exec

>> for ping server</RE CV_OUTPUT>'

>> 

>> This happens also if bwping is run as root. Bwping version is 1.5.2-10 and it was installed by package, I mean not from the sources recompiled. Does anybody have suggestions?

>> 

>> 

>> Thanks

>> Gaetano

 

 

--

Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net

--

Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net

--

Eli Dart, Network Engineer                          NOC: (510) 486-7600

ESnet Office of the CTO (AS293)                          (800) 333-7638

Lawrence Berkeley National Laboratory 

PGP Key fingerprint = C970 F8D3 CFDD 8FFF 5486 343A 2D31 4478 5F82 B2B3