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!

Enterprise Security Content Update (ESCU) | New Releases

In January, the Splunk Threat Research Team had one release of new security content via the Splunk ES Content ...

Expert Tips from Splunk Professional Services, Ensuring Compliance, and More New ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Observability Release Update: AI Assistant, AppD + Observability Cloud Integrations & ...

This month’s releases across the Splunk Observability portfolio deliver earlier detection and faster ...