Unknown setting [xpack.notification.email]

alerting

#1

I'm trying to follow Email Action | X-Pack for the Elastic Stack [6.1] | Elastic and getting following error while trying to start elasticsearch:

elasticsearch | [2018-01-12T05:48:39,956][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [ba1897ad8ad4] uncaught exception in thread [main]
elasticsearch | org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [xpack.notification.email] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
elasticsearch | 	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:125) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:112) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:85) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | Caused by: java.lang.IllegalArgumentException: unknown setting [xpack.notification.email] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
elasticsearch | 	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:312) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:276) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:135) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.node.Node.<init>(Node.java:330) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.node.Node.<init>(Node.java:245) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:212) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:212) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:322) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:121) ~[elasticsearch-6.1.1.jar:6.1.1]
elasticsearch | 	... 6 more
elasticsearch exited with code 1
# cat xpack.env 
xpack.notification.email=MYEMAILATGMAILDOTCOM
# 

needless to say, I replace MYEMAILATGMAILDOTCOM with my own email)

per error's advise:

please check that any required plugins are installed, or check the breaking changes documentation for removed settings

I'm using docker image docker.elastic.co/elasticsearch/elasticsearch-platinum:6.1.1 and xpack is part of it (nothing to install) and I even check for breaking changes documentation and did not find anything relevant...

Please advise.


Watcher and X-Pack do not appear to run or even be installed despite using Elastic stack v6.3.2
(Ioannis Kakavas) #2

Hi alexus,

is a namespace, not a specific setting. In the link you posted, there is an explicit example for gmail, please follow that.


#3

@ikakavas - gotcha) - my goal is NOT to send through Gmail, but rather TO Gmail)

Is there a way to configure xpack.notification namespace outside of elasticsearch.yml, like via curl?
assuming no, do I have to configure above namespace across every node?


(Alexander Reelsen) #4

the notification settings are dynamic and be updated using the Cluster Update Settings API

--Alex


(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.