hi
From: Fabrizio Di Meo [mailto:fabriziodimeo@yahoo.it] Hi,
I've just a question about Apache 1.3.20 release 66 which should fix the last vulnerability (at least the last one I knew about).
Despite my package updating I go on to check continuos crashes of my web server due to some tcp scanning to the port 80.
Has someone checked this problem or ... I'm in error?
I have had some similar problems. I use a self-compiled Apache 1.3.26 with PHP 4.2.2, which used to crash every now and then. That's why I set up a cronjob to survey the Apache processes and, in case of Apache not running, restarting Apache. I know it's fighting symptoms, but I don't have the time right now to search for the cause. It's on my TODO-list for the next 2 months ...
Thank you,
Fabrizio.
regards, Stefan The crontab-entry: 0-59/5 * * * * /my_tools/processchecker.sh /usr/local/apache/bin/httpd Here's the script I use: webserver:~ # cat /my_tools/processchecker.sh #!/bin/sh BINARY=$1; LOGFILE="/var/log/processchecker.log"; DATE=`/bin/date`; MAILTO=stefan.peer@tiwag.at CC=XXXXX@somwhere.in.the.net HOST=`hostname -f`; RCDIR="/etc/init.d"; if [ -z $BINARY ] ; then echo "Usage: $0 <binary>"; exit 1; fi RCSCRIPT=`find $RCDIR -type f -exec grep -H "$BINARY" {} \; | awk -F":" '{print $1}' | uniq` #if [ -z $RCSCRIPT ]; then # RCSCRIPT=/etc/rc.d/`basename $BINARY`; #fi START_CMD="$RCSCRIPT start"; STOP_CMD="$RCSCRIPT stop"; STATUS_CMD="/sbin/checkproc $BINARY"; if $STATUS_CMD ; then echo "$DATE: $BINARY is up and running" >> $LOGFILE; else echo -n "$DATE: $BINARY not running. Starting $BINARY ...." >> $LOGFILE; if $START_CMD ; then echo "done." >> $LOGFILE; MESSAGE="$BINARY started successfully" else echo "failed." >> $LOGFILE; echo "Yikes, $BINARY could not be started on $HOST!"; MESSAGE="Yikes, $BINARY could not be started on $HOST!" fi echo $MESSAGE | mail -s "$0 - $BINARY not running on $HOST" $MAILTO -c $CC fi exit 0;