Outputs.conf sslPassword not hashing for specific systems

[ricotries]

I have a test environment with similar devices (Windows 10 laptops that serve the same purpose and have the same software) that I'm using to test the SSL configuration for the input-outputs of log receiving/forwarding between Universal Forwarders and one Indexer (both version 6.5). The issue is that for some devices, once the Universal Forwarder is installed and they point to the Indexer (which is set up as a Deployment Server as well) to pull the app that contains the testing SSL configuration for outputs.conf, certain devices do not hash the sslPassword when the UF restarts, while others do. So all devices are phoning home and are listed under Forwarder Management, but only some are sending logs, while the rest (that are not hashing the sslPassword) can't send any logs.

What is going on?

[codebuilder · Accepted solution]

All the behaviors you describe, especially the lack of password hashing, generally indicates that Splunk is unable to access the file.
Verify that your Splunk user has access to the file(s) and that they are not set to read only.

[codebuilder]

Any progress?

[ricotries]

Yeah that was it, I figured out that when I installed the UFs, I forgot to run the installer as administrator in some of them, which happen to be the ones that were failing to hash the password.

[codebuilder]

Glad to hear you were able to resolve it.