9e246ac3d8
zed monitors ZFS events. When a zevent is posted, zed will run any scripts that have been enabled for the corresponding zevent class. Multiple scripts may be invoked for a given zevent. The zevent nvpairs are passed to the scripts as environment variables. Events are processed synchronously by the single thread, and there is no maximum timeout for script execution. Consequently, a misbehaving script can delay (or forever block) the processing of subsequent zevents. Plans are to address this in future commits. Initial scripts have been developed to log events to syslog and send email in response to checksum/data/io errors and resilver.finish/scrub.finish events. By default, email will only be sent if the ZED_EMAIL variable is configured in zed.rc (which is serving as a config file of sorts until a proper configuration file is implemented). Signed-off-by: Chris Dunlap <cdunlap@llnl.gov> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Issue #2
82 lines
2.3 KiB
Bash
Executable File
82 lines
2.3 KiB
Bash
Executable File
#!/bin/sh
|
|
#
|
|
# Send email to ZED_EMAIL in response to a DATA zevent.
|
|
# Only one message per ZED_EMAIL_INTERVAL_SECS will be sent for a given
|
|
# class/pool combination. This protects against spamming the recipient
|
|
# should multiple events occur together in time for the same pool.
|
|
# Exit codes:
|
|
# 0: email sent
|
|
# 1: email failed
|
|
# 2: email suppressed
|
|
# 3: missing executable
|
|
# 4: unsupported event class
|
|
# 5: internal error
|
|
# State File Format:
|
|
# POOL:TIME_OF_LAST_EMAIL
|
|
#
|
|
test -f "${ZED_SCRIPT_DIR}/zed.rc" && . "${ZED_SCRIPT_DIR}/zed.rc"
|
|
|
|
test -n "${ZEVENT_POOL}" || exit 5
|
|
test -n "${ZEVENT_SUBCLASS}" || exit 5
|
|
|
|
if test "${ZEVENT_SUBCLASS}" != "data"; then \
|
|
logger -t "${ZED_SYSLOG_TAG:=zed}" \
|
|
-p "${ZED_SYSLOG_PRIORITY:=daemon.warning}" \
|
|
`basename "$0"`: unsupported event class \"${ZEVENT_SUBCLASS}\"
|
|
exit 4
|
|
fi
|
|
|
|
# Only send email if ZED_EMAIL has been configured.
|
|
test -n "${ZED_EMAIL}" || exit 2
|
|
|
|
# Ensure requisite executables are installed.
|
|
if ! command -v "${MAIL:=mail}" >/dev/null 2>&1; then
|
|
logger -t "${ZED_SYSLOG_TAG:=zed}" \
|
|
-p "${ZED_SYSLOG_PRIORITY:=daemon.warning}" \
|
|
`basename "$0"`: "${MAIL}" not installed
|
|
exit 3
|
|
fi
|
|
|
|
NAME="zed.${ZEVENT_SUBCLASS}.email"
|
|
LOCKFILE="${ZED_LOCKDIR:=/var/lock}/${NAME}.lock"
|
|
STATEFILE="${ZED_RUNDIR:=/var/run}/${NAME}.state"
|
|
|
|
# Obtain lock to ensure mutual exclusion for accessing state.
|
|
exec 8> "${LOCKFILE}"
|
|
flock -x 8
|
|
|
|
# Query state for last time email was sent for this pool.
|
|
TIME_NOW=`date +%s`
|
|
TIME_LAST=`egrep "^${ZEVENT_POOL}:" "${STATEFILE}" 2>/dev/null | cut -d: -f2`
|
|
if test -n "${TIME_LAST}"; then
|
|
TIME_DELTA=`expr "${TIME_NOW}" - "${TIME_LAST}"`
|
|
if test "${TIME_DELTA}" -lt "${ZED_EMAIL_INTERVAL_SECS:=3600}"; then
|
|
exit 2
|
|
fi
|
|
fi
|
|
|
|
"${MAIL}" -s "ZFS ${ZEVENT_SUBCLASS} error for ${ZEVENT_POOL} on `hostname`" \
|
|
"${ZED_EMAIL}" <<EOF
|
|
A ZFS ${ZEVENT_SUBCLASS} error has been detected:
|
|
|
|
eid: ${ZEVENT_EID}
|
|
host: `hostname`
|
|
time: ${ZEVENT_TIME_STRING}
|
|
pool: ${ZEVENT_POOL}
|
|
EOF
|
|
MAIL_STATUS=$?
|
|
|
|
# Update state.
|
|
egrep -v "^${ZEVENT_POOL}:" "${STATEFILE}" 2>/dev/null > "${STATEFILE}.$$"
|
|
echo "${ZEVENT_POOL}:${TIME_NOW}" >> "${STATEFILE}.$$"
|
|
mv -f "${STATEFILE}.$$" "${STATEFILE}"
|
|
|
|
if test "${MAIL_STATUS}" -ne 0; then
|
|
logger -t "${ZED_SYSLOG_TAG:=zed}" \
|
|
-p "${ZED_SYSLOG_PRIORITY:=daemon.warning}" \
|
|
`basename "$0"`: "${MAIL}" exit="${MAIL_STATUS}"
|
|
exit 1
|
|
fi
|
|
|
|
exit 0
|