Reporting

After upgrading Splunk 6.4 to 6.6 why is Splunk not able to send mails anymore? Error: No such file or directory

inko6nito
Explorer

Hi,

we've made an update of Splunk (6.4 -> 6.6) and changed our certificates, everything works fine except one thing:

We're not able to send emails anymore. Triggered by alert or directly executed via SPL (| sendemail ...), both is not possible.

We get the following errors in python.log:

 ERROR sendemail:137 - Sending email. subject="xxx", results_link="yyy", recipients="[u'name@server.com']", server="mail.server" 
 ERROR sendemail:443 - [Errno 2] No such file or directory while sending mail to: ... 

In splunk.log it is almost the same message:

 ...[lot_of_arguments] ... ERROR   sendemail:443 - [Errno 2] No such file or directory while sending mail to: ... 

Does anyone have an idea, what file or directory Splunk cannot find when sending a mail or how I can find it out?

thx!

0 Karma

splunkybit
Engager

It is a simple typing error at line 115!
I have changed to:

sslConfJSON=ssContent.get('alert_Actions'),

because the splunk conf file name is with an underscore in it.
Thanks for your post in splunk answers 🙂

0 Karma

inko6nito
Explorer

Well, I've found something but I would not call it a solution:

When I comment out the line 115 in the Script sendemail.py my Splunk is able to send mails again.
Content of the line:

  sslConfJSON=ssContent.get('alertActions'), 

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...