SMART (Smart Monitoring and Rebooting Tool)
Listing 2. sudo Configured for SMART Access
# Defaults specification Defaults:root !syslog # User privilege specification root ALL=(ALL) ALL sysman server=(root) NOPASSWD: /home/sysman/check-service sysman server=(root) NOPASSWD: /sbin/reboot
This way, we disable syslog logging when sudo is executed by user root, and we assign root privileges to user sysman, at the host server, only for the execution of commands /home/sysman/check-service and /sbin/reboot, without asking sysman for the password every time.
Through the PID file defined in the configuration file, we obtain the parent process identifier (PID), and we determine the number of active processes generated by this service. Next we check whether:
The service is responding to petitions within the defined time period.
The number of processes generated by the service doesn't exceed the maximum and minimum defined thresholds.
Considering the results obtained in former verifications, we classify the service status:
0: service is responding to requests within the defined time period, the number of processes generated by service remains between the defined thresholds, and the information provided by the PID file is correct.
1: service is responding to requests within the defined time period and the number of processes generated by service remains between the defined thresholds, but either the information provided by the PID file is incorrect or this file doesn't exist, even though it has been defined.
2: service is responding to requests within the defined time period, but the number of processes generated by the service is beyond the defined thresholds (this could be the case of an overloaded but operative Web server).
3: the number of generated processes is out of thresholds, and we don't have any tool (script) to check whether the service is operative (this could be the case of processes such as syslogd, crond and xinetd).
4: service is not responding to requests within the defined time period.
We group the above five situations in three more general cases:
OK (status 0 and 1).
WARN (status 2).
DOWN (status 3 and 4).
When executing the program with no parameters, it simply will determine the status of services defined in the configuration file and will display the results. If we want the program to work in an active way, we need to use some of the following parameters:
-w: restart services in WARN status and send a notification (e-mail) for each one of them.
-d: restart services in DOWN status and send a notification for each one of them.
-wd: restart services in WARN and DOWN status and send a notification for each one of them.
--all: restart all services independently of their status and send a notification for each service with WARN or DOWN status.
--reboot: restart the whole system independently of service's status and send a general notification.
Once the service status has been determined, and according to the parameter specified in the execution, the action carried out for each service will consist of that shown in Table 1.
Table 1. Service Actions
|OK||--all||Restart the service|
|WARN||-w, -wd, --all||Restart the service|
|Send a notification relating to service|
|-d||Send a notification relating to service|
|DOWN||-d, -wd, --all||Restart the service|
|Send a notification relating to service|
Furthermore, independently of the service's status, with the parameters --all and --reboot, a notification via e-mail is sent to the administrator about the performed action.
Listing 3 shows a sample of SMART in action, executed from a console with parameter -d (recovery of services in DOWN status).
Webinar: 8 Signs You’re Beyond Cron
On Demand NOW
Join Linux Journal and Pat Cameron, Director of Automation Technology at HelpSystems, as they discuss the eight primary advantages of moving beyond cron job scheduling. In this webinar, you’ll learn about integrating cron with an enterprise scheduler.View Now!
|Chrome-Colored Parakeets||May 05, 2015|
|Mumblehard--Let's End Its Five-Year Reign||May 04, 2015|
|An Easy Way to Pay for Journalism, Music and Everything Else We Like||May 04, 2015|
|When Official Debian Support Ends, Who Will Save You?||May 01, 2015|
|May 2015 Issue of Linux Journal: Cool Projects||May 01, 2015|
|May 2015 Video Preview||May 01, 2015|
- Mumblehard--Let's End Its Five-Year Reign
- An Easy Way to Pay for Journalism, Music and Everything Else We Like
- When Official Debian Support Ends, Who Will Save You?
- Ubuntu Ditches Upstart
- "No Reboot" Kernel Patching - And Why You Should Care
- Video On Demand: 8 Signs You're Beyond Cron
- DevOps: Better Than the Sum of Its Parts
- May 2015 Issue of Linux Journal: Cool Projects
- Picking Out the Nouns
- Return of the Mac