After running the collection, it is not running and the state still shows as New.
Please advise to resolve this .
I've moved your question to the RSA Identity Governance & Lifecycle space, where it will be seen by the product's support engineers, other customers and partners. Please bookmark this page and use it when you have product-specific questions.
Alternatively, from the RSA Support page, click on Ask A Question on the blue navigation bar and choose Ask A Product Related Question. From there, scroll to RSA Identity Governance & Lifecycle and click Ask A Question. That way your question will appear in the correct space.
Most likely there are other collections in progress.
Asking a question is not like asking the right question
thanks for the reply.
No collections are running, still they are in New state.
I tried to cancel the collections and rerun the collectors, but still facing the same issue. Collections are starting to run state.
Can you change the Time Span to Last 7 days and then share a screenshot of the entire screen (similar like I did)?
I have attached the screenshot for your reference.
Scroll down, most likely the last result will be in a running state.
Based on the queue time column, there is probably a collection which is stuck and that's why all others are in a New state.
To release the stuck collection, you can restart the server.
Many thanks for the reply. I restarted the server and now it is working fine.
Just for understanding, why the collections are stuck in New state itself and if it gets stuck why we need to restart the server.
I have asked RSA/EMC/DELL in support to add an option that if a "stack trace" occurs (RSA Identity Governance & Lifecycle is very sensitive for network problems, which often give stack traces during collection), then that collection should be automatically be aborted. But RSA/EMC/DELL have never shown interest in this, they ask me to fix the network instead... *sigh*
But if more think that collections should not be queued up indefinitely, then please vote on these two suggestions below that at least makes it possible to avoid that the server gets stuck in a collection for days (which stops other collections apparently):
Option to define collection duration (time out): https://community.rsa.com/ideas/1441Dont queue collectors that are already queued: https://community.rsa.com/ideas/1562
Please advise - Just for understanding, why the collections are getting stuck in New state itself and not going to running state. Collectors getting stuck in New state for long duration.
After restarting the server the collector worked fine and running.
if it gets stuck why we need to restart the server. Why the collections are in New state itself for long time and not moving to run. Please let me know the reason.
We have seen the same issue in our environment. You have to create an support ticket, but i can tell you that they have not found a solution yet.
Since it occurs very randomly, all you can do is either restart or start the collector again and hope for the best.
Us too. From what I can tell, there are a lot of possible ways for a collection to go sideways and if IGL doesn't handle it, then you're looking at an application restart. I really wish I knew more about how the collection queue is processed and how the scheduler works.
We had a kinda fruitfull support meeting last friday with Engineering. We came to the conclusion is not a remote agent issue. It seems there is an issue in the job scheduler. I keep you posted
We have this issue right now in PROD. Not really happy that for every issue, server restart is the only option. Good to hear you're getting traction! Keep us posted!
Collections stuck in "New" status is a common symptom for several different types of failures. Problems with the scheduler that may caused this symptom have been resolved in 7.1.0 P04 and 7.0.2 P11 and later.
Retrieving data ...