<?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: Why am I getting &amp;quot;Socket error communicating with splunkd&amp;quot; when I try to reload my deployment server to push out new configurations? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130646#M4939</link>
    <description>&lt;P&gt;This happened to us a lot after we upgraded to splunk 6.4 version,  We ended up needing to use the deployment command "splunk reload deploy-server -timeout 200" where 200 is 200 seconds.  You are just telling splunk to give the deployment a little more time before it times out.  This could be required if you are deploying a large number of apps to a large number of servers.  Hope that helps!&lt;/P&gt;</description>
    <pubDate>Fri, 26 Aug 2016 11:39:28 GMT</pubDate>
    <dc:creator>mookiie2005</dc:creator>
    <dc:date>2016-08-26T11:39:28Z</dc:date>
    <item>
      <title>Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130643#M4936</link>
      <description>&lt;P&gt;Socket error communicating with splunkd (error=The read operation timed out), path = /services/deployment/server/config/_reload&lt;/P&gt;

&lt;P&gt;I get this error whenever i try to reload my deployment server to push out new configs.  It wont let me make any changes.  I have opened up a ticket with Splunk support (Case# - 201659) but to no avail.  Has anyone else seen this type of issue and know how to fix it or what is causing the issue? &lt;/P&gt;</description>
      <pubDate>Fri, 21 Nov 2014 16:44:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130643#M4936</guid>
      <dc:creator>JoeSco27</dc:creator>
      <dc:date>2014-11-21T16:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130644#M4937</link>
      <description>&lt;P&gt;Restart splunkd of the deployment server should fix the problem. But i am not sure what exactly caused this error yet. Anyone knows about the root cause of this error?&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2015 23:22:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130644#M4937</guid>
      <dc:creator>itmonitoring</dc:creator>
      <dc:date>2015-02-03T23:22:17Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130645#M4938</link>
      <description>&lt;P&gt;I have the same problem.  Take a look at this posting:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/170244/splunk-reload-deploy-server%E3%82%92%E5%AE%9F%E8%A1%8C%E3%81%99%E3%82%8B%E3%81%A8socket-error-%E3%81%A8%E3%81%AA%E3%82%8B.html"&gt;http://answers.splunk.com/answers/170244/splunk-reload-deploy-server%E3%82%92%E5%AE%9F%E8%A1%8C%E3%81%99%E3%82%8B%E3%81%A8socket-error-%E3%81%A8%E3%81%AA%E3%82%8B.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The above does not work for me, I end up being presented with the following:&lt;BR /&gt;
"Too many HTTP threads (659) already running, try again later&lt;/P&gt;

&lt;P&gt;The server can not presently handle the given request."&lt;/P&gt;

&lt;P&gt;Did you ever find a solution?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Feb 2015 14:31:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130645#M4938</guid>
      <dc:creator>LiquidTension</dc:creator>
      <dc:date>2015-02-18T14:31:38Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130646#M4939</link>
      <description>&lt;P&gt;This happened to us a lot after we upgraded to splunk 6.4 version,  We ended up needing to use the deployment command "splunk reload deploy-server -timeout 200" where 200 is 200 seconds.  You are just telling splunk to give the deployment a little more time before it times out.  This could be required if you are deploying a large number of apps to a large number of servers.  Hope that helps!&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2016 11:39:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130646#M4939</guid>
      <dc:creator>mookiie2005</dc:creator>
      <dc:date>2016-08-26T11:39:28Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130647#M4940</link>
      <description>&lt;P&gt;This is the answer that solved my problem. Just add the -timeout 200 and no issues. &lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2017 14:39:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130647#M4940</guid>
      <dc:creator>hortonew</dc:creator>
      <dc:date>2017-01-27T14:39:17Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130648#M4941</link>
      <description>&lt;P&gt;Thank this also help me too. I was running into the issue 2 years ago decided just to ignore it.  the flag provides so much satisfaction to get successful reloading message &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Apr 2017 18:56:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130648#M4941</guid>
      <dc:creator>cesaccenturefed</dc:creator>
      <dc:date>2017-04-28T18:56:55Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130649#M4942</link>
      <description>&lt;P&gt;same issue i am facing now aslo i have tried with -timeout 200 but still socket error message it showing&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 08:31:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130649#M4942</guid>
      <dc:creator>shaikhussain2</dc:creator>
      <dc:date>2018-08-14T08:31:07Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130650#M4943</link>
      <description>&lt;P&gt;Hi. Has anyone figured &lt;EM&gt;what&lt;/EM&gt; causes the socket error message? I'm getting the same error, but I feel like adding the timeout flag on the reload deploy-server command is just hiding the problem, not actually fixing it. I've noticed that almost all my RAM is used for cache, but I don't know if this is related or not.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 14:10:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130650#M4943</guid>
      <dc:creator>hettervik</dc:creator>
      <dc:date>2019-03-15T14:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to push out new configurations?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130651#M4944</link>
      <description>&lt;P&gt;Hi, This might be in your environment using in 1 server 2 components such like we were using 2 component in 1 server ( SH &amp;amp; DS ), so we have faced same issue and then separated both in separate servers and then the command was executing  perfectly.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 14:57:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/130651#M4944</guid>
      <dc:creator>shaikhussain2</dc:creator>
      <dc:date>2019-03-15T14:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I getting "Socket error communicating with splunkd" when I try to reload my deployment server to pu</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/612410#M26112</link>
      <description>&lt;P&gt;Reloading servers can take a bit more time if your environment is big. that is you have thousands of forwarders connecting to your DS.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 12:28:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Why-am-I-getting-quot-Socket-error-communicating-with-splunkd/m-p/612410#M26112</guid>
      <dc:creator>splunkoptimus</dc:creator>
      <dc:date>2022-09-08T12:28:08Z</dc:date>
    </item>
  </channel>
</rss>

