<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Mongodb SSL errors using self-signed certs in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Mongodb-SSL-errors-using-self-signed-certs/m-p/304936#M2660</link>
    <description>&lt;P&gt;I have a customer that is evaluating Splunk in a cloud provider.  They are trying to evaluate the performance of bare metal vs VM instances.&lt;/P&gt;

&lt;P&gt;There are four hosts&lt;/P&gt;

&lt;P&gt;1 bare metal Enterprise indexer&lt;BR /&gt;
1 VM Enterprise indexer&lt;BR /&gt;
2 VM forwarders configured to send one copy&lt;/P&gt;

&lt;P&gt;I have created self-signed certs for all of the hosts --- web, forwarding, etc.  The SSL config in server.conf is identical for both of them except for the name of the server certificate.&lt;/P&gt;

&lt;P&gt;Today on the bare metal instance, the kvstore started crashing.  I see the following in mongod.log:&lt;/P&gt;

&lt;P&gt;2018-01-12T19:02:34.677Z W CONTROL  No SSL certificate validation can be performed since no CA file has been provided; please&lt;BR /&gt;
 specify an sslCAFile parameter&lt;/P&gt;

&lt;P&gt;The server.conf on both machines points to the same CA cert.  I've confirmed the CA certs on both machines have the same md5 hash and permissions.&lt;/P&gt;

&lt;P&gt;I also see this in the mongod.log on the problem indexer:&lt;/P&gt;

&lt;P&gt;2018-01-12T19:02:34.694Z I CONTROL  [initandlisten] options: { net: { port: 8191, ssl: { PEMKeyFile: "/opt/splunk/etc/auth/mycerts/index01_cert.pem", PEMKeyPassword: "", allowInvalidHostnames: true, disabledProtocols: "noTLS1_0,noTLS1_1", mode: "requireSSL", sslCipherConfig: "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RS..." }, unixDomainSocket: { enabled: false } }, replication: { oplogSizeMB: 200, replSet: "DE599A03-4B9A-426B-BDE9-882044E6E8C3" }, security: { javascriptEnabled: false, keyFile: "/opt/splunk/var/lib/splunk/kvstore/mongo/splunk.key" }, setParameter: { enableLocalhostAuthBypass: "0" }, storage: { dbPath: "/opt/splunk/var/lib/splunk/kvstore/mongo", mmapv1: { smallFiles: true } }, systemLog: { timeStampFormat: "iso8601-utc" } }&lt;/P&gt;

&lt;P&gt;From what I see in the server.conf.spec, all of the [kvstore] SSL options, like caCertFile and caCertPath, are deprecated.&lt;/P&gt;

&lt;P&gt;Identical configs, identical certs...  Why is mongodb having issues on only one machine?&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 17:38:39 GMT</pubDate>
    <dc:creator>responsys_cm</dc:creator>
    <dc:date>2020-09-29T17:38:39Z</dc:date>
    <item>
      <title>Mongodb SSL errors using self-signed certs</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Mongodb-SSL-errors-using-self-signed-certs/m-p/304936#M2660</link>
      <description>&lt;P&gt;I have a customer that is evaluating Splunk in a cloud provider.  They are trying to evaluate the performance of bare metal vs VM instances.&lt;/P&gt;

&lt;P&gt;There are four hosts&lt;/P&gt;

&lt;P&gt;1 bare metal Enterprise indexer&lt;BR /&gt;
1 VM Enterprise indexer&lt;BR /&gt;
2 VM forwarders configured to send one copy&lt;/P&gt;

&lt;P&gt;I have created self-signed certs for all of the hosts --- web, forwarding, etc.  The SSL config in server.conf is identical for both of them except for the name of the server certificate.&lt;/P&gt;

&lt;P&gt;Today on the bare metal instance, the kvstore started crashing.  I see the following in mongod.log:&lt;/P&gt;

&lt;P&gt;2018-01-12T19:02:34.677Z W CONTROL  No SSL certificate validation can be performed since no CA file has been provided; please&lt;BR /&gt;
 specify an sslCAFile parameter&lt;/P&gt;

&lt;P&gt;The server.conf on both machines points to the same CA cert.  I've confirmed the CA certs on both machines have the same md5 hash and permissions.&lt;/P&gt;

&lt;P&gt;I also see this in the mongod.log on the problem indexer:&lt;/P&gt;

&lt;P&gt;2018-01-12T19:02:34.694Z I CONTROL  [initandlisten] options: { net: { port: 8191, ssl: { PEMKeyFile: "/opt/splunk/etc/auth/mycerts/index01_cert.pem", PEMKeyPassword: "", allowInvalidHostnames: true, disabledProtocols: "noTLS1_0,noTLS1_1", mode: "requireSSL", sslCipherConfig: "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RS..." }, unixDomainSocket: { enabled: false } }, replication: { oplogSizeMB: 200, replSet: "DE599A03-4B9A-426B-BDE9-882044E6E8C3" }, security: { javascriptEnabled: false, keyFile: "/opt/splunk/var/lib/splunk/kvstore/mongo/splunk.key" }, setParameter: { enableLocalhostAuthBypass: "0" }, storage: { dbPath: "/opt/splunk/var/lib/splunk/kvstore/mongo", mmapv1: { smallFiles: true } }, systemLog: { timeStampFormat: "iso8601-utc" } }&lt;/P&gt;

&lt;P&gt;From what I see in the server.conf.spec, all of the [kvstore] SSL options, like caCertFile and caCertPath, are deprecated.&lt;/P&gt;

&lt;P&gt;Identical configs, identical certs...  Why is mongodb having issues on only one machine?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 17:38:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Mongodb-SSL-errors-using-self-signed-certs/m-p/304936#M2660</guid>
      <dc:creator>responsys_cm</dc:creator>
      <dc:date>2020-09-29T17:38:39Z</dc:date>
    </item>
  </channel>
</rss>

