Plugins for nagios used by Voxer, made specifically for SmartOS
Check bash for CVE-2014-6271 (shellshock)
$ check_shellshock
ok: bash is secure against shellshock
You can pass an optional binary to check as the first argument, defaults to bash in your $PATH
$ check_shellshock /bin/bash
critical: /bin/bash is vulnerable to shellshock
$ check_shellshock ./out/bin/bash
ok: ./out/bin/bash is secure against shellshock
Check the age of the SmartOS kernel version
$ check_kernel_version
warning: joyent_20140530T010428Z - 6 months old (195 days)
Pass arguments to modify warn and crit thresholds (respectively) in days
$ check_kernel_age 300 600
ok: joyent_20140530T010428Z - 6 months old (195 days)
Check for services in SMF that are not functioning properly
$ check_svcs
ok: all services are online
Check kstat for hard errors - useful for identifying failing hardware
$ check_hard_errors
ok: no hard errors found
Look for flapping services in SMF (rapidly restarting services)
$ check_flapping_services
ok: no flapping services detected
If a service is flapping it will exit with critical status and print the service name(s)
$ check_flapping_services
critical: flapping services found, svc:/application/voxer/dave-process:default
Like check_disk for memory usage using kstat to calculate used memory
$ check_mem -w 90 -c 95
ok: 7% used (warning=90%, critical=95%)|mem_used=303812608;mem_cap=4294967296
Like check_mem, but checks to see if you are over the memory allocated for your zone
$ check_mem_cap
ok: nover is 0|nover=0
Like check_mem for disk utilization
$ check_disk_busy -w 90 -c 95 sd1
ok: disk 1% busy (warning=90%, critical=95%, disk=sd1)|disk_busy=1
The final argument is the disk name to check (defaults to sd1), if
you supply an invalid name, a list of all disks will be printed to
stderr.
Count and alert on the number of running processes. The benefit of this check
over the built-in check_proc is that this script only does process count, so
it is fast, and also does not require escalated privileges.
$ ./check_proc_count -w 200 -c 400
ok: 37 processes running|proc_count=37
Look for running processes with an invalid or removed UID. This is usually
a sign that an automatically generated user from something like pkgin has
been clobbered by configuration management software.
$ check_proc_owners
critical: 2 processes found without valid UIDs
$ check_proc_owners -v
critical: 2 processes found without valid UIDs
pid 47247 (uid 2033): sh
pid 47251 (uid 2033): node server.js v
Supply -v for verbose output, suitable for interactive use.
Run any script that outputs perf data at the end with a -n switch
to suppress that output.
LICENSE - "MIT License" Copyright (c) 2007-2014 Voxer LLC. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.