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

Expo Registry fails to start #149

Closed
nutjob4life opened this issue Jan 10, 2023 · 0 comments
Closed

Expo Registry fails to start #149

nutjob4life opened this issue Jan 10, 2023 · 0 comments
Assignees
Labels
B13.0 B13.1 bug Something isn't working i&t.skip s.medium Medium level severity task

Comments

@nutjob4life
Copy link
Member

🐛 Describe the bug

On pds-expo, the Registry fails to start. The error message:

Caused by: org.opensearch.OpenSearchSecurityException:
Error while initializing transport SSL layer from PEM:
OpenSearchException[Unable to read /usr/share/opensearch/config/esnode-key.pem (/usr/share/opensearch/config/esnode-key.pem).
Please make sure this files exists and is readable regarding to permissions.
Property: plugins.security.ssl.transport.pemkey_filepath]

The cause is that on pds-expo, the file certs/node1.pem is owned by pds4 and mode 600—but in the container appears owned by root and not opensearch and as a result it can't be read.

🕵️ Expected behavior

That it starts on pds-expo.

📚 Version of Software Used

main branch

🖥 System Info

  • Red Hat Enterprise Linux release 8.7 (Ootpa)
  • Docker 20.10.22

🦄 Related requirements

⚙️ Engineering Details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B13.0 B13.1 bug Something isn't working i&t.skip s.medium Medium level severity task
Projects
None yet
Development

No branches or pull requests

2 participants