<?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 How to use cmd parsetest for troubleshooting? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-use-cmd-parsetest-for-troubleshooting/m-p/170296#M34412</link>
    <description>&lt;P&gt;From&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Troubleshooting/CommandlinetoolsforusewithSupport" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Troubleshooting/CommandlinetoolsforusewithSupport&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Example:&lt;BR /&gt;
    parsetest "10/11/2009 12:11:13" "syslog"&lt;/P&gt;

&lt;P&gt;I adapted it to my current use case but can't figure out what it's trying to do&lt;/P&gt;

&lt;P&gt;/opt/splunk/bin/splunk cmd /opt/splunk/bin/parsetest "2014-11-01 23:50:21,318" "my_test_sourcetype"&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 18:33:07 GMT</pubDate>
    <dc:creator>splunk_zen</dc:creator>
    <dc:date>2020-09-28T18:33:07Z</dc:date>
    <item>
      <title>How to use cmd parsetest for troubleshooting?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-use-cmd-parsetest-for-troubleshooting/m-p/170296#M34412</link>
      <description>&lt;P&gt;From&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Troubleshooting/CommandlinetoolsforusewithSupport" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Troubleshooting/CommandlinetoolsforusewithSupport&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Example:&lt;BR /&gt;
    parsetest "10/11/2009 12:11:13" "syslog"&lt;/P&gt;

&lt;P&gt;I adapted it to my current use case but can't figure out what it's trying to do&lt;/P&gt;

&lt;P&gt;/opt/splunk/bin/splunk cmd /opt/splunk/bin/parsetest "2014-11-01 23:50:21,318" "my_test_sourcetype"&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;BR /&gt;
Conf is currently being modified by process 15206.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 18:33:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-use-cmd-parsetest-for-troubleshooting/m-p/170296#M34412</guid>
      <dc:creator>splunk_zen</dc:creator>
      <dc:date>2020-09-28T18:33:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to use cmd parsetest for troubleshooting?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-use-cmd-parsetest-for-troubleshooting/m-p/170297#M34413</link>
      <description>&lt;P&gt;Bump. Anyone with experience using bin/parsetest?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jul 2015 10:35:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-use-cmd-parsetest-for-troubleshooting/m-p/170297#M34413</guid>
      <dc:creator>splunk_zen</dc:creator>
      <dc:date>2015-07-17T10:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to use cmd parsetest for troubleshooting?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-use-cmd-parsetest-for-troubleshooting/m-p/170298#M34414</link>
      <description>&lt;P&gt;Hi splunk_zen,&lt;/P&gt;

&lt;P&gt;if you run &lt;CODE&gt;splunk cmd parsetest --help&lt;/CODE&gt; you will get some options:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Usage: /opt/splunk/bin/splunkd [OPTION...]
  --nodaemon      causes the system not to daemonize
  -c STRING       override the config path
  -h              no longer supported
  -i              no longer supported
  -n STRING       the component name to start with
  -p INT          the management port Splunkd will listen on
  --debug         start with debug log config

Help options:
  -?, --help      Show this help message
  --usage         Display brief usage message
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You maybe noticed, that is says &lt;CODE&gt;Usage: /opt/splunk/bin/splunkd [OPTION...]&lt;/CODE&gt; so this means the parsetest command should be used when Splunk is stopped. Running the &lt;CODE&gt;parsetest&lt;/CODE&gt; command will start a Splunk process with the provided options, like &lt;CODE&gt;--debug&lt;/CODE&gt; which will increase debug verbosity in &lt;CODE&gt;splunkd.log&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;But I would only use it when advised by Splunk support to do so, like mentioned in the docs &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.3/Troubleshooting/CommandlinetoolsforusewithSupport"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.3/Troubleshooting/CommandlinetoolsforusewithSupport&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Mon, 21 Mar 2016 22:05:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-use-cmd-parsetest-for-troubleshooting/m-p/170298#M34414</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-03-21T22:05:48Z</dc:date>
    </item>
  </channel>
</rss>

