PMP Enterprise - Dual import / can no longer delete resources.
Product : ManageEngine Password Manager Pro
Version : 8.3.0
Build Number : 8300
Our Enterprise installation of PMP has been running fine for some time. However, beginning just recently we can no longer delete resources. On top of that, during a recent import task, PMP imported the resources twice, so we have double listings for 100+ resources.
We actually had to bring down our active instance because the CPU was pegged by postgres attempting to delete the resources.
When I trigger a deletion request, the GUI will sit at "Loading..." for 10+ minutes and eventually display something along the lines of "You are not allowed to make this request, the operation has been audited." (I am a super admin) But the resource actually /does/ get deleted.
If I watch the processes with top, postgres spawns off children running select functions against the DB until the operation finally succeeds, if I attempt to delete multiple resources or run multiple deletions at once without waiting for a full completion, this gets compounded and that is when the CPU pegs. The children that are spawned take some time after the success to clean themselves up. In all it takes 30+ minutes to delete one resource.
Other operations are successful, I can update resources / accounts, create / delete resource groups.
Is anyone able to offer assistance with this issue?
Thank you -
Version : 8.3.0
Build Number : 8300
Our Enterprise installation of PMP has been running fine for some time. However, beginning just recently we can no longer delete resources. On top of that, during a recent import task, PMP imported the resources twice, so we have double listings for 100+ resources.
We actually had to bring down our active instance because the CPU was pegged by postgres attempting to delete the resources.
When I trigger a deletion request, the GUI will sit at "Loading..." for 10+ minutes and eventually display something along the lines of "You are not allowed to make this request, the operation has been audited." (I am a super admin) But the resource actually /does/ get deleted.
If I watch the processes with top, postgres spawns off children running select functions against the DB until the operation finally succeeds, if I attempt to delete multiple resources or run multiple deletions at once without waiting for a full completion, this gets compounded and that is when the CPU pegs. The children that are spawned take some time after the success to clean themselves up. In all it takes 30+ minutes to delete one resource.
Other operations are successful, I can update resources / accounts, create / delete resource groups.
Is anyone able to offer assistance with this issue?
Thank you -