NCM Jobs Not Stopping

I currently have a NCM job for Config backup and inventory. They each run twice a week. I've noticed that each time they run at 2:00 AM, that morning at 8:00 the job is still running and using up resources on the server. I receive an email confirmation each time the jobs are completed and they typically only take a couple hours to complete. I then have to manually stop each job within NCM. Anyone else experience this?

Thanks

Find more posts tagged with

ncm_5.5.1

job

Configuration

Accepted answers

DirtySouth

I get a results email when my jobs complete and the only errors I've noticed are snmp timeouts, but that varies depending on the device. I don't believe thats related. The Config Backup finsihes within 20 minutes (432 devices). The inventory takes much longer and I believe is the reason for the job not stopping.

All comments

Donald_Francis

I get that from time to time. I usually just manually stop it and on the next run it is fine. Sometimes I just reboot the server.

If you get it consitently probably should open a ticket so support can gert in there and look around.

parentch

I have almost the same problem with my Config backup job. I run it daily and it does one of the following:

- It works as expected and takes about 45mins to complete (half of the time)

- Sometimes, it sends me 2 emails saying the job is complete with 0 devices, 20 secs after the job starts.. Of course, the it doesn't backup any device when this happens.

- Sometimes, it starts and never stops. It uses all the server resources and I have to manually stop it on the morning. The backup doesn't work for any device when this is the case.

DirtySouth

parentch, that sounds like a bigger problem than what I've been seeing. You might want to open a support case on that. Fortunately, my config backups & inventory do completely correctly.

moyzan

We installed NCM last week and I have the same problem. It started the job last Saturday the 9th at 00:01 and I just stopped it. Here's the last part of the log that shows what happened:

1/9/2010 12:10:19 AM : Completed Backup Journalier : Job-774437 ; Devices : 378 ; Errors : 135
Execution time : 8 minutes, 35 seconds
___________________________________________________________________________

ERROR: Job Canceled

1/11/2010 10:51:35 AM : Completed Backup Journalier : Job-774437
___________________________________________________________________________

Obviously I have some configuration to do on my 135 devices that are not responding but hopefully that's not the cause of the job hanging...

It should be noted that the job completed all tasks when it was run on the 9th but since it didn't stop, it didn't execute on the 10th and 11th.

chris.lapoint

moyzan, please open a support ticket on this issue so we can investigate this further.

parentch

Moyzan, is your OS installed in english? I'm just trying to figure out if regional settings could be the source of the problem.

thx