{"id":876,"date":"2012-07-04T10:47:10","date_gmt":"2012-07-04T02:47:10","guid":{"rendered":"http:\/\/www.computersolutions.cn\/blog\/?p=876"},"modified":"2012-07-04T11:02:50","modified_gmt":"2012-07-04T03:02:50","slug":"sysfence-updates-for-debian-startup-script-and-makefile-fix","status":"publish","type":"post","link":"https:\/\/www.computersolutions.cn\/blog\/2012\/07\/sysfence-updates-for-debian-startup-script-and-makefile-fix\/","title":{"rendered":"sysfence updates for debian (startup script, and makefile fix)"},"content":{"rendered":"

A while ago I wrote a post about sysfence. http:\/\/www.computersolutions.cn\/blog\/2010\/12\/debian-system-load-monitoring\/<\/a> <\/p>\n

As it really was a while ago, I’ll recap quickly.<\/p>\n

Sysfence is a small, light system monitoring app that has a nice heavy hand. If load goes over user defined limits, it will kill processes specified in its config (with extreme prejudice), and only start them up again once load is back under a certain level.<\/p>\n

Got that?<\/p>\n

Ok.<\/p>\n

sysfence is rather good at what it does, fits my needs, so I’ve continued to use it over the years. One of the things I never got around to doing was making a startup script for it – this is mostly as it works as advertised – i’ve had zero issues!<\/p>\n

That said, someone finally called my bluff and asked me for my startup script, which of course, I didn’t have, so I made one this morning.<\/p>\n

The script is debian biased, and depends on where you installed sysfence.<\/p>\n

You’ll need 3 files as below. Change settings to your needs.<\/p>\n

1) Basic settings for sysfence<\/p>\n

\/etc\/default\/sysfence<\/p>\n


\nSYSFENCE_ENABLE=true #Are we enabled (er, yes!)
\nDAEMON_OPTS=\" \/etc\/sysfence\/sysfence.conf\" #Where is our ruleset
\nMAILTO=\"root\" #Who to call in case of issues.
\n<\/code><\/p>\n

2) Config file for sysfence<\/p>\n

\/etc\/sysfence\/sysfence.conf<\/p>\n


\n#[Your sysfence watch rules goes here]
\n#My example below<\/p>\n

rule \"Apache\" {
\n la1 >= 6.00 or la5 >= 3.5
\n}
\nrun '\/usr\/sbin\/apache2ctl stop; sleep 120; \/usr\/sbin\/apache2ctl start'
\nrule \"warning\" { la1 >= 6.00 } run once 'echo \"Load High: $HOSTNAME\" | mail $MAILTO'
\n<\/code><\/p>\n

3) Debian Startup script<\/p>\n


\n#!\/bin\/sh
\n### BEGIN INIT INFO
\n# Provides: sysfence
\n# Required-Start: $local_fs $remote_fs
\n# Required-Stop: $local_fs $remote_fs
\n# Should-Start: $network
\n# Should-Stop: $network
\n# Default-Start: 2 3 4 5
\n# Default-Stop: 0 1 6
\n# Short-Description: Daemonized version of sysfence
\n# Description: Starts the sysfence daemon
\n# \/etc\/default\/sysfence.
\n### END INIT INFO
\n# Author: L. Sheed<\/p>\n

#The complete default command that is being run is:
\n#sysfence \" \/etc\/sysfence\/sysfence.conf\"
\n#obviously this will change with your variables,
\n#but the entire command is here for testing
\n# uses \/etc\/default\/sysfence<\/p>\n

NAME=\"sysfence\"
\nSYSFENCE_ENABLE=false
\nDESC=\"sysfence Daemon\"<\/p>\n

DAEMON=`which sysfence`
\nDAEMON1=\"sffetch\"
\nDAEMON2=\"sfwatch\"
\nLOGFILE=\"\/var\/log\/sysfence.log\"<\/p>\n

test -x $DAEMON || exit 0<\/p>\n

if [ ! -e \"${LOGFILE}\" ]
\nthen
\n touch \"${LOGFILE}\"
\n chmod 640 \"${LOGFILE}\"
\n chown root:adm \"${LOGFILE}\"
\nfi<\/p>\n

. \/lib\/lsb\/init-functions<\/p>\n

if [ -f \/etc\/default\/$NAME ]; then
\n . \/etc\/default\/$NAME
\n case \"x$SYSFENCE_ENABLE\" in
\n xtrue|x1|xyes)
\n SYSFENCE_ENABLE=true
\n ;;
\n *)
\n SYSFENCE_ENABLE=false
\n exit 1;
\n ;;
\n esac
\nfi<\/p>\n

case \"$1\" in
\n start)
\n PID=`ps aux | grep \"$DAEMON1 \" | grep -v grep | awk '{print $2}'`
\n if [ \"x$PID\" != \"x\" ]; then
\n echo `date` \" * $NAME appears to be already running!\" | tee -a $LOGFILE
\n exit
\n fi
\n if $SYSFENCE_ENABLE; then
\n echo \"Starting $DESC\"
\n log_daemon_msg \"Starting $DESC\" \"$NAME\"
\n $DAEMON $DAEMON_OPTS<\/p>\n

PID=`ps aux | grep \"$DAEMON1 \" | grep -v grep | awk '{print $2}'`
\n echo \" * $NAME PID is $PID\"
\n echo \"Watching:\"
\n ps -ef | grep \"$DAEMON2 \" | grep \"$PID\"
\n else
\n log_warning_msg \"Not starting $DESC $NAME, disabled via \/etc\/default\/$NAME\"
\n fi
\n ;;<\/p>\n

stop)
\n if $SYSFENCE_ENABLE; then
\n PID=`ps aux | grep \"$DAEMON1 \" | grep -v grep | awk '{print $2}'`
\n if [ \"x$PID\" = \"x\" ]; then
\n echo \" * $NAME is not running\"
\n else
\n echo \" Stopping $NAME\"
\n log_daemon_msg \"Stopping $DESC\" \"$NAME\"
\n kill $PID
\n fi
\n fi
\n ;;<\/p>\n

status)
\n PID=`ps aux | grep \"$DAEMON1 \" | grep -v grep | awk '{print $2}'`
\n if [ \"x$PID\" = \"x\" ]; then
\n echo \" * $NAME is not running\"
\n else
\n echo \" * $NAME PID is $PID\"
\n echo \"Watching:\"
\n ps -ef | grep \"$DAEMON2 \" | grep \"$PID\"
\n fi
\n ;;<\/p>\n

*)
\n N=\/etc\/init.d\/$NAME
\n echo \"Usage: $N {start|stop|status}\" >&2
\n exit 1
\n ;;
\nesac<\/p>\n

exit 0; <\/p>\n

<\/code><\/p>\n

You can download the init script here – sysfence init script for debian<\/a><\/p>\n

Yikes, I almost forgot the other bit of this post. Tsk tsk…<\/p>\n

The makefile doesn’t make in some of my servers. Its probably that dash shell expansion breaks stuff vs bash, but haven’t investigated it properly.<\/p>\n

This is a simple fix <\/p>\n

open up the makefile and change the expansion stuff to explicitly list the .o files.<\/p>\n

eg<\/p>\n

Makefile says:<\/p>\n

CC=gcc
\nLDFLAGS=
\nCFLAGS=-Wall -O2
\nobjects=conditions.o getstats.o mainloop.o cp2memory.o datastruct.o sysfence.o
\nparseopt=parseopt\/{confread,lex,parse}.o
\nsys=sys\/{exit,xalloc,log,communication,sighandlers,processtitle,users}.o
\n... (rest of the file)
\n<\/code><\/p>\n

Change to:<\/p>\n


\nCC=gcc
\nLDFLAGS=
\nCFLAGS=-Wall -O2
\nobjects=conditions.o getstats.o mainloop.o cp2memory.o datastruct.o sysfence.o
\nparseopt=parseopt\/confread.o parseopt\/lex.o parseopt\/parse.o
\nsys=sys\/exit.o sys\/xalloc.o sys\/log.o sys\/communication.o sys\/sighandlers.o sys\/processtitle.o sys\/users.o
\n... (rest of the file)
\n<\/code><\/p>\n

make clean<\/p>\n

and<\/p>\n

make<\/p>\n

Simple!<\/p>\n","protected":false},"excerpt":{"rendered":"

A while ago I wrote a post about sysfence. http:\/\/www.computersolutions.cn\/blog\/2010\/12\/debian-system-load-monitoring\/ As it really was a while ago, I’ll recap quickly. Sysfence is a small, light system monitoring app that has a nice heavy hand. If load goes over user defined limits, it will kill processes specified in its config (with extreme prejudice), and only start […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[4],"tags":[421,258,423,422,303],"class_list":["post-876","post","type-post","status-publish","format-standard","hentry","category-useful-info","tag-bash","tag-debian","tag-script","tag-startup","tag-sysfence"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/876","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/comments?post=876"}],"version-history":[{"count":5,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/876\/revisions"}],"predecessor-version":[{"id":880,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/876\/revisions\/880"}],"wp:attachment":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/media?parent=876"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/categories?post=876"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/tags?post=876"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}