Sounds like I have a manifest file/hashing issue that appears whenever I restart splunkd on an endpoint, like the following:
# ./splunk stop
Stopping splunkd...
Shutting down. Please wait, as this may take a few minutes.
Stopping splunk helpers...
Done.
# ./splunk start
Splunk> 4TW
Checking prerequisites...
Checking mgmt port [8089]: open
Checking conf files for problems...
Done
Checking default conf files for edits...
Cannot find any source of hashes. Manifest file '(null)' not present?
Problems were found, please review your files and move customizations to local
All preliminary checks passed.
Starting splunk server daemon (splunkd)...
Done
Is this just an annoying error or are there real problems when the manifest is missing? Our UNIX operations team tells me that they install the UF via a package manager, and claim that there is no manifest present on the systems.
Thanks!
↧