So I just ran into a couple issues with ADE, one a huge security risk and the other I found files being left out there for 5+ years obviously not cleaned up automatically by ADE. While they are not the files you specifically speak of here, the following files are not being cleaned up automatically after deployment or based on a schedule.
1. \Nimsoft\probes\service\automated_deployment_engine\nms-robot-vars-<devicename>_<datetime>.txt (had over 1,300 of these)
2. Nimsoft\probes\service\automated_deployment_engine\ade_xml_temp\automated_deployment-<id>.xml (had over 800 of these) -->!!! you will also find your major security risk in these files!!!
You will find these files not being cleaned up on all your hubs you deploy from.
I had been trying to figure out where some of my space usage was coming from. Glad I caught it before the system crashed due to lack of space.
Ticket# 20050710 and 20050724
I'm told, as apparently you were, that ADE does not do cleanup. Supports answer was this is "as designed" and while I may agree it probably is, I as an administrator should not have to be going out there cleaning these up manually nor should I as an administrator have to script the cleanup. Good coding practices would account for files left behind and make sure they are cleaned up in a timely manner or provide settings for the cleanup that the customer can set.
I've asked that this go to development and that a hotfix be provided at the very least in 9.2.x for ticket 20050724 and 9.2.x and 8.51 for ticket 20050710 due to the security concern which overlaps with file cleanup.
Original Message:
Sent: 08-16-2019 09:39 AM
From: Daniel Blanco
Subject: *** UIM 9.x Defects/Bugs/Gotchas ***
ADE Probe Defect automated_deployment_engine
New defect that won't be fixed. So I hit an issue with the automated_depoloyment_engine probe (ADE). I noticed on one of my hubs that it wasn't starting up fully. It just has the PID.
So looking into the issue what it turns out to be is that if you have forwarding rules in the distsrv probe to send archive packages to other hubs, there's a directory in the ADE probe /opt/nimsoft/probes/service/automated_deployment_engine/ade_package_temp that will just fill up over time. By fill up I mean I had one hub running for 32 days and this directory has over 2 million temp files in it.
/opt/nimsoft/probes/service/automated_deployment_engine/ade_package_temp
[DanB@uimhub ade_package_temp]# ls | wc -l
2,103,992
So what happens after the probe is restarted, it will go thru all these files and try to process them. This will take a very long time. Anyway L2 won't fix the issue. It's considered a "feature enhancement'. (Really????)
Case#20012890
Final response from development.
ADE as of now does not cleanup ade_package_temp folder as there is no code to handle this. Hence the only workaround as of now is to cleanup the folder manually. Since this is an enhancement, we will consider implementing it in future releases.
So just wanted to share this info. If you ever see the ade probe in this state or have hubs that forward packages and have the ade probe on that box, check this directory. This is running ade version 8.51
To fix this temporarily you can stop the ADE probe then get on the box running the probe, cd into the
/opt/nimsoft/probes/service/automated_deployment_engine/and then do a "rm -rf ade_package_temp". In my situation it took maybe 30+ min to run to clean up this directory. Then once its gone you can start the ade probe up again and it starts to fill back up.