[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ping issues

From: Paul Theodoropoulos
Subject: ping issues
Date: Wed, 16 May 2018 20:45:13 -0700
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0

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).

address@hidden: ~ # ping -c1 -s 1
PING ( 1(29) bytes of data.
9 bytes from ( icmp_seq=1 ttl=42

--- 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
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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]