<?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 Re: splunk fowarder SSL error ERROR TcpOutputProc in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101159#M21195</link>
    <description>&lt;P&gt;ok.. I see the CERT in the file..&lt;/P&gt;

&lt;P&gt;i added the output from openssl to the description.. looks ok to me.. what do you think ?&lt;BR /&gt;
thanks &lt;BR /&gt;
mike&lt;/P&gt;</description>
    <pubDate>Tue, 01 Nov 2011 02:00:11 GMT</pubDate>
    <dc:creator>mcalautti</dc:creator>
    <dc:date>2011-11-01T02:00:11Z</dc:date>
    <item>
      <title>splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101157#M21193</link>
      <description>&lt;P&gt;on the forwarder I get&lt;BR /&gt;
ERROR TcpOutputProc - Error initializing SSL context - invalid sslCertPath for server &lt;INDEXER&gt;&lt;/INDEXER&gt;&lt;/P&gt;

&lt;P&gt;right before that I see&lt;BR /&gt;
 ERROR SSLCommon - Can't read key file /opt/splunkforwarder/etc/certs/forwarder.pem errno=101077092 error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt.&lt;/P&gt;

&lt;P&gt;not sure what that means.&lt;BR /&gt;
I took the existing certs DIR from an existing splunk build that is working fine with the forwarder&lt;/P&gt;

&lt;P&gt;the indexer is version 4.1.5, build 85165 &lt;BR /&gt;
the forwarder is splunkforwarder-4.2.3-105575-Linux-x86_64&lt;/P&gt;

&lt;P&gt;output from openssl x509 -inform PEM -in forwarder.pem -text -noout&lt;/P&gt;

&lt;P&gt;Certificate:&lt;BR /&gt;
    Data:&lt;BR /&gt;
        Version: 1 (0x0)&lt;BR /&gt;
        Serial Number:&lt;BR /&gt;
            8e:69:04:62:da:36:fa:2b&lt;BR /&gt;
        Signature Algorithm: sha1WithRSAEncryption&lt;BR /&gt;
        Issuer: C=US, ST=CA, L=SanFrancisco, O=SplunkInc, CN=SplunkCA, O=SplunkUser&lt;BR /&gt;
        Validity&lt;BR /&gt;
            Not Before: Sep 21 18:29:40 2011 GMT&lt;BR /&gt;
            Not After : Sep 20 18:29:40 2014 GMT&lt;BR /&gt;
        Subject: C=US, ST=MA, L=Bedford, O=sb&lt;BR /&gt;
        Subject Public Key Info:&lt;BR /&gt;
            Public Key Algorithm: rsaEncryption&lt;BR /&gt;
            RSA Public Key: (1024 bit)&lt;BR /&gt;
                Modulus (1024 bit):&lt;BR /&gt;
                    00:a8:d4:41:84:b2:9f:3c:3f:7f:c3:a2:3d:54:9d:&lt;BR /&gt;
                    7f:0b:52:53:73:37:35:85:99:04:ce:09:40:68:38:&lt;BR /&gt;
                    5c:ed:0f:52:ff:89:31:e8:b7:c7:f6:82:8d:bc:12:&lt;BR /&gt;
                    fa:34:e1:53:65:47:af:4c:5d:03:ab:a0:7f:64:3b:&lt;BR /&gt;
                    b2:24:b8:da:db:4e:16:fb:09:3e:11:1f:aa:5e:b3:&lt;BR /&gt;
                    b2:20:d6:78:99:3d:ed:c8:74:5b:94:e9:b2:bb:12:&lt;BR /&gt;
                    c6:db:85:fa:4c:ec:f3:8b:41:28:6b:03:2e:e4:c6:&lt;BR /&gt;
                    11:d4:47:ec:21:c5:8a:70:e0:2f:64:bd:e5:28:f7:&lt;BR /&gt;
                    a8:c9:a3:8d:e6:f1:10:b8:59&lt;BR /&gt;
                Exponent: 65537 (0x10001)&lt;BR /&gt;
    Signature Algorithm: sha1WithRSAEncryption&lt;BR /&gt;
        71:91:88:bd:22:cb:aa:45:3c:9e:ec:43:8d:a3:78:cb:d2:f1:&lt;BR /&gt;
        b6:16:a3:66:80:ba:68:55:c8:18:0d:6f:a9:1a:2a:c2:f3:cf:&lt;BR /&gt;
        a0:c2:b6:0a:f1:8b:f4:9b:e1:e4:70:d3:5c:8c:b1:75:2f:bf:&lt;BR /&gt;
        bd:fc:de:e1:bd:c9:a1:ac:54:fe:99:3e:d1:29:9a:a6:9b:b5:&lt;BR /&gt;
        7c:d3:2f:4e:4e:f2:f6:af:a1:0b:cc:e1:d2:e7:1d:3a:27:0c:&lt;BR /&gt;
        7d:21:4e:78:1e:d1:45:32:da:79:0c:b0:8a:48:3f:3f:fa:23:&lt;BR /&gt;
        3e:71:6b:6f:63:c8:21:ee:c8:a6:86:4e:18:b7:40:52:22:29:&lt;BR /&gt;
        48:38&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 10:02:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101157#M21193</guid>
      <dc:creator>mcalautti</dc:creator>
      <dc:date>2020-09-28T10:02:39Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101158#M21194</link>
      <description>&lt;P&gt;I'd start with looking at the forwarder.pem file with vi and openssl first.&lt;/P&gt;

&lt;P&gt;With vi, it should be readable text with "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----" blocks.  Next use openssl and inspect the data returned:&lt;BR /&gt;
openssl x509 -inform PEM -in &lt;YOUR_FILE&gt; -text -noout&lt;/YOUR_FILE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2011 21:19:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101158#M21194</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2011-10-31T21:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101159#M21195</link>
      <description>&lt;P&gt;ok.. I see the CERT in the file..&lt;/P&gt;

&lt;P&gt;i added the output from openssl to the description.. looks ok to me.. what do you think ?&lt;BR /&gt;
thanks &lt;BR /&gt;
mike&lt;/P&gt;</description>
      <pubDate>Tue, 01 Nov 2011 02:00:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101159#M21195</guid>
      <dc:creator>mcalautti</dc:creator>
      <dc:date>2011-11-01T02:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101160#M21196</link>
      <description>&lt;P&gt;I just ended up recreating and it worked.. via&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/7164/how-do-i-set-up-ssl-forwarding-with-new-self-signed-certificates-and-authentication"&gt;http://splunk-base.splunk.com/answers/7164/how-do-i-set-up-ssl-forwarding-with-new-self-signed-certificates-and-authentication&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Nov 2011 16:00:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101160#M21196</guid>
      <dc:creator>mcalautti</dc:creator>
      <dc:date>2011-11-01T16:00:14Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101161#M21197</link>
      <description>&lt;P&gt;We just ran into this using conf files working fine on a OpenSolaris 32-bit - not working on Ubuntu 10.04 TLS (64-bit)&lt;/P&gt;

&lt;P&gt;The problem was the decryption of the password, pasting the real in as plain text worked, and the resulting encrypted string was different on the Ubuntu.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2011 10:26:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101161#M21197</guid>
      <dc:creator>moseisleydk</dc:creator>
      <dc:date>2011-11-17T10:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101162#M21198</link>
      <description>&lt;P&gt;I just saw the same behavior between two Windows 7 Professional x64 machines - pasting the password in plaintext worked. Thanks for the idea.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2012 20:31:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101162#M21198</guid>
      <dc:creator>andyspusm</dc:creator>
      <dc:date>2012-02-09T20:31:08Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101163#M21199</link>
      <description>&lt;P&gt;This error occurs when splunk tries to decrypt the RSA private key in server.pem with the wrong password.&lt;BR /&gt;&lt;BR /&gt;
I'll show you how to fix this by decrypting the cert by hand as long as you are using default splunk signing CAs.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; 1. Delete server.pem from your universal forwarder and restart splunk (this will recreate server.pem with a default password of 'password')
 2. Decrypt the private RSA key 'openssl rsa -in server.pem -out server_unprotected.pem'
 3. Since server_unprotected.pem will only have the decrypted RSA private key in it, copy &amp;amp; paste the other two blocks from server.pem (don't copy over the original encrypted RSA private key)
 4. mv splunk_unprotected.pem server.pem
 5. Restart splunk
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 12 Jul 2013 21:33:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101163#M21199</guid>
      <dc:creator>nrpeter</dc:creator>
      <dc:date>2013-07-12T21:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101164#M21200</link>
      <description>&lt;P&gt;It works like a charm. Thanks peter. One typo in the point 4 where it should be server.pem and not splunk.pem&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2015 12:30:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101164#M21200</guid>
      <dc:creator>karthi4k</dc:creator>
      <dc:date>2015-01-28T12:30:58Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101165#M21201</link>
      <description>&lt;P&gt;life saver bro, other than the typo on #4.  This is a solid fix.  &lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2016 00:50:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101165#M21201</guid>
      <dc:creator>dhillny</dc:creator>
      <dc:date>2016-06-22T00:50:06Z</dc:date>
    </item>
    <item>
      <title>Re: splunk fowarder SSL error ERROR TcpOutputProc</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101166#M21202</link>
      <description>&lt;P&gt;this should be the answer indeed!!!!&lt;/P&gt;</description>
      <pubDate>Tue, 02 Oct 2018 08:06:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/splunk-fowarder-SSL-error-ERROR-TcpOutputProc/m-p/101166#M21202</guid>
      <dc:creator>wqiu_splunk</dc:creator>
      <dc:date>2018-10-02T08:06:21Z</dc:date>
    </item>
  </channel>
</rss>

