We have an issue, in the stdlog shows many errors to animator, this problem impact in the performance server.
Could you help how is the best form to eliminate this message in the logs?
Thanks and regards,
What specific messages do you see in the STDLOGs?
Are you running SDM in conventional (primary/secondary) or AA (background/standby) architecture?
Do you have a dedicated DOMSRVR for the animator process? If not, please refer to Creating a dedicated Domsrvr to the Animator Proce - CA Knowledge
2471 Recurring animator ANI:574509316 (iss:917343) for atev:127847397 missed 1 firings, the first at 02/22/2018 15:45:18animator_nxd 7364 ERROR animator_nxd.c 2471 Recurring animator ANI:574509315 (iss:873634) for atev:126452432 missed 1 firings, the first at 02/22/2018 15:45:18animator_nxd 7364 ERROR animator_nxd.c 2471 Recurring animator ANI:574462732 (iss:909512) for atev:127608357 missed 1 firings, the first at 02/22/2018 15:45:18animator_nxd 7364 ERROR animator_nxd.c 2471 Recurring animator ANI:574462736 (iss:929657) for atev:128237634 missed 1 firings, the first at 02/22/2018 15:45:18animator_nxd 7364 ERROR animator_nxd.c 2471 Recurring animator ANI:574509318 (iss:930817) for atev:128272296 missed 1 firings, the first at 02/22/2018 15:45:18animator_nxd 7364 ERROR animator_nxd.c 2471 Recurring animator ANI:574509320 (iss:910657) for atev:127646056 missed 1 firings, the first at 02/22/2018 15:45:18
Gabriel, I think you would need to exam why the firings keep missing. For example, is atev:127646056 still present in the mdb? If not, then this atev will continue missing firing and if you have a lot then the stdlog will be filled with such errors. Then the question becomes why it is not present in mdb...like manually delete from mdb? or this mdb was migrated/moved from another install? Thanks _Chi
From my experience, errors like these aren't necessarily the cause of your noted performance issues - they may be a symptom. If the system is busy processing a ton of information (e.g. there's a lot of activity going on, a large pdm_load is happening, archive & purge is running, etc.), it may slow down and miss its' intended fire times for scheduled events. I've also seen this kind of message occur when SLAs are configured and a ticket with a large number of children is closed - the animator suddenly has hundreds (or more) events to process, and can't handle them all on time.
If you're seeing "missed 1 firings" frequently, but don't see the same event get missed 2 or more times, it might indicate that you're having the server do too much work with too few resources - it's still processing everything, just at a bit of a delay. For that situation, double-check that you meet or exceed the minimum hardware and software requirements, and consider increasing the number of servers in your environment if you have a lot of activity on a small number of servers. If you're seeing the same events miss their fire time multiple times each, then that could indicate that the animator isn't processing fast enough to keep up with demand - setting up an animator-specific domsrvr as Paul noted earlier may help here (though again, make sure your server has enough resources to do this).
Since this is likely more of a symptom of a performance issue than a cause, I'd also recommend reviewing some of our troubleshooting suggestions for performance issues, linked below.
How to Identify Performance Problems in CA SDM
Hello, The migration was made several months ago and the instance was also migrated to a server in azure cloud a few months ago as well. Additionally the events if esxiten in the mdb. Regards,
Checkout this thread about adding a new domsrvr for animator that might help alleviate some of this bottle neck.
Animator in ServiceDesk 14.1 - current locks climbing
Do you have events that trigger exactly at the same time every day or something like that?