Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elasticsearch does not start as a daemon #16579

Closed
jasontedor opened this issue Feb 10, 2016 · 0 comments
Closed

Elasticsearch does not start as a daemon #16579

jasontedor opened this issue Feb 10, 2016 · 0 comments
Assignees
Labels
>bug :Core/Infra/Core Core issues without another label v5.0.0-alpha1

Comments

@jasontedor
Copy link
Member

Due to the settings refactoring and the magical action-at-a-distance way that some settings like es.foreground are set via system properties, Elasticsearch does not currently start as a daemon (and thus as a service) when built from master:

$ ~/elasticsearch/elasticsearch-3.0.0-SNAPSHOT/bin/elasticsearch -d
$ Exception in thread "main" java.lang.IllegalArgumentException: unknown setting [foreground]
        at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:227)
        at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:216)
        at org.elasticsearch.common.settings.SettingsModule.configure(SettingsModule.java:60)
        at <<<guice>>>
        at org.elasticsearch.node.Node.<init>(Node.java:224)
        at org.elasticsearch.node.Node.<init>(Node.java:156)
        at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:188)
        at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:294)
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:37)
Refer to the log for complete error details.

Closes #11564

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Core/Infra/Core Core issues without another label v5.0.0-alpha1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants