<?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: Python Alert Script not running when using pyodbc in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Python-Alert-Script-not-running-when-using-pyodbc/m-p/147363#M2393</link>
    <description>&lt;P&gt;Oh, and just to be clear, the script runs fine if I remove the reference to pyodbc and skip my table lookup (ultimately, though, I need to make this call).&lt;/P&gt;</description>
    <pubDate>Wed, 12 Feb 2014 01:19:11 GMT</pubDate>
    <dc:creator>bruceclarke</dc:creator>
    <dc:date>2014-02-12T01:19:11Z</dc:date>
    <item>
      <title>Python Alert Script not running when using pyodbc</title>
      <link>https://community.splunk.com/t5/Alerting/Python-Alert-Script-not-running-when-using-pyodbc/m-p/147362#M2392</link>
      <description>&lt;P&gt;All,&lt;/P&gt;

&lt;P&gt;I ran into an issue with my python alert script after trying to import pyodbc into my script. I read elsewhere that it might be due to Splunk's version of python not being able to import pyodbc. So, I created a wrapper python script as described here: &lt;A href="http://answers.splunk.com/answers/10839/scripted-lookup-script-doesnt-work-with-splunk-python-version-but-works-fine-with-python-27"&gt;http://answers.splunk.com/answers/10839/scripted-lookup-script-doesnt-work-with-splunk-python-version-but-works-fine-with-python-27&lt;/A&gt;.&lt;/P&gt;

&lt;P&gt;When I run &lt;PRE&gt;splunk cmd python "path/to/python/wrapper"&lt;/PRE&gt; everything works fine. I see the output and it sends an email as I expected. However, when the alert gets triggered by Splunk, the script fails. I see the following error in splunkd.log:&lt;/P&gt;

&lt;PRE&gt;02-11-2014 20:04:05.573 -0500 WARN  script - Maxinputs must be at least 10000, command name="runshellscript"&lt;/PRE&gt;

&lt;P&gt;Any ideas on how to fix this? Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2014 01:18:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Python-Alert-Script-not-running-when-using-pyodbc/m-p/147362#M2392</guid>
      <dc:creator>bruceclarke</dc:creator>
      <dc:date>2014-02-12T01:18:23Z</dc:date>
    </item>
    <item>
      <title>Re: Python Alert Script not running when using pyodbc</title>
      <link>https://community.splunk.com/t5/Alerting/Python-Alert-Script-not-running-when-using-pyodbc/m-p/147363#M2393</link>
      <description>&lt;P&gt;Oh, and just to be clear, the script runs fine if I remove the reference to pyodbc and skip my table lookup (ultimately, though, I need to make this call).&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2014 01:19:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Python-Alert-Script-not-running-when-using-pyodbc/m-p/147363#M2393</guid>
      <dc:creator>bruceclarke</dc:creator>
      <dc:date>2014-02-12T01:19:11Z</dc:date>
    </item>
    <item>
      <title>Re: Python Alert Script not running when using pyodbc</title>
      <link>https://community.splunk.com/t5/Alerting/Python-Alert-Script-not-running-when-using-pyodbc/m-p/147364#M2394</link>
      <description>&lt;P&gt;There were two versions of python on the machine. This led to a conflict that was masked by a hard to decipher error message in Splunk.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2014 22:36:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Python-Alert-Script-not-running-when-using-pyodbc/m-p/147364#M2394</guid>
      <dc:creator>bruceclarke</dc:creator>
      <dc:date>2014-12-08T22:36:25Z</dc:date>
    </item>
  </channel>
</rss>

