![]() It took me quite some time to write this down, and i'd really appreciate if you could take at least the same amount of time reading this. So if you run into problems, please read this tutorial again and make sure you really followed it to the point. PLEASE don't email me as soon as you hit some wall when you try to implement this. This is all there is to this healthcheck setup. Same as on Server1 just using a different email address to send the pings to. These will be similar on both of the servers.Īdd the foollowing line to your Router-Records on both servers:ĥ,35 * * * * root echo "ping" | /usr/bin/mail -s ping check pings received from server1ħ,37 * * * * root /var/CommuniGate/apps/pings.sh You need to configure 2 Special Router Entries on both servers. Let us also assume, that healthckeck interval of 30 Minutes is good enough for us. ![]() This method involves the usage of cron, a shell script to analyze the received "ping" emails and the CGPro PIPE-Module and a perl script to "pipe" the received emails directly to a file on the server's HardDisk instead of a real Mailbox.įor this Tutorial, let us assume you have two CGPro Servers, called: and which handle email for these two domains respectively. This method - which uses real emails instead of just connecting to the email-servers ports (25 for SMTP for example) - has the benefit, that it can reliably alert you in case of a "stuck" Queue, where a simple connection to port 25 would still work.Ī stuck Queue is most often caused by a crashed or hung external helper. If one of the servers doesn't receive such a "ping" email, it alerts me via SMS. This Healtchcheck works by using a pair of CGP Servers which email each other on given intervals.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |