ping issues
Paul Theodoropoulos <[email protected]>
| Newsgroups | gmane.comp.monitoring.monit.general |
|---|---|
| Organization | Syntactically Subversive Services |
| Message-ID | <[email protected]> |
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