Are you a member of the Splunk Community?
- Find Answers
- :
- Using Splunk
- :
- Other Using Splunk
- :
- Reporting
- :
- Re: Splunk Email createSSLContextSettings error
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk Email createSSLContextSettings error
I am trying to test Splunk Email with configuration integrated with AWS SES however keeps getting createSSLContextFromSettings error. Can anyone has a workaround or suggestions?
Query: | savedsearch "Logs" | stats count | sendemail to=test@user.com
ERROR: command="sendemail", createSSLContextFromSettings() got an unexpected keyword argument 'confJSON' while sending mail to: test@user.com
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The owner of the search needs to have list_storage_passwords capability.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I received this error post upgrading from 6.5.2 to 6.3.3.
For me, it occurred on a Search Head Cluster - which included deployment of the original search app (e.g. /opt/splunk/etc/shcluster/apps/search) from the deployer - obviously the the upgrade didn't upgrade this instance of the search app, and a later deployment then overwrote the 6.3.3 search app on the cluster with a 6.5.2 one which then started spitting out the createSSLContextFromSettings error.
Initial Resolution: updated /opt/splunk/etc/shcluster/apps/search from (a post 6.3.3 upgrade of) /opt/splunk/etc/apps/search and redeployed.
Long term resolution: migrate all deployed 'local' Knowledge Objects to a new app and strongly discourage users from creating new objects in the search app on the SHC.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you find a solution for this problem? I got exactly the same error, after upgrading to Splunk 7.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any update?
Community Content Calendar, September edition
Splunkbase Unveils New App Listing Management Public Preview
Leveraging Automated Threat Analysis Across the Splunk Ecosystem
