<?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: Cannot remove forward-server in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492805#M84244</link>
    <description>&lt;P&gt;Good idea!&lt;BR /&gt;
I executed that command and found one suspect:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout:clustered_indexers]

[indexer_discovery:cluster_master]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Could this be the issue? Is it safe to remove? We are going to retire the entire on-prem indexer setup, we do already have all data in SplunkCloud. &lt;/P&gt;</description>
    <pubDate>Wed, 18 Mar 2020 13:54:06 GMT</pubDate>
    <dc:creator>andreasknutsson</dc:creator>
    <dc:date>2020-03-18T13:54:06Z</dc:date>
    <item>
      <title>Cannot remove forward-server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492803#M84242</link>
      <description>&lt;P&gt;I have inherited an old on-prem &lt;STRONG&gt;Splunk 7.0.2&lt;/STRONG&gt;  installation that I'm now trying to reconfigure to forward data to our SplunkCloud instance.&lt;BR /&gt;
I have installed the SplunkCloud app on the search-head that is acting as deploy-server. It is now forwarding its internal logs to the cloud as expected. Now I want to remove the old forward-servers. &lt;/P&gt;

&lt;P&gt;When I execute: &lt;CODE&gt;./splunk list forward-server&lt;/CODE&gt;&lt;BR /&gt;
I get this: &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;Active forwards:&lt;BR /&gt;
        10.yy.167.67:9997 (ssl)&lt;BR /&gt;
        inputs1.q.splunkcloud.com:9997&lt;BR /&gt;
(ssl) Configured but inactive&lt;BR /&gt;
forwards:&lt;BR /&gt;
        10.yy.167.68:9997&lt;BR /&gt;
        inputs10.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs11.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs12.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs13.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs14.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs15.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs2.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs3.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs4.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs5.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs6.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs7.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs8.q.splunkcloud.com:9997&lt;BR /&gt;
        inputs9.q.splunkcloud.com:9997&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;This looks correct. &lt;BR /&gt;
Then I execute: &lt;CODE&gt;./splunk remove forward-server 10.yy.167.68:9997&lt;/CODE&gt; and get this message:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;In handler 'tcpout-server': Type = outputs, Context = (user: nobody, app:, root: /opt/splunk/etc), Acting as = nobody: Invalid configuration context: Cannot read configuration if user context is set but app context is not&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;I get the same kind of message if I try to do this in the web gui.&lt;/P&gt;

&lt;P&gt;I have tried to find the configuration file that contains this forward-server config but I cannot locate it. &lt;BR /&gt;
It should be &lt;CODE&gt;/splunk/etc/system/local/outputs.conf&lt;/CODE&gt; but there is no such file. I have tried grabbing for the IP address in the entire /etc directory structure but got no matches!&lt;/P&gt;

&lt;P&gt;Does anyone have any input on how to proceed?&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Andreas&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2020 09:52:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492803#M84242</guid>
      <dc:creator>andreasknutsson</dc:creator>
      <dc:date>2020-03-18T09:52:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot remove forward-server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492804#M84243</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Try to find out &lt;CODE&gt;tcpout&lt;/CODE&gt; stanza from outputs.conf using btool and find that server.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$PLUNK_HOME/bin/splunk cmd btool outputs list --debug
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 18 Mar 2020 12:35:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492804#M84243</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2020-03-18T12:35:28Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot remove forward-server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492805#M84244</link>
      <description>&lt;P&gt;Good idea!&lt;BR /&gt;
I executed that command and found one suspect:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout:clustered_indexers]

[indexer_discovery:cluster_master]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Could this be the issue? Is it safe to remove? We are going to retire the entire on-prem indexer setup, we do already have all data in SplunkCloud. &lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2020 13:54:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492805#M84244</guid>
      <dc:creator>andreasknutsson</dc:creator>
      <dc:date>2020-03-18T13:54:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot remove forward-server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492806#M84245</link>
      <description>&lt;P&gt;Server &lt;CODE&gt;10.yy.167.67&lt;/CODE&gt; under any &lt;CODE&gt;tcpout&lt;/CODE&gt; stanza with parameter &lt;CODE&gt;server&lt;/CODE&gt; ? &lt;/P&gt;

&lt;P&gt;It looks like you are using Indexer discovery and due to that &lt;CODE&gt;10.yy.167.67&lt;/CODE&gt; indexer is coming from Cluster Master, in that case that server will be removed from forward-server list when you'll decommission that indexer from Indexer Cluster.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2020 14:14:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cannot-remove-forward-server/m-p/492806#M84245</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2020-03-18T14:14:57Z</dc:date>
    </item>
  </channel>
</rss>

