Getting Data In

Failed to write usn context

srich
Explorer

I am seeing the following errors over and over again in my splunkd.log file. I'm not sure where to go to resolve this. Any thoughts?

05-20-2010 11:15:54.163 ERROR ExecProcessor - message from ""C:\Program Files\Splunk\bin\splunk-admon.exe"" splunk-admon - run: Failed to write usn context. 05-20-2010 11:15:54.163 ERROR ExecProcessor - message from ""C:\Program Files\Splunk\bin\splunk-admon.exe"" splunk-admon - main: Failed to run ADMonitor='NearestDC', targedDC='{FQDN of DC}'

Tags (1)
1 Solution

Ledio_Ago
Splunk Employee
Splunk Employee

It sounds like Active Directory monitor program, splunk-admon.exe, couldn't save its checkpoint value, which is a USN string.

Check and see if the checkpoint file is created under:

Splunk\var\lib\splunk\persistentstorage\ADMon\NearestDC.ini

For some reason we can't write to that file.

View solution in original post

Ledio_Ago
Splunk Employee
Splunk Employee

It sounds like Active Directory monitor program, splunk-admon.exe, couldn't save its checkpoint value, which is a USN string.

Check and see if the checkpoint file is created under:

Splunk\var\lib\splunk\persistentstorage\ADMon\NearestDC.ini

For some reason we can't write to that file.

Ledio_Ago
Splunk Employee
Splunk Employee

Glad to hear you got it fixed.
How did it get to that state, do you know?

0 Karma

srich
Explorer

The file was there but permissions were wrong. Thanx.

0 Karma
Get Updates on the Splunk Community!

Take the 2021 Splunk Career Survey for $50 in Amazon Cash

Help us learn about how Splunk has impacted your career by taking the 2021 Splunk Career Survey. Last year’s ...

Using Machine Learning for Hunting Security Threats

WATCH NOW Seeing the exponential hike in global cyber threat spectrum, organizations are now striving more for ...

Observability Newsletter Highlights | March 2023

 March 2023 | Check out the latest and greatestSplunk APM's New Tag Filter ExperienceSplunk APM has updated ...