<?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: How to troubleshoot Deployment Server (6.1.4) startup error &amp;quot;DeploymentClient - DC shares a Splunk instance with its DS; unsupported configuration&amp;quot; in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-troubleshoot-Deployment-Server-6-1-4-startup-error-quot/m-p/159083#M5937</link>
    <description>&lt;P&gt;It sounds like the  Deployment Server is being told to check in with itself.  From what I understand the DS cannot also be a Deployment Client (under the same instance).  I would suggest you check /SplunkPath/etc/system/local/deploymentclient.conf  or check if you have a deployment client app.  &lt;/P&gt;

&lt;P&gt;Remove the offending deploymentclient.conf/app and then in your serverclass.conf  put your DS on the blacklist.  &lt;/P&gt;</description>
    <pubDate>Mon, 15 Dec 2014 21:21:38 GMT</pubDate>
    <dc:creator>dantxto</dc:creator>
    <dc:date>2014-12-15T21:21:38Z</dc:date>
    <item>
      <title>How to troubleshoot Deployment Server (6.1.4) startup error "DeploymentClient - DC shares a Splunk instance with its DS; unsupported configuration"</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-troubleshoot-Deployment-Server-6-1-4-startup-error-quot/m-p/159082#M5936</link>
      <description>&lt;P&gt;Architecture: deployment server, universal forwarders, indexers, search heads.&lt;BR /&gt;
After a tech refresh of one forwarder the deployment box was restarted (reload deployment-server)  and the following error is showing up:&lt;BR /&gt;
ERROR DC:DeploymentClient - DC shares a Splunk  instance with its DS; unsupported configuration. &lt;/P&gt;

&lt;P&gt;Config data is not making it to the new forwarder.&lt;BR /&gt;
Also, on the DS review of the splunk/etc/apps directory shows most of the same directories (apps) that appear in the /etc/deployment-apps directory.&lt;BR /&gt;
Is this a problem?  If so what exactly should be the only directories in the 'apps' directory of a dedicated DS?&lt;BR /&gt;
If not - what is the best way to trace down the above DC error?&lt;BR /&gt;
Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2014 21:15:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-troubleshoot-Deployment-Server-6-1-4-startup-error-quot/m-p/159082#M5936</guid>
      <dc:creator>paulahoffman</dc:creator>
      <dc:date>2014-12-15T21:15:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to troubleshoot Deployment Server (6.1.4) startup error "DeploymentClient - DC shares a Splunk instance with its DS; unsupported configuration"</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-troubleshoot-Deployment-Server-6-1-4-startup-error-quot/m-p/159083#M5937</link>
      <description>&lt;P&gt;It sounds like the  Deployment Server is being told to check in with itself.  From what I understand the DS cannot also be a Deployment Client (under the same instance).  I would suggest you check /SplunkPath/etc/system/local/deploymentclient.conf  or check if you have a deployment client app.  &lt;/P&gt;

&lt;P&gt;Remove the offending deploymentclient.conf/app and then in your serverclass.conf  put your DS on the blacklist.  &lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2014 21:21:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-troubleshoot-Deployment-Server-6-1-4-startup-error-quot/m-p/159083#M5937</guid>
      <dc:creator>dantxto</dc:creator>
      <dc:date>2014-12-15T21:21:38Z</dc:date>
    </item>
  </channel>
</rss>

