- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
After several update of some splunkbase apps and after a restart of my search head, I get this error :
Invalid key in stanza [lookup_watcher] in /opt/splunk/etc/apps/SplunkAdmins/default/inputs.conf, line 2: python.version (value: python3).
Invalid key in stanza [sendresults_alert] in /opt/splunk/etc/apps/sendresults/default/alert_actions.conf, line 7: python.version (value: python3).
Invalid key in stanza [slack] in /opt/splunk/etc/apps/slack_alerts/default/alert_actions.conf, line 6: python.version (value: python3).
Invalid key in stanza [script://$SPLUNK_HOME/etc/apps/splunk-dashboard-app/bin/save_image_and_icon_on_install.py] in /opt/splunk/etc/apps/splunk-dashboard-app/default/inputs.conf, line 4: python.version (value: python3).
I am in 7.3.4 and before updating, I checked the compatibility version with both 7.3 and 8.x because I am about to upgrade my platform to a 8.x version.
Is this message (python3) will block the functionality of app updated on the 7.3.4 splunk version ?
Thank you.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


"Invalid key" messages (they're really just warnings rather than errors) notify you of entries in config files that are not recognized. That is, the key specified is not in the corresponding .spec file. Usually, this is the result of a spelling error. In this case, however, the key is known only to Splunk versions 8 and higher so the messages can be ignored in earlier versions.
If this reply helps you, Karma would be appreciated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


"Invalid key" messages (they're really just warnings rather than errors) notify you of entries in config files that are not recognized. That is, the key specified is not in the corresponding .spec file. Usually, this is the result of a spelling error. In this case, however, the key is known only to Splunk versions 8 and higher so the messages can be ignored in earlier versions.
If this reply helps you, Karma would be appreciated.
