Getting Data In

High consumption POWERSHELL in Active Directory without related processes Splunk-Powershell.

hcarvcamp
Explorer

Hi, everyone

I have a simple PowerShell script that runs every 5 minutes grabbing data from a database.
I have noticed the memory climbs quite high (almost 4GB). I have an "output" is the Heavy Forwarder. Seems like the memory keeps climbing.

Print below, the processes:

alt text

Any suggestions?

Thank you,

Hugo Campelo.
_

spayneort
Contributor

Are you running the ad-repl-stat.ps1 script on Windows Server 2012 R2?

http://blogs.splunk.com/2014/01/13/active-directory-replication-and-windows-server-2012-r2/

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Are you sure the offending powershell process is related to Splunk. Not to be alarmist, but some ransomware use powershell to encrypt files.

---
If this reply helps you, Karma would be appreciated.
0 Karma

hcarvcamp
Explorer

Rich,

When i STOP the UF, the highest consumption "die", and, back to the "normal" consumption.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

That would seem to confirm it's Splunk-related.

---
If this reply helps you, Karma would be appreciated.
0 Karma

hcarvcamp
Explorer

Yeah,

But do you have any idea what can be?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...