For my client I am trying to build a test cluster that will be used for production deployment. The indexer are not communicating with he master server. This is an example of the problem:
[root@splunkIndexer-1 bin]#
[root@splunkIndexer-1 bin]# curl -v -m 10 https://splunkMaster.chenierservices.local:8089/services/server/info
* About to connect() to splunkMaster.chenierservices.local port 8089 (#0)
* Trying 192.168.10.109...
* Connected to splunkMaster.chenierservices.local (192.168.10.109) port 8089 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* Server certificate:
* subject: O=SplunkUser,CN=SplunkServerDefaultCert
* start date: Mar 16 22:28:51 2016 GMT
* expire date: Mar 16 22:28:51 2019 GMT
* common name: SplunkServerDefaultCert
* issuer: E=support@splunk.com,CN=SplunkCommonCA,O=Splunk,L=San Francisco,ST=CA,C=US
* NSS error -8172 (SEC_ERROR_UNTRUSTED_ISSUER)
* Peer's certificate issuer has been marked as not trusted by the user.
* Closing connection 0
curl: (60) Peer's certificate issuer has been marked as not trusted by the user.
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
[root@splunkIndexer-1 bin]#
According to this, the Splunk certificates are not properly signed and trusted. This obviously is a show stopper. Looked at the Splunk knowledge base and found no answer.
↧