perfSONAR User Q&A and Other Discussion

[Onno Zweers <>]

Hi Mark,

 

Thanks! I was able to get opensearch working.

 

The first problem with it was that it was configured to allocate 66GB of RAM. 😂 The machine does not have that.

 

I fixed it by changing the Xms value in /etc/opensearch/jvm.options.

 

The next problem was this error:

 

Apr 19 16:40:17 perfsonar.grid.surfsara.nl systemd-entrypoint[146506]: java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native

 

After googling a bit I found a similar problem in elasticsearch:

https://stackoverflow.com/questions/47824643/unable-to-load-jna-native-support-library-elasticsearch-6-x/50371992#50371992

 

I used the solution there but had to replace “elasticsearch” with “opensearch”:

 

[root@perfsonar /etc/opensearch]# nano /etc/sysconfig/opensearch 

 

[root@perfsonar /etc/opensearch]# grep ^OPENSEARCH_JAVA_OPTS /etc/sysconfig/opensearch 

OPENSEARCH_JAVA_OPTS="-Djna.tmpdir=/var/lib/opensearch/tmp"

 

[root@perfsonar /etc/opensearch]# mkdir /var/lib/opensearch/tmp

 

[root@perfsonar /etc/opensearch]# chown -R opensearch:opensearch /var/lib/opensearch/tmp

 

[root@perfsonar /etc/opensearch]# systemctl restart opensearch

 

[root@perfsonar /etc/opensearch]# systemctl status opensearch

● opensearch.service - OpenSearch

   Loaded: loaded (/usr/lib/systemd/system/opensearch.service; enabled; vendor preset: disabled)

   Active: active (running) since Wed 2023-04-19 17:16:54 CEST; 7s ago

 

 

 

As for the checker script: thanks for pointing me to the /etc/pscheduler/limits.conf file. However, it’s not very clear to me how this file works.

 

I suppose I need to remove this block:

 

      {

            "#": "This prevents denial of service by scheduling long tasks.",

            "name": "idleex-default",

            "description": "Default limits for idleex",

            "type": "test",

            "data": {

                "test": "idleex",

                "limit": {

                    "duration": {

                        "range": {

                            "lower": "PT1S",

                            "upper": "PT2S"

                        }

                     }

                }

            }

      },

 

But do I also need to remove all references to idleex-default? And to idleex?

 

The script says:

 

> The idleex test is now disallowed for untrusted hosts by the 'allowed-tests' limit.

 

But there is no 'allowed-tests' mentioned in the limits.conf. Should there be?

 

The script also mentions a throughput-default-time test. But the code for that test differs between the limist.conf and the script output. Should I replace the limits.conf version with the script’s version?

 

Cheers,

Onno

 

Van: Mark Feit <>
Datum: dinsdag, 18 april 2023 om 17:23
Aan: Onno Zweers <>, <>
Onderwerp: Re: Perfsonar (automatically) upgraded to 5.0 and now broken

Onno Zweers writes:

 

Today our monitoring warned me that /tmp on our perfsonar node was full. After investigation, I discovered the upgraded packages. I had missed the announcement, apologies for that (too busy to read emails haha).

 

It looks like there are  two unrelated problems:

 

So now we have a system that says “Error loading test listing; measurement archive unreachable:

https://perfsonar-bandwidth.grid.surfsara.nl/esmond/perfsonar/archive/”

                …

I also noptice that opensearch was installed together with perfsonar 5.0. But it failes to start.

 

The error message is a side effect of  OpenSearch having failed to start.  That may have been caused by the full /tmp directory, so I’d recommend making sure /tmp has been cleaned out and trying a “systemctl restart opensearch” to get it going again.  If that fails, please run “journalctl -xe” and send any OpenSearch-related entries here or privately if you’d prefer that.

 

Limit processor is not initialized: Limit 'idleex-default' has unsupported type 'test'

 …

It says “replace” but I can’t seem to find which file or config I need to replace.

 

The limit configuration lives in /etc/pscheduler/limits.conf.  I’ve updated the helper script so it mentions what file it’s checking.

 

--Mark