Hi
I am unable to enable monitoring on a network file share, \servername\f$\XXX\XXX on a linux server. I am adding the path as data inputs from the GUI. I had made sure that the Splunkd is running as root on the linux splunk search head server. I am getting the following error:
Parameter name: Path must be absolute.
I was able to test the same thing out on my Windows Search Head on version 6.1.4 version and splunkd started monitoring files from the network file share \servername\f$\XXX\XXX, but when I am trying to replicate the same thing on linux Splunk Search Head server, I get the parameter name : path must be absolute error.
Please guide me if I am missing something.
The syntax for monitoring a network share is different between windows and linux:
To monitor a shared network drive, enter the following: <myhost>/<mypath> (or \\<myhost>\<mypath> on Windows). Make sure Splunk has read access to the mounted drive, as well as to the files you wish to monitor.
You may also prefer to "mount" the network drive on the linux box before monitoring it so that it will be on a local path like /mnt/networkShare
Finally, make sure the user splunkd is running as has permission on the network share.
Hi mmohiuddin,
can you provide the complete monitor stanza?
Usually this kind of error pops up if you try to monitor a windows path from linux like this:
[monitor://c:\foo\bar\file.txt]
Or on a windows server something like this:
[monitor:///foo/bar/file.txt]
Was getting the "ERROR AdminManager - Parameter name: Path must be absolute" problem when I tried upLoad File into Splunk. After a couple of attempt without success on Firefox web browser, I decided to try Chrome browser and the data file was uploaded successfully!!!
I hope that saves someone some grief!
Seeing the same thang while uploading csv from my local desktop. Interesting...
Happened to me as well. Went back and tried uploading it again using the saved format I'd created early, and did not get the error. Wondered if something happened on the filesystem, as the file was on a UNC path.
Worked when I selected the file (rather than drag and drop into UI).
@mmohiuddin, I encountered this same error last night when uploading some data. This morning, I tried uploading the data on a different network, and it worked without any problem. Were you able to resolve your issue?