<?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 Symantec Cloud Scripted Input in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294706#M85902</link>
    <description>&lt;P&gt;Evaluating Symantec EndPoint Protection Cloud product which has a technote for getting events into Splunk Enterprise running on a Windows Server.&lt;/P&gt;
&lt;P&gt;Created a scripted input per the Symantec Technote&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.symantec.com/en_US/article.HOWTO128173.html#v126173001" target="_blank"&gt;Symantec Technote&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;however I get the following error in SPLUNKD.log&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;ERROR ExecProcessor - Couldn't start command ""C:\Program Files\Splunk\bin\scripts\wrapper.sh"": FormatMessage was unable to decode error (193), (0xc1)&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;The scripted input uses a wrapper (wrapper.sh) for calling a python script. Contents of the wrapper.sh file are&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;#!/bin/bash&lt;BR /&gt;
/usr/bin/python /Applications/Splunk/bin/scripts/ExportClient.py&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;If I try and execute the actual python script (ExportClient.py) from the command line I get the following error:&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;C:\Program Files\Splunk\bin&amp;gt;splunk cmd python scripts\ExportClient.py&lt;BR /&gt;Traceback (most recent call last):&lt;BR /&gt;File "scripts\ExportClient.py", line 8, in &lt;BR /&gt;import dateutil.parser&lt;BR /&gt;ImportError: No module named dateutil.parser&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;Any help is appreciated.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jun 2020 23:53:05 GMT</pubDate>
    <dc:creator>smaat11</dc:creator>
    <dc:date>2020-06-08T23:53:05Z</dc:date>
    <item>
      <title>Symantec Cloud Scripted Input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294706#M85902</link>
      <description>&lt;P&gt;Evaluating Symantec EndPoint Protection Cloud product which has a technote for getting events into Splunk Enterprise running on a Windows Server.&lt;/P&gt;
&lt;P&gt;Created a scripted input per the Symantec Technote&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.symantec.com/en_US/article.HOWTO128173.html#v126173001" target="_blank"&gt;Symantec Technote&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;however I get the following error in SPLUNKD.log&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;ERROR ExecProcessor - Couldn't start command ""C:\Program Files\Splunk\bin\scripts\wrapper.sh"": FormatMessage was unable to decode error (193), (0xc1)&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;The scripted input uses a wrapper (wrapper.sh) for calling a python script. Contents of the wrapper.sh file are&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;#!/bin/bash&lt;BR /&gt;
/usr/bin/python /Applications/Splunk/bin/scripts/ExportClient.py&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;If I try and execute the actual python script (ExportClient.py) from the command line I get the following error:&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;C:\Program Files\Splunk\bin&amp;gt;splunk cmd python scripts\ExportClient.py&lt;BR /&gt;Traceback (most recent call last):&lt;BR /&gt;File "scripts\ExportClient.py", line 8, in &lt;BR /&gt;import dateutil.parser&lt;BR /&gt;ImportError: No module named dateutil.parser&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;Any help is appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2020 23:53:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294706#M85902</guid>
      <dc:creator>smaat11</dc:creator>
      <dc:date>2020-06-08T23:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: Symantec Cloud Scripted Input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294707#M85903</link>
      <description>&lt;P&gt;Went and coped the dateutil library to the  /Applications/Splunk/bin/scripts/ directory, and tried re-running ExportClient.py script from the command line.  THis time received the following error:&lt;/P&gt;

&lt;HR /&gt;

&lt;PRE&gt;&lt;CODE&gt;C:\Program Files\Splunk\bin&amp;gt;splunk cmd python scripts\ExportClient.py
Traceback (most recent call last):
  File "scripts\ExportClient.py", line 8, in &amp;lt;module&amp;gt;
    import dateutil.parser
  File "C:\Program Files\Splunk\bin\scripts\dateutil\parser\__init__.py", line 2
, in &amp;lt;module&amp;gt;
    from ._parser import parse, parser, parserinfo
  File "C:\Program Files\Splunk\bin\scripts\dateutil\parser\_parser.py", line 42
, in &amp;lt;module&amp;gt;
    import six
ImportError: No module named six
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;HR /&gt;

&lt;P&gt;My guess is the Symantec Documentation is making an assumption on what python modules are installed since now it can't seem to find "six".   I am running Splunk Enterprise is 6.6.1.  is there difference in the python that is included with version 7 ?&lt;/P&gt;</description>
      <pubDate>Tue, 27 Mar 2018 21:29:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294707#M85903</guid>
      <dc:creator>smaat11</dc:creator>
      <dc:date>2018-03-27T21:29:34Z</dc:date>
    </item>
    <item>
      <title>Re: Symantec Cloud Scripted Input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294708#M85904</link>
      <description>&lt;P&gt;Finally got back to working on this...&lt;/P&gt;

&lt;P&gt;Still new to Splunk, Python and the Symantec Cloud app, but it appeared like the Symantec instructions were written more for a Linux implementation of Splunk....&lt;/P&gt;

&lt;P&gt;Anyway, I partially got this to work by:&lt;/P&gt;

&lt;P&gt;(1) Upgrading to Splunk 7.03&lt;BR /&gt;
(2) Downloading/Copying the Dateutil library into the \bin\scripts directory&lt;BR /&gt;
(3) Changing the Path variable to the SEPConfig.Ini file in the ExportClient.py script.&lt;/P&gt;

&lt;P&gt;OLD&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;r3_url = "https://usea1.r3.securitycloud.symantec.com/r3_epmp_i"
oauth_url = "/oauth2/tokens"
export_api = "/sccs/v1/events/export"
CONFIG_INI = os.path.join('/Applications/Splunk/', 'bin', 'scripts', 'SEPCloudConfig.ini')
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;NEW&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;## Full path to my Splunk installation
MySplunk_Home = 'C:\Program Files\Splunk'

r3_url = "https://usea1.r3.securitycloud.symantec.com/r3_epmp_i"
oauth_url = "/oauth2/tokens"
export_api = "/sccs/v1/events/export"
CONFIG_INI = os.path.join(MySplunk_Home, 'bin', 'scripts', 'SEPCloudConfig.ini')
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;(4) Changing the Scripted Input to reference the actual ExportClient.py script instead of the Wrapper.sh file provided by Symantec.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Apr 2018 14:09:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294708#M85904</guid>
      <dc:creator>smaat11</dc:creator>
      <dc:date>2018-04-11T14:09:40Z</dc:date>
    </item>
    <item>
      <title>Re: Symantec Cloud Scripted Input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294709#M85905</link>
      <description>&lt;P&gt;Hi smaat11,&lt;/P&gt;

&lt;P&gt;I've encountered problem while using the script for the SEPC too.&lt;BR /&gt;
What version of Python are you running?&lt;BR /&gt;
I had Splunk 7.2.4 and Python2.7 with below pip installation. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunk@SplunkServer7:/opt/splunk/bin/scripts$ pip2 list
asn1crypto (0.24.0)
certifi (2019.3.9)
cffi (1.12.3)
chardet (3.0.4)
cryptography (2.6.1)
enum34 (1.1.6)
idna (2.8)
ipaddress (1.0.22)
ndg-httpsclient (0.4.0)
pip (8.1.1)
pyasn1 (0.1.9)
pycparser (2.19)
pyOpenSSL (19.0.0)
python-dateutil (2.8.0)
requests (2.7.0)
setuptools (20.7.0)
six (1.12.0)
UNKNOWN (0.0.0)
urllib3 (1.23)
wheel (0.29.0)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Excerpt of error I'm getting within Splunkd.log&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;05-09-2019 13:27:39.642 +0800 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/wrapper.sh"     self._send_output(message_body)
05-09-2019 13:27:39.642 +0800 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/wrapper.sh"   File "/usr/lib/python2.7/httplib.py", line 897, in _send_output
05-09-2019 13:27:39.642 +0800 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/wrapper.sh"     self.send(msg)
05-09-2019 13:27:39.642 +0800 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/wrapper.sh"   File "/usr/lib/python2.7/httplib.py", line 859, in send
05-09-2019 13:27:39.642 +0800 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/wrapper.sh"     self.connect()
05-09-2019 13:27:39.642 +0800 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/wrapper.sh"   File "/opt/splunk/lib/python2.7/site-packages/requests/packages/urllib3/connection.py", line 129, in connect
05-09-2019 13:27:39.643 +0800 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/wrapper.sh"     self.sock = ssl.wrap_socket(conn, self.key_file, self.cert_file)
05-09-2019 13:27:39.643 +0800 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/wrapper.sh" AttributeError: 'NoneType' object has no attribute 'wrap_socket'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When running directly via Python, shows below error:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunk@SplunkServer7:/opt/splunk/bin/scripts$ python ExportClient.py
Traceback (most recent call last):
  File "ExportClient.py", line 208, in &amp;lt;module&amp;gt;
    main()
  File "ExportClient.py", line 194, in main
    total_events = total_events + len(data)
TypeError: object of type 'NoneType' has no len()
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Have you encountered any of these and do you have any suggestion?&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 05:30:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294709#M85905</guid>
      <dc:creator>salax</dc:creator>
      <dc:date>2019-05-09T05:30:05Z</dc:date>
    </item>
    <item>
      <title>Re: Symantec Cloud Scripted Input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294710#M85906</link>
      <description>&lt;P&gt;Any solution found?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2019 20:20:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294710#M85906</guid>
      <dc:creator>GDustin</dc:creator>
      <dc:date>2019-10-15T20:20:26Z</dc:date>
    </item>
    <item>
      <title>Re: Symantec Cloud Scripted Input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294711#M85907</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;

&lt;P&gt;My script is working fine.&lt;BR /&gt;
It is able to get auth token and able to connect with SEPC cloud.&lt;BR /&gt;
but in event export no logs are coming...but i am able to see logs in sepc console&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2020 11:42:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Symantec-Cloud-Scripted-Input/m-p/294711#M85907</guid>
      <dc:creator>nagendra1111</dc:creator>
      <dc:date>2020-03-26T11:42:44Z</dc:date>
    </item>
  </channel>
</rss>

