Do a "w" on the box to see how long it's been online, and whether that
corresponds with when you know the AppServer went offline. It would interest
me to know if this is what happened, because if AppServer just dies, there's
something really wrong.
> From: barknech@...
> Date: Tue, 7 May 2002 22:12:13 +0200
> To: webware-discuss@...
> Subject: Re: [Webware-discuss] Restarting AppServer automatically
> Ben Parker hat gesagt: // Ben Parker wrote:
>> The reason for this is that a crashed live AppServer should never
>> happen, so when it does it usually means there is some seriously
>> wrong code running, or something malicious going on, and I would
>> rather identify the problem, restart manually, than restart in a
>> chaotic situation. I just don't like running anything that could
>> possibly mask a fatal error.
> You're right, that is of course the thing to do after a crash. But in
> my current situation there probably was another more simple reason for
> the AppServer to disapear: I have to start the AppServer by hand, and
> I suspect, that the machine was simply rebooted or something like
> that, and the AppServer couldn't start again without my intervention.
> Must talk to the admin...
> I now installed a simple shell skript that mails me, if the AppServer
> needs a restart:
> if ! ps $(cat $PIDFILE ) >& /dev/null;
> echo Appserver died on `date` | mutt -s "[Alert] Appserver died" $MAILTO
> In the crontab this is needed:
> 10 * * * * checkappserver.sh
> For my needs, this is sufficient now, as my site has not much traffic.
> I even use a selfmade webware CMS that stores its entries as
> cPickles... ;)
> Next I'll take a look at Monitor.py, also because I think, that an
> application, that needs an AppServer, also needs a tool, that rings
> the alarm, if the vital AppServer goes away.
> Frank Barknecht _ _______footils__
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: bandwidth@...
> Webware-discuss mailing list