check for crash?
Israel Brewster
israel at frontierflying.com
Mon Nov 24 19:42:03 CET 2008
On Nov 21, 2008, at 10:07 AM, Fernando Rocha wrote:
> Hi Israel,
>
> I think that by the check_process is hard to identify this issue,
> because as you said the process still running and just stop to work.
>
> How do you know when it crashes?
> Is there some log occurrences?
> Does it gives some errors on the web page?
The applet in question is a status display screen. I know it has
crashed because a) the data displayed is out of date, and b) it
doesn't respond to user input. Since it is a passive monitoring
system, there is no log written. No error is displayed, it just stops
updating properly. I guess what I was hoping for was that there might
be some indication I could get from the process list or the like that
I simply didn't know to look for, rather than an application-specific
check. Something along the lines of how you can check for a "zombie"
process by looking at the output of a ps. From the responses I have
gotten so far, however, this wouldn't appear to be the case. Thanks
anyway!
-----------------------------------------------
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
-----------------------------------------------
>
>
> --
> Fernando Rocha <fernando.rocha at opservices.com.br>
> Analista de Suporte - Operação
> OpServices - Porto Alegre - RS - Brasil
> +55 51 3275.3588
> www.opservices.com.br
> www.opmon.org
>
> ----- "Israel Brewster" <israel at frontierflying.com> wrote:
>
>> I'm wondering if anyone can give me suggestions as to how to
>> monitor a
>>
>> specific process to make sure it keeps running properly. The specific
>>
>> issue I have is that I have a Java Webstart applet running on OpenBSD
>>
>> 4.4 that, from time to time, randomly crashes. I can't just use
>> check_process (I don't think so, at least) because when it "crashes"
>>
>> the process never actually exits- it just stops working. I have to go
>>
>> in and manually kill it before I can restart it. Does anyone have any
>>
>> thoughts as to how I could check for this situation? I realize this
>> may not strictly be a nagios question, and I apologize to anyone who
>>
>> is bothered by that, but since I would be doing the monitoring with
>> Nagios this seemed the most logical place I could think of to ask.
>> Thanks!
>>
>> -----------------------------------------------
>> Israel Brewster
>> Computer Support Technician
>> Frontier Flying Service Inc.
>> 5245 Airport Industrial Rd
>> Fairbanks, AK 99709
>> (907) 450-7250 x293
>> -----------------------------------------------
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Nagios-users mailing list
>> Nagios-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>> ::: Please include Nagios version, plugin version (-v) and OS when
>> reporting any issue.
>> ::: Messages without supporting info will risk being sent to /dev/
>> null
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list