Question
AMEX
US
Last activity: 11 May 2018 16:13 EDT
How to Debug PEGA0010 : Agent Disabled issue
Today morning in our production environment, on one of the nodes, some OOTB agents went down and restarted automatically.
Logs show:
Agent [Pega-RULES] activity [Code-.SystemPulse] queue number [1] terminated manually ErrorMsg: Terminated manually.
We can see alert PEGA0010 in Alert log. No other information is available in Pega rules and Alert Logs.
Agents were automatically restarted before we could check the exceptions on Agent Management in SMA.
What is the best way to find out what cased the issue.
Thanks,
Sumanth
Accepted Solution
Pegasystems Inc.
US
I believe "Terminated manually" suggests that a person went in and disabled the agent themselves (otherwise it would have said it was disabled due to execution errors). If you don't see any errors in the logs, that would be my guess as to what happened.
PEG
GB
Where/how exactly did you see that agent were down?
The system pulse is used by Pega cluster technology to check if a node is live.
If the system pulse is not working, the Pega cluster could believe this node is down. I wonder if this could result in the agent landing page showing agent being down when in fact they are up.
Try to double-check these agents were really down.
AMEX
US
We have AES configured to monitor the servers and we received an alert from AES when the agent was down.
Later we checked the logs and we could see the Pega-RULES and ALERTs logs with the agent down message.
Is there any way to get agent execution history like when it started, stopped?? (Reason it got stopped).
Accepted Solution
Pegasystems Inc.
US
I believe "Terminated manually" suggests that a person went in and disabled the agent themselves (otherwise it would have said it was disabled due to execution errors). If you don't see any errors in the logs, that would be my guess as to what happened.