<?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 do you debug custom search command: Error in 'script'? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-do-you-debug-custom-search-command-Error-in-script/m-p/460495#M99469</link>
    <description>&lt;P&gt;I have no idea why this issue was connected to the logger but once I set &lt;CODE&gt;stderr_dest = log&lt;/CODE&gt; instead &lt;CODE&gt;stderr_dest = message&lt;/CODE&gt; it started working.&lt;/P&gt;</description>
    <pubDate>Mon, 02 Dec 2019 13:57:40 GMT</pubDate>
    <dc:creator>seva98</dc:creator>
    <dc:date>2019-12-02T13:57:40Z</dc:date>
    <item>
      <title>How do you debug custom search command: Error in 'script'?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-you-debug-custom-search-command-Error-in-script/m-p/460494#M99468</link>
      <description>&lt;P&gt;How do I debug following?&lt;/P&gt;

&lt;P&gt;I have custom search command generatereport that I have developed on Linux, I am using logger to print information I need.  Everything works fine there. I even get error with python output line of code if something is wrong.&lt;/P&gt;

&lt;P&gt;But when I move my command to Windows I don't receive detailed error message, only Error in 'script' and it is almost impossible to debug. Is there a way how to read python log and found out what happened? Script had to fail somewhere.&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/7827iA5453232778CCDAA/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2019 09:43:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-you-debug-custom-search-command-Error-in-script/m-p/460494#M99468</guid>
      <dc:creator>seva98</dc:creator>
      <dc:date>2019-10-15T09:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: How do you debug custom search command: Error in 'script'?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-you-debug-custom-search-command-Error-in-script/m-p/460495#M99469</link>
      <description>&lt;P&gt;I have no idea why this issue was connected to the logger but once I set &lt;CODE&gt;stderr_dest = log&lt;/CODE&gt; instead &lt;CODE&gt;stderr_dest = message&lt;/CODE&gt; it started working.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2019 13:57:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-you-debug-custom-search-command-Error-in-script/m-p/460495#M99469</guid>
      <dc:creator>seva98</dc:creator>
      <dc:date>2019-12-02T13:57:40Z</dc:date>
    </item>
  </channel>
</rss>

