Opensearch service fails to come up on perfsonar-toolkit installation

Open
#454 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
backend, search

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from perfsonar/toolkit

All issues in perfsonar/toolkit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.