• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: nagios and unresponsive wotaskd?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nagios and unresponsive wotaskd?


  • Subject: Re: nagios and unresponsive wotaskd?
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 3 Dec 2010 10:49:51 -0800

On Dec 3, 2010, at 10:48 AM, Pascal Robert wrote:
> Le 2010-12-03 à 13:26, Ray Kiddy a écrit :
>
>>
>> Hello -
>>
>> We have a suite of nagios services that we are using to track various things about our WebObjects apps. One piece of it is noisier than others and I am curious if others see the same things.
>>
>> I have a simple HTTP check on port 1085 on our application nodes and those services are always flapping. We have larger problems with the responsiveness of some pieces of our architecture, and I am trying to figure out better ways to track what is going on. And it is not clear that if the wotaskd is having problems responding, that this leads directly to the problems we are having. I suspect that the wotaskd being unresponsive is one of the secondary symptoms. But one never knows.
>>
>> I think that when we transition to better versions of the deployment management apps (yes, we are still using Apple's, lame as they are), this will probably get easier.
>>
>> If anyone has a service to watch wotaskd output, what has been learned about how to check it? I have set the timeout higher than I think I should. I want to parse the output and find more intelligent indicators, but if the processes are not even responding to requests, why bother? Does anyone use nagios to connect to a JavaMonitor? I cannot decide if that is going to be either a good idea or worthwhile.
>
> We also check wotaskd by doing a simple check on port 1085 with the "check_http" plugin and we don't get the same behavior that you describe. We do have a couple of timeouts per year, and every time, it's because of an application's instance who gone rogue and wotaskd is too busy trying to talk to that instance.


A hung / busy instance would be my guess as well.  wotaskd does not do well in that situation.


Chuck

--
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects







Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >nagios and unresponsive wotaskd? (From: Ray Kiddy <email@hidden>)
 >Re: nagios and unresponsive wotaskd? (From: Pascal Robert <email@hidden>)

  • Prev by Date: Re: nagios and unresponsive wotaskd?
  • Next by Date: Re: Timestamps and PostgreSQL
  • Previous by thread: Re: nagios and unresponsive wotaskd?
  • Next by thread: ERXResponseRewriter.Delegate not used by WOImage
  • Index(es):
    • Date
    • Thread