CatTools_Client Memory Issue

Question

Okay I've been running into a serious problem when using CatTools. I've wrote a custom script to do IOS Upgrades and also another script to pull Cisco Device information and save it to a file so I can import it into the database. The scripts work great but one problem. The memory that the CatTools_Client.exe is using when running these scripts never goes down but keeps climbing. This looks like a memory leak to me because after it finishes the activity on a device it's never restore that memory back to the pool. For me to do my upgrades I have to run it on less than 400 devices, after it completes, kill the CatTools_Client.exe process and then I can perform another batch. I've watched the scripts that are already with Cattools and they don't experience this problem.

So my question is what is wrong with my scripts that isn't wrong with the default scripts that are included. I have included this line at the end of my scripts. cl.DisconnectHost which is supposedly to disconnect the client but it doesn't sound or look like it's working correctly. If a developer sees this I would be more than happy to let them look at my script so they can see if there is a problem in it.

Sartuche24 · Accepted Answer

issue has been resolved after working with Steve Welsh on the issue. It took some major digging but in the end the problem was using the CatTools API within my scripts. After talking to Steve this was never designed to run in an activity but on external scripts which I knew but I didn't know it would cause a problem like it did, so my advice don't use the API in your activities you run through CatTools only on external scripts. The reason I was running the API is because I wanted some information from the DB but didn't know there were included variables already holding this information. These variables aren't documented but I will list them below and also brought it to the attention of Steve who will work the internal side of trying to get the documentation updated with the variables that are available within CatTools. Variables: cl.CurDevHostName <-- The Current Device IP Address cl.CurDevType <-- The Current Device type such as Cisco.Router.General cl.CurDevModel <-- The Current Model of the Device as it is in the DB cl.CurDevName <-- The name of the device in the DB, this is different from cl.DeviceName because cl.DeviceName is the hostname that the activity determines once it logs into the device. I would assume anything in the DB can be used if you use the following prefix to how the column is labelled in the DB: cl.CurDev{Column Name} <-- Now don't take my word on it but so far it has worked. If you need a list of Column names just perform an export and the Column Headers are what you would use. Thanks again to Steve for all the help.