<?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: Windows props.conf source stanza - Can't use the embedded Python interpreter in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Windows-props-conf-source-stanza-Can-t-use-the-embedded-Python/m-p/177836#M35654</link>
    <description>&lt;P&gt;Solved by installing (and recommending users to) standalone Python interpreter in Windows&lt;/P&gt;

&lt;P&gt;Thus i could never used the embedded Python interpreter only in Windows.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Mar 2015 12:24:15 GMT</pubDate>
    <dc:creator>guilmxm</dc:creator>
    <dc:date>2015-03-23T12:24:15Z</dc:date>
    <item>
      <title>Windows props.conf source stanza - Can't use the embedded Python interpreter</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-props-conf-source-stanza-Can-t-use-the-embedded-Python/m-p/177835#M35653</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have developed an App "Nmon performance Monitor for Unix and Linux Systems" (&lt;A href="http://apps.splunk.com/app/1753/"&gt;http://apps.splunk.com/app/1753/&lt;/A&gt;)&lt;/P&gt;

&lt;P&gt;I am currently working on a new release which will allow Windows OS to achieve the conversion step required by the App, this is being achieved by a third party Python script.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Currently, for *nix hosts, the props.conf source stanza is:&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# Source stanza for nmon2csv.py script
# This source stanza will be called by the archive processor to convert NMON raw data into csv files
# SPlunk can manage. See inputs.conf for the associated monitor
# The standard nmon App and PA-nmon App will use the embedded splunk interpreter

[source::.../*.nmon]

invalid_cause = archive
unarchive_cmd = $SPLUNK_HOME/bin/splunk cmd python $SPLUNK_HOME/etc/apps/nmon/bin/nmon2csv.py
sourcetype = nmon_processing
NO_BINARY_CHECK = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;I have tried with no sucess to transpose this to Windows, like:&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::...\.*.nmon]

invalid_cause = archive
unarchive_cmd = $SPLUNK_HOME\bin\splunk.exe cmd python $SPLUNK_HOME\Splunk\etc\apps\nmon\bin\nmon2csv.py
sourcetype = nmon_processing
NO_BINARY_CHECK = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It does not work, giving errors in splunkd.log like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; ERROR ArchiveContext - archive writer failure: errno=Le canal de communication est sur le point d’être fermé.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have tried to use the full path of Splunk and i have tried to protect the "Program Files" directory name with no luck (with " () ' )&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::...\.*.nmon]

invalid_cause = archive
unarchive_cmd = C:\Program Files\Splunk\bin\splunk.exe cmd python C:\Program Files\Splunk\etc\apps\nmon\bin\nmon2csv.py
sourcetype = nmon_processing
NO_BINARY_CHECK = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I could be tempted to think that the problem comes from the directory name and its white space, but if i install as a dependency a Python 2x package in Windows (so i can later call any python script from Windows) and if i simply use:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::...\.*.nmon]

invalid_cause = archive
unarchive_cmd = C:\Program Files\Splunk\etc\apps\nmon\bin\nmon2csv.py
sourcetype = nmon_processing
NO_BINARY_CHECK = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;Everything works perfectly and my lib script will convert my data as exepected.&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;My goal is to use the embedded Python interpreter not to have to ask users to install to be able to use the App.&lt;/P&gt;

&lt;P&gt;As it is, i am currently unable to use the embedded Python interpreter in Windows where i do not have any issue with any other *nix OS.&lt;/P&gt;

&lt;P&gt;Does anyone has some idea ?&lt;/P&gt;

&lt;P&gt;Thanks !&lt;/P&gt;</description>
      <pubDate>Mon, 11 Aug 2014 14:56:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-props-conf-source-stanza-Can-t-use-the-embedded-Python/m-p/177835#M35653</guid>
      <dc:creator>guilmxm</dc:creator>
      <dc:date>2014-08-11T14:56:11Z</dc:date>
    </item>
    <item>
      <title>Re: Windows props.conf source stanza - Can't use the embedded Python interpreter</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-props-conf-source-stanza-Can-t-use-the-embedded-Python/m-p/177836#M35654</link>
      <description>&lt;P&gt;Solved by installing (and recommending users to) standalone Python interpreter in Windows&lt;/P&gt;

&lt;P&gt;Thus i could never used the embedded Python interpreter only in Windows.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Mar 2015 12:24:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-props-conf-source-stanza-Can-t-use-the-embedded-Python/m-p/177836#M35654</guid>
      <dc:creator>guilmxm</dc:creator>
      <dc:date>2015-03-23T12:24:15Z</dc:date>
    </item>
  </channel>
</rss>

