<?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: Sendemail action not working in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354581#M6221</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Can you try increasing value for below parameter in &lt;CODE&gt;alert_actions.conf&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ttl     = &amp;lt;integer&amp;gt;[p]
* Optional argument specifying the minimum time to live (in seconds)
  of the search artifacts, if this action is triggered.
* If p follows integer, then integer is the number of scheduled periods.
* If no actions are triggered, the artifacts will have their ttl determined
  by the "dispatch.ttl" attribute in savedsearches.conf.
* Defaults to 10p
* Defaults to 86400 (24 hours)   for: email, rss
* Defaults to   600 (10 minutes) for: script
* Defaults to   120 (2 minutes)  for: summary_index, populate_lookup

maxtime = &amp;lt;integer&amp;gt;[m|s|h|d]
* The maximum amount of time that the execution of an action is allowed to
  take before the action is aborted.
* Use the d, h, m and s suffixes to define the period of time:
  d = day, h = hour, m = minute and s = second.
  For example: 5d means 5 days.
* Defaults to 5m for everything except rss.
* Defaults to 1m for rss.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 15 Mar 2018 12:36:07 GMT</pubDate>
    <dc:creator>p_gurav</dc:creator>
    <dc:date>2018-03-15T12:36:07Z</dc:date>
    <item>
      <title>Sendemail action not working</title>
      <link>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354578#M6218</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I have scheduled a search to run every 15 mins and added the following actions when the search returns results:&lt;BR /&gt;
- Add to triggered alerts;&lt;BR /&gt;
- Send email.&lt;/P&gt;

&lt;P&gt;When the scheduled search returns results, it gets added to the Triggered Alerts but the sendemail action does not work.&lt;BR /&gt;
When looking at the python.log it shows the following:&lt;BR /&gt;
2018-03-15 11:51:06,163 +0100 INFO  sendemail:134 - Sending email. subject="Splunk Alert: Multiple Failed logon attempts alert", results_link=splunk_scheduled_search", recipients="[u'&lt;A href="mailto:user@mail.com" target="_blank"&gt;user@mail.com&lt;/A&gt;']", server="smtp.mail.com"&lt;/P&gt;

&lt;P&gt;It appears that when I include the sendemail command in the query, it works fine, but not through the scheduled alerts.&lt;/P&gt;

&lt;P&gt;Any ideas why?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 18:30:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354578#M6218</guid>
      <dc:creator>elllie</dc:creator>
      <dc:date>2020-09-29T18:30:03Z</dc:date>
    </item>
    <item>
      <title>Re: Sendemail action not working</title>
      <link>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354579#M6219</link>
      <description>&lt;P&gt;Any other error in _internal logs? &lt;/P&gt;</description>
      <pubDate>Thu, 15 Mar 2018 12:06:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354579#M6219</guid>
      <dc:creator>p_gurav</dc:creator>
      <dc:date>2018-03-15T12:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: Sendemail action not working</title>
      <link>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354580#M6220</link>
      <description>&lt;P&gt;From scheduler.log:&lt;BR /&gt;
03-15-2018 10:53:02.185 +0000 INFO  SavedSplunker - savedsearch_id="nobody;search;Multiple Failed logon attempts alert", search_type="scheduled", user="admin", app="search", savedsearch_name="Multiple Failed logon attempts alert", priority=default, status=success, digest_mode=1, scheduled_time=1521110880, window_time=0, dispatch_time=1521110880, run_time=0.203, result_count=2, alert_actions="email", sid="scheduler_&lt;EM&gt;admin&lt;/EM&gt;&lt;EM&gt;search&lt;/EM&gt;_RMD5cf1e87219f408a1a_at_1521110880_14", suppressed=0, thread_id="AlertNotifierWorker-1"&lt;/P&gt;

&lt;P&gt;splunkd.log:&lt;BR /&gt;
03-15-2018 10:53:01.642 +0000 WARN  ScriptRunner - Killing script, probably timed out, grace=5sec, script="C:\Program Files\Splunk\bin\PYTHON.EXE C:\Program Files\Splunk\etc\apps\search\bin\sendemail.py "results_link=&lt;A href="http://SOUTH-SEC-01:8000/app/search/@go?sid=scheduler__admin__search__RMD5cf1e87219f408a1a_at_1521110880_14" target="_blank"&gt;http://SOUTH-SEC-01:8000/app/search/@go?sid=scheduler__admin__search__RMD5cf1e87219f408a1a_at_1521110880_14&lt;/A&gt;" "ssname=Multiple Failed logon attempts alert" "graceful=True" "trigger_time=1521110881" results_file="C:\Program Files\Splunk\var\run\splunk\dispatch\scheduler_&lt;EM&gt;admin&lt;/EM&gt;&lt;EM&gt;search&lt;/EM&gt;_RMD5cf1e87219f408a1a_at_1521110880_14\results.csv.gz""&lt;/P&gt;

&lt;P&gt;03-15-2018 10:53:02.185 +0000 ERROR script - sid:scheduler_&lt;EM&gt;admin&lt;/EM&gt;&lt;EM&gt;search&lt;/EM&gt;_RMD5cf1e87219f408a1a_at_1521110880_14 Script execution failed for external search command 'sendemail'&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 18:30:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354580#M6220</guid>
      <dc:creator>elllie</dc:creator>
      <dc:date>2020-09-29T18:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: Sendemail action not working</title>
      <link>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354581#M6221</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Can you try increasing value for below parameter in &lt;CODE&gt;alert_actions.conf&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ttl     = &amp;lt;integer&amp;gt;[p]
* Optional argument specifying the minimum time to live (in seconds)
  of the search artifacts, if this action is triggered.
* If p follows integer, then integer is the number of scheduled periods.
* If no actions are triggered, the artifacts will have their ttl determined
  by the "dispatch.ttl" attribute in savedsearches.conf.
* Defaults to 10p
* Defaults to 86400 (24 hours)   for: email, rss
* Defaults to   600 (10 minutes) for: script
* Defaults to   120 (2 minutes)  for: summary_index, populate_lookup

maxtime = &amp;lt;integer&amp;gt;[m|s|h|d]
* The maximum amount of time that the execution of an action is allowed to
  take before the action is aborted.
* Use the d, h, m and s suffixes to define the period of time:
  d = day, h = hour, m = minute and s = second.
  For example: 5d means 5 days.
* Defaults to 5m for everything except rss.
* Defaults to 1m for rss.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 15 Mar 2018 12:36:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Sendemail-action-not-working/m-p/354581#M6221</guid>
      <dc:creator>p_gurav</dc:creator>
      <dc:date>2018-03-15T12:36:07Z</dc:date>
    </item>
  </channel>
</rss>

