Elasticsearch won't start after adding email settings in elasticsearch.yml

Hi, I'm trying to configure automated reporting and the first part of it appears to be configuring/adding email settings in elasticsearch.yml.

My elsticsearch.yml is relatively vanilla, i.e. only the path.data, path.log and the network.host have been uncommented and edited.

The settings I added, for the email configuration, are:

    profile: standard
      auth: true
      starttls.enable: true
      host: smtp.ionos.com
      port: 587
      user: reporting@<my_domain>.net 
      password: <my_password>

After I do systemctl restart elasticsearch.service, I don't see anything incremental in the /var/log/elasticsearch/elasticsearch.log.

In particular:

[2019-01-04T13:46:06,472][INFO ][o.e.n.Node               ] [FSwndfv] stopping ...
[2019-01-04T13:46:06,484][INFO ][o.e.x.w.WatcherService   ] [FSwndfv] stopping watch service, reason [shutdown initiated]
[2019-01-04T13:46:06,538][INFO ][o.e.x.m.j.p.l.CppLogMessageHandler] [FSwndfv] [controller/1491] [Main.cc@148] Ml controller exiting
[2019-01-04T13:46:06,539][INFO ][o.e.x.m.j.p.NativeController] [FSwndfv] Native controller process has stopped - no new native processes can be started
[2019-01-04T13:46:06,808][INFO ][o.e.n.Node               ] [FSwndfv] stopped
[2019-01-04T13:46:06,808][INFO ][o.e.n.Node               ] [FSwndfv] closing ...
[2019-01-04T13:46:06,817][INFO ][o.e.n.Node               ] [FSwndfv] closed

I wonder if there's another log where I could find out what is happening and why it is not starting.

Any help would be appreciated.

The mistake was that I did not have proper indentation in the elasticsearch.yml.

Given that the previous lines in my file (not shown above) had a space before starting, xpack.notification.email.account: also needed a space before.

This is what was causing elasticsearch not to start.

As for the rest of the lines, I believe I already had 4 spaces for every sub-section.

1 Like

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