Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@stephenfrank
Copy link
Contributor

The docker set up worked perfectly in MacOS + Docker but under another Linux + Docker environment I got this exception from Elasticsearch when starting the container.

uncaught exception in thread [main]
java.lang.IllegalArgumentException: unknown setting [bootstrap.system_call_filter ] did you mean [bootstrap.system_call_filter]?
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:544)
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:489)
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:460)
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:431)
	at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:149)
	at org.elasticsearch.node.Node.<init>(Node.java:406)
	at org.elasticsearch.node.Node.<init>(Node.java:289)
	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:227)
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:227)
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:393)
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170)
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161)
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86)
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127)
	at org.elasticsearch.cli.Command.main(Command.java:90)
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126)
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92)
For complete error details, refer to the log at /usr/share/elasticsearch/logs/docker-cluster.log

While I haven't dug deep into the environments / versions where this error is present, the change is innocuous enough and fixes one issue I had.

@sarah-mason sarah-mason added the Community Pull requests that have been contributed from community members outside Artefactual label Oct 6, 2025
@sarah-mason
Copy link
Contributor

Hi @stephenfrank - thank you for much for your two pull requests! All checks have passed, so there's nothing more we need at the moment. We have an AtoM maintainer on holiday at the moment and we're finishing up a few things from the 2.10 release cycle, but the maintainers will get to reviewing the PRs in a week or two. Please let me know if you have any questions. Again, thank you for your contribution!

@anvit anvit added this to the 2.10.1 milestone Nov 5, 2025
Copy link
Contributor

@anvit anvit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's weird, neither me nor @melaniekung have ever encountered this on linux before. But it's innocuous enough. Thanks @stephenfrank

@anvit anvit merged commit 7db926d into artefactual:qa/2.x Nov 6, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Community Pull requests that have been contributed from community members outside Artefactual

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants