configautodownload.exe has 28 iterations on my NCM server

Is it normal that at any given time I would have 28 or so iterations/processes of configautodownload.exe? It is not doing a download now.... I do use real time config backup. I go in about once a week and kill most of them but they come back.

Its almost like leftover processes from when it did a backup after a change.

Thanks!!

Find more posts tagged with

configautodownload.exe_ncm

rtcd_iteration

Accepted answers

All comments

FormerMember

I have hung up ones all the time.

Piyoush

Glad I am not the only one who saw that... They disappeared only after a server reboot...

FormerMember

I asked for them to consider having that .exe perform downloads from a queue of devices changed instead of spawning a new instance for every changed detected. I can't push changes to all my devices anymore. Doing so kills the server.

docwhite

I'm calling the dev team's attention to this. What resources are the zombie download processes tying up?

Doug

ctopaloglu

Same problem here. I am deleting all the hung processes as I am replying this message .

I even upgrade the NCM 6.1 RC but nothing changed. You should fix this bug in the 6.1 GA.

christineb

Hi everyone - we haven't been able to reproduce this issue, but we're going to send it back for additional investigation. I'll be in touch as we find out more.

--Christine

FormerMember

Case in point. If I send an update to 250 routers I get real time change detection for 250 devices, thus 250 processes spawned and the server dies. I usually have to have it restarted via VM Console. I have one orphaned at 20MB RAM

christineb

Pyro13g - have you tried to adjust the setting: 'Limit number of simultaneous RTN download operations' option on NCM Settings > RTCD > Config Change Settings screen? That might do what you want.

--Christine

FormerMember

I'm seeing the same problem and would really like to see this fixed.

I noticed that everything runs fine if we only update a switch at a time but for mass changes I like to push them out with NCM (one of the reasons we got NCM) and RTN stop working is not something we like to deal with every time we update 100 switches.

ctopaloglu

NCM 7.0 Beta 4 is out at the moment. Soon they will release the RC after then you can use it.

FormerMember

I figured out my issue with the configautodownlaod.exe running multiple times and not quitting, what i noticed was a lot of traps were being sent to my NPM server and were continueing to loop and not stop.

i checked my trap alert setting to find that i did not follow page 79 of the admin guide and had the wrong snmp MIB set to fire off the configautodownload.exe. what i thought was a MIB that was a change to the config MIB was actually a logon MIB, and because NCM was logging on to check the config it then sent another trap that matched the logon MIB.

when i reset the alert and followed the directions in the admin guide to the T i was able to stop the configautodownload from looping all the time.

and after all those year of teachers telling me to read all the directions before jumping, i could have saved myself and tech support a good deal of time if i just would have read all the steps.

thank you to the tech support team for putting up with me.