<?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: Checking conf files for problems... in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Checking-conf-files-for-problems/m-p/197917#M39276</link>
    <description>&lt;P&gt;This isn't exactly the answer to your question, but the btool utility can be useful for troubleshooting configuration files. See &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.1/Troubleshooting/Usebtooltotroubleshootconfigurations"&gt;Use btool to troubleshoot configurations&lt;/A&gt; in the Troubleshooting Manual. There are &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.1/Troubleshooting/CommandlinetoolsforusewithSupport"&gt;other command-line troubleshooting tools&lt;/A&gt;, but I don't know of a command or tool that runs that check. Hopefully someone else will reply here with a more direct answer.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Jun 2014 15:45:17 GMT</pubDate>
    <dc:creator>ChrisG</dc:creator>
    <dc:date>2014-06-13T15:45:17Z</dc:date>
    <item>
      <title>Checking conf files for problems...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Checking-conf-files-for-problems/m-p/197916#M39275</link>
      <description>&lt;P&gt;On Splunk start up I see:&lt;BR /&gt;&lt;BR /&gt;
Undocumented key used in transforms.conf; stanza='anon' setting='DEST_KEY' key='raw'&lt;BR /&gt;&lt;BR /&gt;
Please resolve these problems by correcting typos in key names, or by adding them to [accepted_keys] in transforms.conf if they are intended.&lt;BR /&gt;&lt;BR /&gt;
All preliminary checks passed.&lt;/P&gt;

&lt;P&gt;How can I run this check from the CLI? Is there some python script I can kick off?  &lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:51:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Checking-conf-files-for-problems/m-p/197916#M39275</guid>
      <dc:creator>rroberts</dc:creator>
      <dc:date>2020-09-28T16:51:18Z</dc:date>
    </item>
    <item>
      <title>Re: Checking conf files for problems...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Checking-conf-files-for-problems/m-p/197917#M39276</link>
      <description>&lt;P&gt;This isn't exactly the answer to your question, but the btool utility can be useful for troubleshooting configuration files. See &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.1/Troubleshooting/Usebtooltotroubleshootconfigurations"&gt;Use btool to troubleshoot configurations&lt;/A&gt; in the Troubleshooting Manual. There are &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.1/Troubleshooting/CommandlinetoolsforusewithSupport"&gt;other command-line troubleshooting tools&lt;/A&gt;, but I don't know of a command or tool that runs that check. Hopefully someone else will reply here with a more direct answer.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jun 2014 15:45:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Checking-conf-files-for-problems/m-p/197917#M39276</guid>
      <dc:creator>ChrisG</dc:creator>
      <dc:date>2014-06-13T15:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: Checking conf files for problems...</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Checking-conf-files-for-problems/m-p/197918#M39277</link>
      <description>&lt;P&gt;Yes, Im familiar with btool. Not exactly what Im looking for but thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jun 2014 15:50:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Checking-conf-files-for-problems/m-p/197918#M39277</guid>
      <dc:creator>rroberts</dc:creator>
      <dc:date>2014-06-13T15:50:47Z</dc:date>
    </item>
  </channel>
</rss>

