Some may come across this problem, if the .conf file is not in the expected location.
For example, I created an app, that I checked in triplicate... only to figure out that, I was putting the .conf in the wrong location... so, Splunk couldn't pick it up. I received the same message as above.
To test connectivity, I also reinstalled the UF and used the GUI to see if it would, "pop," in the deployment server... SUCCESS!?!?
So, I later realized that Splunk couldn't see the file because I didn't put the .conf file in the local folder inside of the app name folder.
The file belongs here on the UF:
%SplunkHome%/etc/apps//local/<.conf file>
Not:
%SplunkHome%/etc/apps//<.conf file>
As mentioned above, I have seen varying results from different syntax. My observation is that spaces sometimes matter after the equals sign. Going directly from docs.splunk.com, it seems that there are very subtle inconsistencies in syntax. Spacing the argument from the variable seems to work most consistently for me.
Best Wishes.
... View more