Check a server is up. If it isn't mail me.
An email saying "brandx.jp.sme ping failed"
3 Alternatives + Submit Alt
-
Alternative to the ping check if your firewall blocks ping. Uses curl to get the landing page silently, or fail with an error code. You can probably do this with wget as well. Show Sample Output
2curl -fs brandx.jp.sme 2&>1 > /dev/null || echo brandx.jp.sme ping failed | mail -ne -s'Server unavailable' joker@jp.co.uk -
For some reason the 2&>1 does not work for me, but the shorter stdout/stderr redirection >& works perfectly (Ubuntu 10.04).
2ping -q -c1 -w3 server.example.com >& /dev/null || echo server.example.com ping failed | mail -ne -s'Server unavailable' admin@example.com -
This version uses netcat to check a particular service.
1nc -zw2 www.example.com 80 || echo http service is down | mail -s 'http is down' admin@example.com
What do you think?
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
What's this?
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Similar Commands
Stay in the loop…
- Follow the Tweets.
-
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10 - Subscribe to the feeds.
-
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
>all a b 1ls: cannot access b: No such file or directory ls: cannot access 1: No such file or directory -rw-r--r-- 1 splante 20000 0 Apr 7 18:08 a# your way just creates a file named 1 with stderrll a b 2&>1 >/dev/nullcat 1ls: cannot access b: No such file or directory ls: cannot access 2: No such file or directoryrm 1# this doesn't send stderr to /dev/nullll a b 2>&1 >/dev/nullls: cannot access b: No such file or directoryll a b 1ls: cannot access b: No such file or directory ls: cannot access 1: No such file or directory -rw-r--r-- 1 splante 20000 0 Apr 7 18:08 a # both of these work as expectedll a b >/dev/null 2>&1ll a b >& /dev/nullwhile true; do /bin/ping -q -c1 -w3 8.8.8.8 2&>1 /dev/null || echo "8.8.8.8 ping failed at $(date +%D) $(date +%H:%M:%S)" >> /var/log/ping.log; sleep 10; done &both 2&>1 and 2>&1 are same for me