Failed to execute action [LCunrRXlStS-vH4o05YY8w_elasticsearch_nodes/send_email_to_admin] java.lang.IllegalArgumentException: no accounts of type [email] configured. Please set up an account using the [xpack.notification.email] settings

Elastic Stack Elasticsearch
1

It says, no accounts of type [email] configured. Please set up an account using the [xpack.notification.email] settings
I tried adding the information but it closes.

[2019-04-03T11:08:54,349][INFO ][o.e.n.Node ] [-mQT_6c] started
[2019-04-03T11:08:54,859][INFO ][o.e.c.s.ClusterSettings ] [-mQT_6c] updating [xpack.monitoring.collection.enabled] from [false] to [true]
[2019-04-03T11:08:56,616][WARN ][o.e.x.s.a.s.m.NativeRoleMappingStore] [-mQT_6c] Failed to clear cache for realms []
[2019-04-03T11:08:56,663][INFO ][o.e.l.LicenseService ] [-mQT_6c] license [7c0c10ff-40ec-4dc6-8e50-88ca87acfcae] mode [trial] - valid
[2019-04-03T11:08:56,676][INFO ][o.e.g.GatewayService ] [-mQT_6c] recovered [22] indices into cluster_state
[2019-04-03T11:08:58,234][INFO ][o.e.x.w.WatcherService ] [-mQT_6c] reloading watcher, reason [new local watcher shard allocation ids], cancelled [0] queued tasks
[2019-04-03T11:09:05,853][INFO ][o.e.c.r.a.AllocationService] [-mQT_6c] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[kibana_sample_data_ecommerce][0], [.kibana_1][0]] ...]).
[2019-04-03T11:09:59,166][ERROR][o.e.x.w.a.e.ExecutableEmailAction] [-mQT_6c] failed to execute action [LCunrRXlStS-vH4o05YY8w_elasticsearch_nodes/send_email_to_admin]
java.lang.IllegalArgumentException: no accounts of type [email] configured. Please set up an account using the [xpack.notification.email] settings
at org.elasticsearch.xpack.watcher.notification.NotificationService.getAccount(NotificationService.java:62) ~[?:?]
at org.elasticsearch.xpack.watcher.notification.email.EmailService.send(EmailService.java:140) ~[?:?]
at org.elasticsearch.xpack.watcher.actions.email.ExecutableEmailAction.execute(ExecutableEmailAction.java:72) ~[?:?]
at org.elasticsearch.xpack.core.watcher.actions.ActionWrapper.execute(ActionWrapper.java:144) ~[x-pack-core-6.5.2.jar:6.5.2]
at org.elasticsearch.xpack.watcher.execution.ExecutionService.executeInner(ExecutionService.java:455) ~[x-pack-watcher-6.5.2.jar:6.5.2]
at org.elasticsearch.xpack.watcher.execution.ExecutionService.execute(ExecutionService.java:295) ~[x-pack-watcher-6.5.2.jar:6.5.2]
at org.elasticsearch.xpack.watcher.execution.ExecutionService.lambda$executeAsync$5(ExecutionService.java:395) ~[x-pack-watcher-6.5.2.jar:6.5.2]
at org.elasticsearch.xpack.watcher.execution.ExecutionService$WatchExecutionTask.run(ExecutionService.java:544) [x-pack-watcher-6.5.2.jar:6.5.2]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:624) [elasticsearch-6.5.2.jar:6.5.2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_191]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]
^C[2019-04-03T11:10:45,740][INFO ][o.e.x.m.j.p.NativeController] [-mQT_6c] Native controller process has stopped - no new native processes can be started
[2019-04-03T11:10:45,741][INFO ][o.e.n.Node ] [-mQT_6c] stopping ...
[2019-04-03T11:10:45,757][INFO ][o.e.x.w.WatcherService ] [-mQT_6c] stopping watch service, reason [shutdown initiated]
[2019-04-03T11:10:46,763][INFO ][o.e.n.Node ] [-mQT_6c] stopped
[2019-04-03T11:10:46,763][INFO ][o.e.n.Node ] [-mQT_6c] closing ...
[2019-04-03T11:10:46,776][INFO ][o.e.n.Node ] [-mQT_6c] closed

2

Hi,

Can you post your configuration of the email account? Our config looks like this:

xpack.notification.email.account:
    exchange_account:
        profile: outlook
        email_defaults:
            from: email@company.com
        smtp:
            auth: false
            starttls.enable: false
            host: mail.company.com
            port: 25

Best regards
Wolfram

3

also make sure the information is available on all nodes (and the nodes are restarted), if you update the YAML file. Alternatively you could also use the cluster update settings API.

--Alex

4

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