<?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: deployment-server socket timeout in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123347#M4683</link>
    <description>&lt;P&gt;Thank you, I will check for that!&lt;/P&gt;</description>
    <pubDate>Thu, 07 Aug 2014 16:40:52 GMT</pubDate>
    <dc:creator>bpwoods</dc:creator>
    <dc:date>2014-08-07T16:40:52Z</dc:date>
    <item>
      <title>deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123340#M4676</link>
      <description>&lt;P&gt;Hi version 6.11 , added over 90 hosts in the Forwarder Management in server class.&lt;BR /&gt;
getting error on the splunk web gui "Gap in numbered regexes: expected attribute=whitelist.82 not found"&lt;/P&gt;

&lt;P&gt;i tried reloading the deployment server, and tried to disable it&lt;BR /&gt;
but getting this error on cmd&lt;BR /&gt;
opt/splunk/bin/splunk reload deploy-server Socket error communicating with splunkd (error=The read operation timed out), path = /services/deployment/server/config/_reload&lt;/P&gt;

&lt;P&gt;seems like to only way is to restart the splunk service?&lt;BR /&gt;
any work around?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jun 2014 21:35:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123340#M4676</guid>
      <dc:creator>tlow</dc:creator>
      <dc:date>2014-06-27T21:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123341#M4677</link>
      <description>&lt;P&gt;"Gap in numbered regexes: expected attribute=whitelist.82 not found"&lt;/P&gt;

&lt;P&gt;For this error, check the &lt;CODE&gt;serverclass.conf&lt;/CODE&gt; file on the deployment server. You should see a number of whitelist entries. They must be in sequential ascending order. My guess is that a line was deleted, leaving a gap. You can fix this manually. &lt;/P&gt;

&lt;P&gt;You should reload the deployment server after fixing &lt;CODE&gt;serverclass.conf&lt;/CODE&gt; using the command&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;/opt/splunk/bin/splunk reload deploy-server&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;If that doesn't work, you should try restarting Splunk.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jun 2014 21:51:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123341#M4677</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-06-27T21:51:45Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123342#M4678</link>
      <description>&lt;P&gt;yes, tried to fix the  serverclass.conf by removing the error line, and tried /opt/splunk/bin/splunk reload deploy-server,  but getting the error..&lt;/P&gt;

&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;is this a bug?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jun 2014 22:40:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123342#M4678</guid>
      <dc:creator>tlow</dc:creator>
      <dc:date>2014-06-27T22:40:50Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123343#M4679</link>
      <description>&lt;P&gt;Did you restart Splunk? I suggest that you try that next...&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jun 2014 01:55:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123343#M4679</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-06-28T01:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123344#M4680</link>
      <description>&lt;P&gt;Having same error, restarted splunk coupl etimes, checked serverclass.conf, still having same error&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jul 2014 14:09:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123344#M4680</guid>
      <dc:creator>dmikon</dc:creator>
      <dc:date>2014-07-07T14:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123345#M4681</link>
      <description>&lt;P&gt;Any luck on this?  Splunk will not start with my serverclass.conf in place.  It becomes completely unresponsive, even after a reboot.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Aug 2014 23:32:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123345#M4681</guid>
      <dc:creator>bpwoods</dc:creator>
      <dc:date>2014-08-06T23:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123346#M4682</link>
      <description>&lt;P&gt;In my case it was some hidden characters in serverclass.conf, you know copy/paste things... i traced them down and everything tip-top now.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Aug 2014 16:33:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123346#M4682</guid>
      <dc:creator>dmikon</dc:creator>
      <dc:date>2014-08-07T16:33:19Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123347#M4683</link>
      <description>&lt;P&gt;Thank you, I will check for that!&lt;/P&gt;</description>
      <pubDate>Thu, 07 Aug 2014 16:40:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123347#M4683</guid>
      <dc:creator>bpwoods</dc:creator>
      <dc:date>2014-08-07T16:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123348#M4684</link>
      <description>&lt;P&gt;I just wasted an appalling amount of time on this problem.   I found a row of blanks or characters that can't be seen in vim in an empty row between a comments block and a [serverClass:.....] statement.  It was in an area where I had recently pasted a couple dozen rows of text.&lt;/P&gt;

&lt;P&gt;We are on 6.1.4.  Something is fragile in the deploy-server when it comes to error-handling in the serverclass.conf.   It also takes quite a while to restart splunkd when the system is in this state, really slows down troubleshooting.&lt;/P&gt;</description>
      <pubDate>Sat, 28 Feb 2015 00:12:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123348#M4684</guid>
      <dc:creator>jeffrogers</dc:creator>
      <dc:date>2015-02-28T00:12:28Z</dc:date>
    </item>
    <item>
      <title>Re: deployment-server socket timeout</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123349#M4685</link>
      <description>&lt;P&gt;I am facing the problem in deployment server the thing is i have a path and sourcetype and index i need to do configuration in deployment server already existing app and inputs.conf file is there and serverclass is already setup, so when i configured the new path, sourcetype the data is not reflecting in splunk and also i am not able to see any changes in universal forwarder i tried CLI command also but no changes has shown and my deployment server is windows server. &lt;BR /&gt;
 even same socket error message is showing whenever i reload the DS&lt;/P&gt;</description>
      <pubDate>Wed, 15 Aug 2018 15:04:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deployment-server-socket-timeout/m-p/123349#M4685</guid>
      <dc:creator>shaikhussain2</dc:creator>
      <dc:date>2018-08-15T15:04:31Z</dc:date>
    </item>
  </channel>
</rss>

