Good questions - I've had it in shared pools and it's own pool. It never shows up. We are getting set to export/re-import it. There's SOX rules so any of that sort of work requires paperwork, etc. Naturally the Production system is broken and not the dev one where I can tinker. Dev works just fine.
William Rentfrow Principal Consultant, StrataCom Inc. wrentf...@stratacominc.com Corporate Website, www.stratacominc.com Blog, www.williamrentfrow.com 715-410-8156 C -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W Sent: Tuesday, May 25, 2010 9:58 AM To: arslist@ARSLIST.ORG Subject: Re: Escalation refuses to run Out of curiosity... What happens if you swap this escalation's pool with another (i.e. take pool 5's escalations and move them to pool 6 and put this in pool 5)? The second test is to export this escalation to a def file and then re-import it. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of William Rentfrow Sent: Tuesday, May 25, 2010 9:53 AM To: arslist@ARSLIST.ORG Subject: Escalation refuses to run ** I'm baffled. Tech support at BMC seems baffled as well. The OOB escalation for SLM is named SLM:EventSchedule:TAD_PollingEscalation. It has not been modified at all except for the thread/pool changes noted below. It is an interval escalation set to 5 minutes. It refuses to fire however. There is simply no mention of it in the logs. Ever. We'd added a dedicated thread - in fact, we have 6 escalations threads/pools. #6 is dedicated solely for this escalation - nothing else is on it. Escalation logging shows all the other escalations working correctly. But for some reason Pool 6 is never mentioned in the logs and the escalation named above is never mentioned. There is no message saying the escalation is disabled - there's nothing saying it is computing the next fire time - it is literally as if this escalation doesn't exist as far as the server is concerned. Suggestions? So far we have... -bounced the server. Repeatedly. -thread level logging -every other kind of logging imaginable -restricted pool to this single escalation -verified pool configuration, etc -verified server licensing, etc. William Rentfrow Principal Consultant, StrataCom Inc. wrentf...@stratacominc.com Corporate Website, www.stratacominc.com Blog, www.williamrentfrow.com 715-410-8156 C _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
