ping issues

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

ping issues

Paul Theodoropoulos
I'm running a little personal project on a shoestring budget - e.g. a
couple of AWS t2.nano instances, so everything needs to be stripped as
bare as possible.

Testing one of the servers from offsite, I can run a single byte
(ignoring overhead), single count ping from the command line no problem
(Debian Stretch).

root@b-ns: ~ # ping -c1 -s 1 a.ns.anastrophe.com
PING a.ns.anastrophe.com (52.32.92.141) 1(29) bytes of data.
9 bytes from a.ns.anastrophe.com (52.32.92.141): icmp_seq=1 ttl=42

--- a.ns.anastrophe.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms

etc etc

However, within monit, the smallest I can set the size is 20, anything
less and it fails.

check host a.ns-ping with address 52.32.92.141
if failed
    ping4 count 3 size 20
    with timeout 15 seconds
then exec /usr/local/bin/pushover

I can certainly live with 20 byte packets, but I'm wondering why less
than 20 bytes won't work in monit. The docs only say that the default is
64 bytes, but no minimum.

--
Paul Theodoropoulos
www.anastrophe.com


--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
Reply | Threaded
Open this post in threaded view
|

Re: ping issues

martinp@tildeslash.com
Hello,

please can you get a network trace of failed ping tests?

Best regards,
Martin


> On 17 May 2018, at 05:45, Paul Theodoropoulos <[hidden email]> wrote:
>
> I'm running a little personal project on a shoestring budget - e.g. a couple of AWS t2.nano instances, so everything needs to be stripped as bare as possible.
>
> Testing one of the servers from offsite, I can run a single byte (ignoring overhead), single count ping from the command line no problem (Debian Stretch).
>
> root@b-ns: ~ # ping -c1 -s 1 a.ns.anastrophe.com
> PING a.ns.anastrophe.com (52.32.92.141) 1(29) bytes of data.
> 9 bytes from a.ns.anastrophe.com (52.32.92.141): icmp_seq=1 ttl=42
>
> --- a.ns.anastrophe.com ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>
> etc etc
>
> However, within monit, the smallest I can set the size is 20, anything less and it fails.
>
> check host a.ns-ping with address 52.32.92.141
> if failed
>    ping4 count 3 size 20
>    with timeout 15 seconds
> then exec /usr/local/bin/pushover
>
> I can certainly live with 20 byte packets, but I'm wondering why less than 20 bytes won't work in monit. The docs only say that the default is 64 bytes, but no minimum.
>
> --
> Paul Theodoropoulos
> www.anastrophe.com
>
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general


--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
Reply | Threaded
Open this post in threaded view
|

Re: ping issues

Paul Theodoropoulos
root@b-ns: ~ # traceroute a.ns.anastrophe.com
traceroute to a.ns.anastrophe.com (52.32.92.141), 30 hops max, 60 byte packets
 1  216.239.58.214 (216.239.58.214)  37.315 ms 74.125.253.191 (74.125.253.191)  36.234 ms  36.200 ms
 2  108.170.242.250 (108.170.242.250)  36.790 ms 108.170.243.9 (108.170.243.9)  36.774 ms 108.170.242.250 (108.170.242.250)  36.793 ms
 3  * 52.95.216.112 (52.95.216.112)  36.951 ms 72.21.221.102 (72.21.221.102)  36.568 ms
 4  54.240.243.128 (54.240.243.128)  37.365 ms 54.240.243.108 (54.240.243.108)  37.017 ms 54.240.243.48 (54.240.243.48)  37.246 ms
 5  54.240.242.75 (54.240.242.75)  36.875 ms 54.240.242.39 (54.240.242.39)  36.884 ms 54.240.242.121 (54.240.242.121)  37.016 ms
 6  * * *
 7  52.93.128.36 (52.93.128.36)  50.907 ms 205.251.232.116 (205.251.232.116)  50.172 ms 52.93.128.34 (52.93.128.34)  51.422 ms
 8  54.239.46.106 (54.239.46.106)  50.115 ms * 54.239.46.104 (54.239.46.104)  49.751 ms
 9  52.93.12.184 (52.93.12.184)  69.342 ms * 52.93.12.112 (52.93.12.112)  66.724 ms
10  52.93.12.234 (52.93.12.234)  76.730 ms 52.93.13.46 (52.93.13.46)  51.741 ms 52.93.12.82 (52.93.12.82)  52.745 ms
11  52.93.12.141 (52.93.12.141)  50.506 ms 52.93.12.74 (52.93.12.74)  53.822 ms 52.93.12.177 (52.93.12.177)  50.117 ms
12  52.93.12.103 (52.93.12.103)  50.149 ms 52.93.12.241 (52.93.12.241)  50.060 ms 52.93.12.72 (52.93.12.72)  53.926 ms
13  52.93.12.97 (52.93.12.97)  50.902 ms 52.93.13.57 (52.93.13.57)  50.717 ms 52.93.12.205 (52.93.12.205)  50.763 ms
14  * 52.93.240.91 (52.93.240.91)  51.905 ms 52.93.240.83 (52.93.240.83)  66.118 ms
15  * * 52.93.15.227 (52.93.15.227)  50.163 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * *^C

And just for good measure, a traceroute from the destination back to the source.

root@a: ~ # traceroute b.ns.anastrophe.com
traceroute to b.ns.anastrophe.com (35.193.38.199), 30 hops max, 60 byte packets
 1  ec2-50-112-0-154.us-west-2.compute.amazonaws.com (50.112.0.154)  20.232 ms ec2-50-112-0-212.us-west-2.compute.amazonaws.com (50.112.0.212)  13.876 ms ec2-50-112-0-214.us-west-2.compute.amazonaws.com (50.112.0.214)  15.830 ms
 2  100.66.8.184 (100.66.8.184)  20.158 ms 100.66.8.22 (100.66.8.22)  15.866 ms 100.66.8.180 (100.66.8.180)  13.869 ms
 3  100.66.10.46 (100.66.10.46)  21.260 ms 100.66.11.164 (100.66.11.164)  16.078 ms 100.66.10.68 (100.66.10.68)  14.671 ms
 4  100.66.6.43 (100.66.6.43)  24.452 ms 100.66.6.133 (100.66.6.133)  11.580 ms 100.66.6.237 (100.66.6.237)  18.260 ms
 5  100.66.4.201 (100.66.4.201)  18.515 ms 100.66.4.243 (100.66.4.243)  14.603 ms 100.66.4.131 (100.66.4.131)  22.182 ms
 6  100.65.8.129 (100.65.8.129)  0.224 ms 100.65.11.65 (100.65.11.65)  0.293 ms 100.65.10.33 (100.65.10.33)  1.007 ms
 7  52.93.240.90 (52.93.240.90)  0.673 ms  0.633 ms 52.93.240.82 (52.93.240.82)  0.636 ms
 8  52.93.12.174 (52.93.12.174)  21.191 ms 52.93.12.66 (52.93.12.66)  3.713 ms 52.93.12.138 (52.93.12.138)  16.026 ms
 9  52.93.12.223 (52.93.12.223)  0.817 ms 52.93.12.153 (52.93.12.153)  0.761 ms 52.93.12.113 (52.93.12.113)  0.741 ms
10  100.91.25.100 (100.91.25.100)  6.881 ms 100.91.25.146 (100.91.25.146)  7.421 ms 100.91.25.80 (100.91.25.80)  7.475 ms
11  54.239.42.195 (54.239.42.195)  15.391 ms 54.239.46.52 (54.239.46.52)  7.890 ms 54.239.43.127 (54.239.43.127)  6.545 ms
12  54.239.42.234 (54.239.42.234)  7.401 ms 100.91.139.113 (100.91.139.113)  7.686 ms 100.91.139.81 (100.91.139.81)  7.232 ms
13  52.95.52.196 (52.95.52.196)  9.535 ms 100.91.139.85 (100.91.139.85)  7.344 ms 52.95.52.124 (52.95.52.124)  7.184 ms
14  52.95.52.225 (52.95.52.225)  6.484 ms 52.95.52.123 (52.95.52.123)  7.370 ms 52.95.52.130 (52.95.52.130)  8.346 ms
15  52.95.216.103 (52.95.216.103)  7.099 ms 52.95.52.251 (52.95.52.251)  8.366 ms 52.95.216.103 (52.95.216.103)  7.040 ms
16  52.95.216.103 (52.95.216.103)  8.005 ms 108.170.245.124 (108.170.245.124)  6.278 ms 52.95.216.103 (52.95.216.103)  8.063 ms
17  108.170.245.124 (108.170.245.124)  7.138 ms 108.170.245.107 (108.170.245.107)  7.100 ms 108.170.245.108 (108.170.245.108)  7.768 ms
18  216.239.46.158 (216.239.46.158)  40.529 ms 216.239.50.39 (216.239.50.39)  8.145 ms 216.239.46.156 (216.239.46.156)  40.506 ms
19  216.239.43.227 (216.239.43.227)  48.931 ms 209.85.240.33 (209.85.240.33)  41.331 ms 216.239.46.156 (216.239.46.156)  41.268 ms
20  216.239.47.251 (216.239.47.251)  50.622 ms 209.85.248.209 (209.85.248.209)  50.059 ms  50.042 ms
21  209.85.252.253 (209.85.252.253)  50.162 ms 209.85.248.209 (209.85.248.209)  50.939 ms 72.14.239.219 (72.14.239.219)  49.764 ms
22  216.239.50.5 (216.239.50.5)  51.618 ms * *
23  * * *


On 5/17/18 09:44, [hidden email] wrote:
Hello,

please can you get a network trace of failed ping tests?

Best regards,
Martin


On 17 May 2018, at 05:45, Paul Theodoropoulos [hidden email] wrote:

I'm running a little personal project on a shoestring budget - e.g. a couple of AWS t2.nano instances, so everything needs to be stripped as bare as possible.

Testing one of the servers from offsite, I can run a single byte (ignoring overhead), single count ping from the command line no problem (Debian Stretch).

root@b-ns: ~ # ping -c1 -s 1 a.ns.anastrophe.com
PING a.ns.anastrophe.com (52.32.92.141) 1(29) bytes of data.
9 bytes from a.ns.anastrophe.com (52.32.92.141): icmp_seq=1 ttl=42

--- a.ns.anastrophe.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms

etc etc

However, within monit, the smallest I can set the size is 20, anything less and it fails.

check host a.ns-ping with address 52.32.92.141
if failed
   ping4 count 3 size 20
   with timeout 15 seconds
then exec /usr/local/bin/pushover

I can certainly live with 20 byte packets, but I'm wondering why less than 20 bytes won't work in monit. The docs only say that the default is 64 bytes, but no minimum.

-- 
Paul Theodoropoulos
www.anastrophe.com


-- 
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

    

-- 
Paul Theodoropoulos
www.anastrophe.com

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
Reply | Threaded
Open this post in threaded view
|

Re: ping issues

martinp@tildeslash.com
Thanks for data. Please can you get yet the ping packet capture (using for example Wireshark) and send it in pcap format to [hidden email]?



On 17 May 2018, at 18:54, Paul Theodoropoulos <[hidden email]> wrote:

root@b-ns: ~ # traceroute a.ns.anastrophe.com
traceroute to a.ns.anastrophe.com (52.32.92.141), 30 hops max, 60 byte packets
 1  216.239.58.214 (216.239.58.214)  37.315 ms 74.125.253.191 (74.125.253.191)  36.234 ms  36.200 ms
 2  108.170.242.250 (108.170.242.250)  36.790 ms 108.170.243.9 (108.170.243.9)  36.774 ms 108.170.242.250 (108.170.242.250)  36.793 ms
 3  * 52.95.216.112 (52.95.216.112)  36.951 ms 72.21.221.102 (72.21.221.102)  36.568 ms
 4  54.240.243.128 (54.240.243.128)  37.365 ms 54.240.243.108 (54.240.243.108)  37.017 ms 54.240.243.48 (54.240.243.48)  37.246 ms
 5  54.240.242.75 (54.240.242.75)  36.875 ms 54.240.242.39 (54.240.242.39)  36.884 ms 54.240.242.121 (54.240.242.121)  37.016 ms
 6  * * *
 7  52.93.128.36 (52.93.128.36)  50.907 ms 205.251.232.116 (205.251.232.116)  50.172 ms 52.93.128.34 (52.93.128.34)  51.422 ms
 8  54.239.46.106 (54.239.46.106)  50.115 ms * 54.239.46.104 (54.239.46.104)  49.751 ms
 9  52.93.12.184 (52.93.12.184)  69.342 ms * 52.93.12.112 (52.93.12.112)  66.724 ms
10  52.93.12.234 (52.93.12.234)  76.730 ms 52.93.13.46 (52.93.13.46)  51.741 ms 52.93.12.82 (52.93.12.82)  52.745 ms
11  52.93.12.141 (52.93.12.141)  50.506 ms 52.93.12.74 (52.93.12.74)  53.822 ms 52.93.12.177 (52.93.12.177)  50.117 ms
12  52.93.12.103 (52.93.12.103)  50.149 ms 52.93.12.241 (52.93.12.241)  50.060 ms 52.93.12.72 (52.93.12.72)  53.926 ms
13  52.93.12.97 (52.93.12.97)  50.902 ms 52.93.13.57 (52.93.13.57)  50.717 ms 52.93.12.205 (52.93.12.205)  50.763 ms
14  * 52.93.240.91 (52.93.240.91)  51.905 ms 52.93.240.83 (52.93.240.83)  66.118 ms
15  * * 52.93.15.227 (52.93.15.227)  50.163 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * *^C

And just for good measure, a traceroute from the destination back to the source.

root@a: ~ # traceroute b.ns.anastrophe.com
traceroute to b.ns.anastrophe.com (35.193.38.199), 30 hops max, 60 byte packets
 1  ec2-50-112-0-154.us-west-2.compute.amazonaws.com (50.112.0.154)  20.232 ms ec2-50-112-0-212.us-west-2.compute.amazonaws.com (50.112.0.212)  13.876 ms ec2-50-112-0-214.us-west-2.compute.amazonaws.com (50.112.0.214)  15.830 ms
 2  100.66.8.184 (100.66.8.184)  20.158 ms 100.66.8.22 (100.66.8.22)  15.866 ms 100.66.8.180 (100.66.8.180)  13.869 ms
 3  100.66.10.46 (100.66.10.46)  21.260 ms 100.66.11.164 (100.66.11.164)  16.078 ms 100.66.10.68 (100.66.10.68)  14.671 ms
 4  100.66.6.43 (100.66.6.43)  24.452 ms 100.66.6.133 (100.66.6.133)  11.580 ms 100.66.6.237 (100.66.6.237)  18.260 ms
 5  100.66.4.201 (100.66.4.201)  18.515 ms 100.66.4.243 (100.66.4.243)  14.603 ms 100.66.4.131 (100.66.4.131)  22.182 ms
 6  100.65.8.129 (100.65.8.129)  0.224 ms 100.65.11.65 (100.65.11.65)  0.293 ms 100.65.10.33 (100.65.10.33)  1.007 ms
 7  52.93.240.90 (52.93.240.90)  0.673 ms  0.633 ms 52.93.240.82 (52.93.240.82)  0.636 ms
 8  52.93.12.174 (52.93.12.174)  21.191 ms 52.93.12.66 (52.93.12.66)  3.713 ms 52.93.12.138 (52.93.12.138)  16.026 ms
 9  52.93.12.223 (52.93.12.223)  0.817 ms 52.93.12.153 (52.93.12.153)  0.761 ms 52.93.12.113 (52.93.12.113)  0.741 ms
10  100.91.25.100 (100.91.25.100)  6.881 ms 100.91.25.146 (100.91.25.146)  7.421 ms 100.91.25.80 (100.91.25.80)  7.475 ms
11  54.239.42.195 (54.239.42.195)  15.391 ms 54.239.46.52 (54.239.46.52)  7.890 ms 54.239.43.127 (54.239.43.127)  6.545 ms
12  54.239.42.234 (54.239.42.234)  7.401 ms 100.91.139.113 (100.91.139.113)  7.686 ms 100.91.139.81 (100.91.139.81)  7.232 ms
13  52.95.52.196 (52.95.52.196)  9.535 ms 100.91.139.85 (100.91.139.85)  7.344 ms 52.95.52.124 (52.95.52.124)  7.184 ms
14  52.95.52.225 (52.95.52.225)  6.484 ms 52.95.52.123 (52.95.52.123)  7.370 ms 52.95.52.130 (52.95.52.130)  8.346 ms
15  52.95.216.103 (52.95.216.103)  7.099 ms 52.95.52.251 (52.95.52.251)  8.366 ms 52.95.216.103 (52.95.216.103)  7.040 ms
16  52.95.216.103 (52.95.216.103)  8.005 ms 108.170.245.124 (108.170.245.124)  6.278 ms 52.95.216.103 (52.95.216.103)  8.063 ms
17  108.170.245.124 (108.170.245.124)  7.138 ms 108.170.245.107 (108.170.245.107)  7.100 ms 108.170.245.108 (108.170.245.108)  7.768 ms
18  216.239.46.158 (216.239.46.158)  40.529 ms 216.239.50.39 (216.239.50.39)  8.145 ms 216.239.46.156 (216.239.46.156)  40.506 ms
19  216.239.43.227 (216.239.43.227)  48.931 ms 209.85.240.33 (209.85.240.33)  41.331 ms 216.239.46.156 (216.239.46.156)  41.268 ms
20  216.239.47.251 (216.239.47.251)  50.622 ms 209.85.248.209 (209.85.248.209)  50.059 ms  50.042 ms
21  209.85.252.253 (209.85.252.253)  50.162 ms 209.85.248.209 (209.85.248.209)  50.939 ms 72.14.239.219 (72.14.239.219)  49.764 ms
22  216.239.50.5 (216.239.50.5)  51.618 ms * *
23  * * *


On 5/17/18 09:44, [hidden email] wrote:
Hello,

please can you get a network trace of failed ping tests?

Best regards,
Martin


On 17 May 2018, at 05:45, Paul Theodoropoulos [hidden email] wrote:

I'm running a little personal project on a shoestring budget - e.g. a couple of AWS t2.nano instances, so everything needs to be stripped as bare as possible.

Testing one of the servers from offsite, I can run a single byte (ignoring overhead), single count ping from the command line no problem (Debian Stretch).

root@b-ns: ~ # ping -c1 -s 1 a.ns.anastrophe.com
PING a.ns.anastrophe.com (52.32.92.141) 1(29) bytes of data.
9 bytes from a.ns.anastrophe.com (52.32.92.141): icmp_seq=1 ttl=42

--- a.ns.anastrophe.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms

etc etc

However, within monit, the smallest I can set the size is 20, anything less and it fails.

check host a.ns-ping with address 52.32.92.141
if failed
   ping4 count 3 size 20
   with timeout 15 seconds
then exec /usr/local/bin/pushover

I can certainly live with 20 byte packets, but I'm wondering why less than 20 bytes won't work in monit. The docs only say that the default is 64 bytes, but no minimum.

-- 
Paul Theodoropoulos
www.anastrophe.com


-- 
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

    

-- 
Paul Theodoropoulos
www.anastrophe.com
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general


--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
Reply | Threaded
Open this post in threaded view
|

Re: ping issues

Paul Theodoropoulos
Will do - thanks Martin!

On 5/17/18 09:58, [hidden email] wrote:
Thanks for data. Please can you get yet the ping packet capture (using for example Wireshark) and send it in pcap format to [hidden email]?



On 17 May 2018, at 18:54, Paul Theodoropoulos <[hidden email]> wrote:

root@b-ns: ~ # traceroute a.ns.anastrophe.com
traceroute to a.ns.anastrophe.com (52.32.92.141), 30 hops max, 60 byte packets
 1  216.239.58.214 (216.239.58.214)  37.315 ms 74.125.253.191 (74.125.253.191)  36.234 ms  36.200 ms
 2  108.170.242.250 (108.170.242.250)  36.790 ms 108.170.243.9 (108.170.243.9)  36.774 ms 108.170.242.250 (108.170.242.250)  36.793 ms
 3  * 52.95.216.112 (52.95.216.112)  36.951 ms 72.21.221.102 (72.21.221.102)  36.568 ms
 4  54.240.243.128 (54.240.243.128)  37.365 ms 54.240.243.108 (54.240.243.108)  37.017 ms 54.240.243.48 (54.240.243.48)  37.246 ms
 5  54.240.242.75 (54.240.242.75)  36.875 ms 54.240.242.39 (54.240.242.39)  36.884 ms 54.240.242.121 (54.240.242.121)  37.016 ms
 6  * * *
 7  52.93.128.36 (52.93.128.36)  50.907 ms 205.251.232.116 (205.251.232.116)  50.172 ms 52.93.128.34 (52.93.128.34)  51.422 ms
 8  54.239.46.106 (54.239.46.106)  50.115 ms * 54.239.46.104 (54.239.46.104)  49.751 ms
 9  52.93.12.184 (52.93.12.184)  69.342 ms * 52.93.12.112 (52.93.12.112)  66.724 ms
10  52.93.12.234 (52.93.12.234)  76.730 ms 52.93.13.46 (52.93.13.46)  51.741 ms 52.93.12.82 (52.93.12.82)  52.745 ms
11  52.93.12.141 (52.93.12.141)  50.506 ms 52.93.12.74 (52.93.12.74)  53.822 ms 52.93.12.177 (52.93.12.177)  50.117 ms
12  52.93.12.103 (52.93.12.103)  50.149 ms 52.93.12.241 (52.93.12.241)  50.060 ms 52.93.12.72 (52.93.12.72)  53.926 ms
13  52.93.12.97 (52.93.12.97)  50.902 ms 52.93.13.57 (52.93.13.57)  50.717 ms 52.93.12.205 (52.93.12.205)  50.763 ms
14  * 52.93.240.91 (52.93.240.91)  51.905 ms 52.93.240.83 (52.93.240.83)  66.118 ms
15  * * 52.93.15.227 (52.93.15.227)  50.163 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * *^C

And just for good measure, a traceroute from the destination back to the source.

root@a: ~ # traceroute b.ns.anastrophe.com
traceroute to b.ns.anastrophe.com (35.193.38.199), 30 hops max, 60 byte packets
 1  ec2-50-112-0-154.us-west-2.compute.amazonaws.com (50.112.0.154)  20.232 ms ec2-50-112-0-212.us-west-2.compute.amazonaws.com (50.112.0.212)  13.876 ms ec2-50-112-0-214.us-west-2.compute.amazonaws.com (50.112.0.214)  15.830 ms
 2  100.66.8.184 (100.66.8.184)  20.158 ms 100.66.8.22 (100.66.8.22)  15.866 ms 100.66.8.180 (100.66.8.180)  13.869 ms
 3  100.66.10.46 (100.66.10.46)  21.260 ms 100.66.11.164 (100.66.11.164)  16.078 ms 100.66.10.68 (100.66.10.68)  14.671 ms
 4  100.66.6.43 (100.66.6.43)  24.452 ms 100.66.6.133 (100.66.6.133)  11.580 ms 100.66.6.237 (100.66.6.237)  18.260 ms
 5  100.66.4.201 (100.66.4.201)  18.515 ms 100.66.4.243 (100.66.4.243)  14.603 ms 100.66.4.131 (100.66.4.131)  22.182 ms
 6  100.65.8.129 (100.65.8.129)  0.224 ms 100.65.11.65 (100.65.11.65)  0.293 ms 100.65.10.33 (100.65.10.33)  1.007 ms
 7  52.93.240.90 (52.93.240.90)  0.673 ms  0.633 ms 52.93.240.82 (52.93.240.82)  0.636 ms
 8  52.93.12.174 (52.93.12.174)  21.191 ms 52.93.12.66 (52.93.12.66)  3.713 ms 52.93.12.138 (52.93.12.138)  16.026 ms
 9  52.93.12.223 (52.93.12.223)  0.817 ms 52.93.12.153 (52.93.12.153)  0.761 ms 52.93.12.113 (52.93.12.113)  0.741 ms
10  100.91.25.100 (100.91.25.100)  6.881 ms 100.91.25.146 (100.91.25.146)  7.421 ms 100.91.25.80 (100.91.25.80)  7.475 ms
11  54.239.42.195 (54.239.42.195)  15.391 ms 54.239.46.52 (54.239.46.52)  7.890 ms 54.239.43.127 (54.239.43.127)  6.545 ms
12  54.239.42.234 (54.239.42.234)  7.401 ms 100.91.139.113 (100.91.139.113)  7.686 ms 100.91.139.81 (100.91.139.81)  7.232 ms
13  52.95.52.196 (52.95.52.196)  9.535 ms 100.91.139.85 (100.91.139.85)  7.344 ms 52.95.52.124 (52.95.52.124)  7.184 ms
14  52.95.52.225 (52.95.52.225)  6.484 ms 52.95.52.123 (52.95.52.123)  7.370 ms 52.95.52.130 (52.95.52.130)  8.346 ms
15  52.95.216.103 (52.95.216.103)  7.099 ms 52.95.52.251 (52.95.52.251)  8.366 ms 52.95.216.103 (52.95.216.103)  7.040 ms
16  52.95.216.103 (52.95.216.103)  8.005 ms 108.170.245.124 (108.170.245.124)  6.278 ms 52.95.216.103 (52.95.216.103)  8.063 ms
17  108.170.245.124 (108.170.245.124)  7.138 ms 108.170.245.107 (108.170.245.107)  7.100 ms 108.170.245.108 (108.170.245.108)  7.768 ms
18  216.239.46.158 (216.239.46.158)  40.529 ms 216.239.50.39 (216.239.50.39)  8.145 ms 216.239.46.156 (216.239.46.156)  40.506 ms
19  216.239.43.227 (216.239.43.227)  48.931 ms 209.85.240.33 (209.85.240.33)  41.331 ms 216.239.46.156 (216.239.46.156)  41.268 ms
20  216.239.47.251 (216.239.47.251)  50.622 ms 209.85.248.209 (209.85.248.209)  50.059 ms  50.042 ms
21  209.85.252.253 (209.85.252.253)  50.162 ms 209.85.248.209 (209.85.248.209)  50.939 ms 72.14.239.219 (72.14.239.219)  49.764 ms
22  216.239.50.5 (216.239.50.5)  51.618 ms * *
23  * * *


On 5/17/18 09:44, [hidden email] wrote:
Hello,

please can you get a network trace of failed ping tests?

Best regards,
Martin


On 17 May 2018, at 05:45, Paul Theodoropoulos [hidden email] wrote:

I'm running a little personal project on a shoestring budget - e.g. a couple of AWS t2.nano instances, so everything needs to be stripped as bare as possible.

Testing one of the servers from offsite, I can run a single byte (ignoring overhead), single count ping from the command line no problem (Debian Stretch).

root@b-ns: ~ # ping -c1 -s 1 a.ns.anastrophe.com
PING a.ns.anastrophe.com (52.32.92.141) 1(29) bytes of data.
9 bytes from a.ns.anastrophe.com (52.32.92.141): icmp_seq=1 ttl=42

--- a.ns.anastrophe.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms

etc etc

However, within monit, the smallest I can set the size is 20, anything less and it fails.

check host a.ns-ping with address 52.32.92.141
if failed
   ping4 count 3 size 20
   with timeout 15 seconds
then exec /usr/local/bin/pushover

I can certainly live with 20 byte packets, but I'm wondering why less than 20 bytes won't work in monit. The docs only say that the default is 64 bytes, but no minimum.

-- 
Paul Theodoropoulos
www.anastrophe.com


-- 
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

-- 
Paul Theodoropoulos
www.anastrophe.com
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general


-- 
Paul Theodoropoulos
www.anastrophe.com

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general