Closed mbdebian closed 4 days ago
Apart from updating the data backend, the error with the container seems to be related to the logs folder for ES:
ot-es | {"type": "server", "timestamp": "2024-06-24T12:53:29,575Z", "level": "ERROR", "component": "o.e.b.ElasticsearchUncaughtExceptionHandler", "cluster.name": "ot-es-cluster", "node.name": "070a9bbc2f90", "message": "uncaught exception in thread [main]",
ot-es | "stacktrace": ["org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Unable to access 'path.logs' (/usr/share/opensearch/logs)",
ot-es | "at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:174) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) ~[elasticsearch-cli-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "Caused by: java.lang.IllegalStateException: Unable to access 'path.logs' (/usr/share/opensearch/logs)",
ot-es | "at org.elasticsearch.bootstrap.FilePermissionUtils.addDirectoryPath(FilePermissionUtils.java:72) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Security.addFilePermissions(Security.java:299) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Security.createPermissions(Security.java:253) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Security.configure(Security.java:121) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:222) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:393) ~[elasticsearch-7.10.2.jar:7.10.2]",
ot-es | "at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) ~[elasticsearch-7.10.2.jar:7.10.2]",
Profiles updated for releases:
Describe the bug Our Standalone deployment tool for platform is using Elasticsearch in the data backend but we replaced that service with Opensearch several releases ago.
Observed behaviour When deploying platform, it reports an error for Elasticsearch backend, which doesn't get deployed.
Expected behaviour The whole Open Targets Platform should launch, and use Opensearch instead of Elasticsearch in the data backend
To Reproduce Steps to reproduce the behaviour:
make set_profile profile='2406-gcs'
make platform_up