Getting Data In

DNS logs - INFO [:12345] Script exceeded maximum runtime of

inventsekar
SplunkTrust
SplunkTrust

Hi Splunk Gurus, 

I use the "Windows DNS Analytical Custom" app for DNS logs onboarding to Splunk Cloud. 

on the DC systems, the PowerShell script runs, but it does not produce any output. 

on Splunk we receive logs as "INFO [:13744] Script exceeded maximum runtime of . Terminating PID 13744"
on these logs i see the source as - source="C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe -command \"& 'c:\\Program Files\\SplunkUniversalForwarder\\etc\\apps\\TA-WinDNSAnalytical-inputs\\bin\\get_dns_analytics.ps1'\" -SplunkdLogging"

one thing to note - the DC systems are pretty busy systems. maybe the script runs but timeouts(i believe). so working on increasing the "timeout" parameter in the inputs.conf file. 

any other suggestions, thoughts pls, thanks. 

thanks and best regards,
Sekar

PS - If this or any post helped you in any way, pls consider upvoting, thanks for reading !
Labels (2)
0 Karma
1 Solution

inventsekar
SplunkTrust
SplunkTrust

We worked with Splunk Support and they suggested some editings/updates on that powershell script, which resolved this issue, hence solving this questions. thanks. 

thanks @PrewinThomas .. given upvotes, thanks again. 

thanks and best regards,
Sekar

PS - If this or any post helped you in any way, pls consider upvoting, thanks for reading !

View solution in original post

inventsekar
SplunkTrust
SplunkTrust

We worked with Splunk Support and they suggested some editings/updates on that powershell script, which resolved this issue, hence solving this questions. thanks. 

thanks @PrewinThomas .. given upvotes, thanks again. 

thanks and best regards,
Sekar

PS - If this or any post helped you in any way, pls consider upvoting, thanks for reading !

PrewinThomas
Motivator

@inventsekar 

On busy DCs script can take longer than the default timeout to query.

Can you run the powershell directly and see how long its taking and adjust your timeout accordingly.

& 'C:\Program Files\SplunkUniversalForwarder\etc\apps\TA-WinDNSAnalytical-inputs\bin\get_dns_analytics.ps1'


Regards,
Prewin
If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!

Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...