CA Configuration Automation

I´d finished the instalation. Management profile is not working properly ( regression test ).

MP start running but never ends. I´ve put down CCA server to stop it.

Does anyone know anything about this issue ?

Hi Pedro

If you know roughly how long the MP should run you can set a time limit in it.

Say roughly the MP should run for 60 minutes normally then set the MP to time out after 90 minutes.

1. Does the problem occur for all MPs?

2. Is there anything in the log?

3. Are there CCA Agents on the system contained in the MP? If yes there could be an agent log.

4. Have you tried restarting the NDG associated with these systems?

Hope this helps.

Kind Regards

Barb

Also, do you have any Grid Nodes in the environment, if so, the Job management part of it will will run on the Grid Node; the CCA Server will just check the database for updates.  Also, if you do have the GNs, check those logs specifically

In short, if a job finished, failed, anything, but the status of the job never went back to the database (for any number of reasons), the job will show it as running.(Here is a detailed workflow that might assist: Tech Tip: Blueprint Discovery Process Flow )

To kill those jobs, you can follow this update (its for NDG, but same concept applies: Re: network scan jobs won't complete or cancel )

Hi Adnan,

Thanks for the suggestion, I asked the Database Administrator to do what procedure was suggested for you.
I do not have access to the database, I am depending on the response from the management to eliminate jobs.

Hi Barbara,

Here are the answers:

If you know roughly how long the MP should run you can set a time limit in it.

Yes, 60 minutes.

Say roughly the MP should run for 60 minutes normally then set the MP to time out after 90 minutes.

1. Does the problem occur for all MPs?

Yes. it does.

2. Is there anything in the log?

there isn't anything.

3. Are there CCA Agents on the system contained in the MP? If yes there could be an agent log.

Yes, there are. but don't have anything in the log.

4. Have you tried restarting the NDG associated with these systems?

Yes, i had restarterd all servers (CCA Server, Grid and NDG), but don't worked.

Thanks for you help.

Pedro.

HI Pedro,

Did you happen to check out the Grid Nodes (if applicable)?  and What about the DB Tables entries to be removed to clean out the stalled jobs?

Hi Pedro, Any update on this ?

Hi Adnan,

Where you able to at least remove the jobs from the database? Re: network scan jobs won't complete or cancel

If not, please try that and try your profile discovery again

If so, I would recommend opening a support ticket so the team can further assist

Hi Adnan,

I don't have how to remove jobs because i'm not dba administration;

I'm waiting the answer from dba administrator to execute the instrunctions that you passed.

Anyway, i'll to open a support ticket to team of CA.

Thanks for your help.

Hi Adnan,

I was analyzing the job problem that never ends and that identified during the process, the status at any given time is "waiting for dependencies". Would you have any idea?

Thanks.

Pedro.

Goes back to what I mentioned earlier, you would need to remove those jobs from the database based off the link I referenced before.  Once you get rid of those bad jobs, the rest should start kicking off accordingly

Hi Adnan,
I did the steps you recommended. The tables were cleaned properly.
After that, we performed new jobs the management profile and the problem happened again.
waiting on dependencies
Management server profile job on "zzzzzzzzzz"
MPServ Job
waiting on dependencies
Management server profile job on "YYYYYYYYYY"
MPServ Job
waiting on dependencies
Management server profile job on "*********"
MPServerJob
Some idea of the cause of the problem?

Thanks a lot.

Pedro.

Very possibly that the jobs are crashing the Grid Server \ Grid Nodes. 

You can check the CCA UI --> Administration --> Grid Information --> Grid Jobs --> see if any exceptions are listed in the Exception Type column.  If so, view those, there might be errors that are crashing the nodes such as Java Heap space or maybe a near-infinite scan that is holding up the job

Also, check what blueprints you are discovering, as at least one of those BPs may be effecting the discovery.  If you have any custom BPs there, I would remove them and test with the OOTB BPs first, if that works, add one Custom BP at a time to see if you can find a culprit

If no Custom BPs exist, then check if any of the blueprints are discovering a "heavy" application, like Exchange, or a Domain Server where a vast amount of information has a potential of being discovered

Another test (which you may want to mix in somewhere there) is if you do have Grid Nodes, stop them.  Let the discovery only use the CCA Server's Grid Server.  This will impact the server's performance a bit if you run many big MPs, so I would do one at a time.  It's a useful troubleshooting technique

If none of the above helps or don't make enough process, I would recommend opening a support ticket and possible doing a remote session with one of the support engineers

Hi Adnan,

Thanks for trying to help me. I don't have blueprint customized. I'm just running blueprints with operating system and database.
I have 3 grid nodes and none showed any error message in the exception column. Even just running the grid server, the problem still occurs.

I'll open a ticket for support CA.

Regards,

Pedro.