Getting Data In

ERROR WinEventLogChannel - initOld: Failed to initialize checkpoint for Windows Event Log channel 'Security' Host is no longer forwarding WinEventLog:Security to the Linux indexer.

Ellen
Splunk Employee
Splunk Employee

All of a sudden my 4.0.9 Splunk server is no longer forwarding the WinEventLog:Security logs onto my 4.1.4 Linux indexer. This was working fine and I can see the communication is established between the 2 systems. What's at issue?

1 Solution

Ellen
Splunk Employee
Splunk Employee

This is a known defect, SPL-31339: WinEventLog:Security logs stop getting indexed and Splunkd.log displays the following errors:

ERROR WinEventLogChannel - initOld: Failed to initialize checkpoint for Windows Event Log channel 'Security' ERROR WinEventLogInputProcessor - main-thread: Failed to initialize Windows Event Log 'Security'

This is likely due the Windows host not shutting down properly and the %SPLUNK_HOME%\var\lib\splunk\persistentstorage\WinEventLog\Security_checkpoint file is empty (size =1KB)

The workaround is to shutdown Splunk on the Windows host, remove the file and restart Splunk to create a new Security_checkpoint file. This will allow the security logs to start indexing again.

This defect is fixed in 4.1.4 (see http://www.splunk.com/base/Documentation/latest/ReleaseNotes/4.1.4) For 4.0.x, the fix is not currently planned and the workaround should be implemented.

View solution in original post

Ellen
Splunk Employee
Splunk Employee

This is a known defect, SPL-31339: WinEventLog:Security logs stop getting indexed and Splunkd.log displays the following errors:

ERROR WinEventLogChannel - initOld: Failed to initialize checkpoint for Windows Event Log channel 'Security' ERROR WinEventLogInputProcessor - main-thread: Failed to initialize Windows Event Log 'Security'

This is likely due the Windows host not shutting down properly and the %SPLUNK_HOME%\var\lib\splunk\persistentstorage\WinEventLog\Security_checkpoint file is empty (size =1KB)

The workaround is to shutdown Splunk on the Windows host, remove the file and restart Splunk to create a new Security_checkpoint file. This will allow the security logs to start indexing again.

This defect is fixed in 4.1.4 (see http://www.splunk.com/base/Documentation/latest/ReleaseNotes/4.1.4) For 4.0.x, the fix is not currently planned and the workaround should be implemented.

Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...