topic Re: Batch input for Windows preventing new file creation in Getting Data In

Batch input for Windows preventing new file creation

ebaileytu — Fri, 24 Jun 2016 20:54:20 GMT

We want to set up a process that writes an application log to a batch input where Splunk will ingest the file and then delete it. The problem is the script that is creating the file is not being allowed to create the file with the following error. Each file is uniquely named. The batch input is for a directory.

PS C:\Users\sa-> C:\Users\sa\Desktop\Export_Server_Oper_Reg_Keys_v1.ps1
Add-Content : The process cannot access the file 'C:\Temp\windows_reg_export\regxprt2016-06-24_14.59.txt' because it is being used by another process.
At C:\Users\sa-\Desktop\Export_TU_Server_Oper_Reg_Keys_v1.ps1:63 char:1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Temp\windows...06-24_14.59.txt:String) [Add-Content], IOException
    + FullyQualifiedErrorId : GetContentWriterIOError,Microsoft.PowerShell.Commands.AddContentCommand

The script only works if the Splunkforwarder service is stopped. I have never seen this behavior before. Any ideas? Thanks!

Re: Batch input for Windows preventing new file creation

jkat54 — Sat, 25 Jun 2016 14:33:50 GMT

The forwarder is locking the file. It's a resource race / contention issue.

Instead of using batch, use monitor with movePolicy=sinkhole.

Re: Batch input for Windows preventing new file creation

ebaileytu — Tue, 05 Jul 2016 16:04:58 GMT

tried that getting the error message - any other ideas?

The UF is running as a local admin and the script is being run as a local admin well.

Thanks

Re: Batch input for Windows preventing new file creation

ebaileytu — Tue, 12 Jul 2016 14:23:08 GMT

Ended up writing a wrapper to execute the PS script and using a script input since we could not get this issue resolved. Could not figure how to fix the question above.

Re: Batch input for Windows preventing new file creation

teresachila — Thu, 04 May 2017 21:07:40 GMT

We are having the same problem. What do you mean by "writing a wrapper to execute the PS script and using a script input" as the workaround?