Opensearch service fails to come up on perfsonar-toolkit installation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with /var/log/opensearch/opensearch.log and the failing /esmond/perfsonar/archive/ URL, then compare those errors with the pscheduler-archive authorization messages. The issue is resolved when OpenSearch initializes correctly and the archive endpoint no longer returns HTTP 500 or Unauthorized.
Written by the indexing model from the issue text.
Description
After installing perfsonar-toolkit on Rocky Linux 8.8, the following error is presented in the main screen (in a red box):
Error loading test listing; measurement archive unreachable:
https://myserver.example.com/esmond/perfsonar/archive/
If I try to access the URL above an error 500 is presented.
I'm repeatedly seeing the following errors on /var/log/opensearch/opensearch.log:
[2023-12-26T04:16:06,172][ERROR][o.o.s.a.BackendRegistry ] [myserver.example.com] Not yet initialized (you may need to run securityadmin)
[2023-12-26T04:16:07,112][ERROR][o.o.s.c.ConfigurationLoaderSecurity7] [myserver.example.com] Failure no such index [.opendistro_security] retrieving configuration for [INTERNALUSERS, ACTIONGROUPS, CONFIG, ROLES, ROLESMAPPING, TENANTS, NODESDN, WHITELIST, ALLOWLIST, AUDIT] (index=.opendistro_security)
[2023-12-26T04:16:07,113][ERROR][o.o.s.c.ConfigurationLoaderSecurity7] [myserver.example.com] Failure no such index [.opendistro_security] retrieving configuration for [INTERNALUSERS, ACTIONGROUPS, CONFIG, ROLES, ROLESMAPPING, TENANTS, NODESDN, WHITELIST, ALLOWLIST, AUDIT] (index=.opendistro_security)
[2023-12-26T04:16:07,113][ERROR][o.o.s.c.ConfigurationLoaderSecurity7] [myserver.example.com] Failure no such index [.opendistro_security] retrieving configuration for [INTERNALUSERS, ACTIONGROUPS, CONFIG, ROLES, ROLESMAPPING, TENANTS, NODESDN, WHITELIST, ALLOWLIST, AUDIT] (index=.opendistro_security)
And the following message in pscheduler-archive logs:
archiver[17673]: archiver WARNING < /head>< body>
archiver[17673]: archiver WARNING < h1>Unauthorized< /h1>
archiver[17673]: archiver WARNING < p >This server could not verify that you
archiver[17673]: archiver WARNING are authorized to access the document
archiver[17673]: archiver WARNING requested. Either you supplied the wrong
archiver[17673]: archiver WARNING credentials (e.g., bad password), or your
archiver[17673]: archiver WARNING browser doesn't understand how to supply
archiver[17673]: archiver WARNING the credentials required.</p>
archiver[17673]: archiver WARNING </body></html>
What would be the reason for those errors? Is the archiver not able to use Opensearch? Is there any file where I should configure the auth tokens for the archiver to use Opensearch?
Thanks in advance.
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from perfsonar/toolkit
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in perfsonar/toolkit
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100