Getting Data In

Why is the Powershell Modular Input not scheduling the script to run?

Kendo213
Communicator

Here is my inputs.conf:

[powershell://checkdnsext]
script = . "$SplunkHome\etc\apps\test_infra_dnsext_inputs\bin\checkdnsext.ps1"
schedule = `0 */5 * ? * *`
sourcetype = test:powershell
index = test

Here is my Powershell located in /app/bin:

$ErrorActionPreference="SilentlyContinue"
$ipaddress = $(ipconfig | where {$_ -match 'IPv4.+\s(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})' } | out-null; $Matches[1])
$dnstest=Resolve-DnsName -Name google.com -server $ipaddress -QuickTimeout -Type A | select Name
if ($dnstest -like '*google*') {
$result="1"
write-host ((get-date),"`nExternal DNS Status:","$result")
}
else{
$result="0"
write-host ((get-date),"`nExternal DNS Status:","$result")
}

The script works. I don't see any errors in splunkd.log on the client, other than the fact that I don't see it scheduling the script to run.

Any ideas?

0 Karma

ansif
Motivator

Can you try with a service restart.

0 Karma

Kendo213
Communicator

I've tried restarting the service numerous times. That cron has 's around it because of the Splunk forum. It doesn't complain about an invalid cron in the internal logs.

0 Karma
Get Updates on the Splunk Community!

Splunk MCP & Agentic AI: Machine Data Without Limits

  Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization ...

Finding Based Detections General Availability

Overview  We’ve come a long way, folks, but here in Enterprise Security 8.4 I’m happy to announce Finding ...

Get Your Hands Dirty (and Your Shoes Comfy): The Splunk Experience

Hands-On Learning and Technical Seminars  Sometimes, you just need to see the code. For those looking for a ...