perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi, 

For the problem you are seeing, did any of the rebuilds happened after we released 5.0.3? That had some fixes to the scripts you mentioned for non-CentOS versions of RedHat. Updating to 5.0.3 from an earlier 5.0.X version will not fix it, the first install needs to be 5.0.3 the way those scripts work. If you go directly to the URL https://10.110.136.120/opensearch does it connect (if its working you’ll likely see some type of auth error, which is fine, just want to make sure opensearch is running). What do you get when you go to the URL  https://10.110.136.120/esmond/perfsonar/archive? Mostly curious if that gives an error connecting to OpenSearch kinda like Johann reported and if it’s because OpenSearch is not running, or it is running but not configured properly.

@Johann: WRT the error message about not being able to archive to ps-19-cpt-teraco, is ps-19-cpt-teraco a 5.0 host? If it is, there is no esmond to archive to, the backward compatibility endpoint is read-only. I think that would be separate from the issue with connecting to Opensearch you shared. Is Opensearch running (you can check with systemctl status opensearch). Also is this CentOS 7 and not some other flavor of RedHat? 

Thanks,

Andy

On June 30, 2023 at 2:57:11 AM, Victor Mendoza () wrote:

Hi,

This might be related to a failure to detect the OS in these setup scripts:

/usr/lib/perfsonar/logstash/scripts/install_logstash_sysconfig.sh
/usr/lib/perfsonar/archive/perfsonar-scripts/pselastic_secure_pre.sh

They didn't work for us on CentOS 7 with 'redhat-lsb-core' installed.

Regards,



On 6/30/23 00:05, Vazquez, Felix wrote:
> Did you find a fix?
>
> ------------------------------------------------------------------------
> *From:* Johann Hugo <>
> *Sent:* Thursday, June 29, 2023 5:10:02 PM
> *To:* Vazquez, Felix <>
> *Cc:* <>
> *Subject:* Re: [perfsonar-user] archive unreachable
> I get a similar error on many of my servers as well. If I follow the URL
> I get elasticsearch.exceptions.ConnectionError
>
> /var/log/pscheduler/pscheduler.log gives the following errors:
> Jun 29 22:58:07 ps-19-cpt-teraco journal: archiver WARNING  17926316:
> Gave up archiving
> https://ps-19-cpt-teraco/pscheduler/tasks/d1c9b407-0013-49da-b4b1-f5c7fb7e59f3/runs/fc7166ba-7d28-4cb3-8d3a-4eaf35b6b666 <https://ps-19-cpt-teraco/pscheduler/tasks/d1c9b407-0013-49da-b4b1-f5c7fb7e59f3/runs/fc7166ba-7d28-4cb3-8d3a-4eaf35b6b666> to esmond
> Jun 29 22:59:08 ps-19-cpt-teraco journal: archiver WARNING  17926318:
> Failed to archive
> https://ps-19-cpt-teraco/pscheduler/tasks/d1c9b407-0013-49da-b4b1-f5c7fb7e59f3/runs/3eb9cbbb-a372-4772-a3d1-55cdcd798d44 <https://ps-19-cpt-teraco/pscheduler/tasks/d1c9b407-0013-49da-b4b1-f5c7fb7e59f3/runs/3eb9cbbb-a372-4772-a3d1-55cdcd798d44> to esmond: Archiver permanently abandoned registering test after 1 attempt(s): 405: Invalid JSON returned
>
>
> On Thu, Jun 29, 2023 at 6:02 PM Vazquez, Felix <
> <mailto:>> wrote:
>
> Please tell me there is a simple fix to this error. I rebuilt the
> server twice with the same error. Other servers are not getting this
> error.____
>
> __ __
>
> Error loading test listing; measurement archive unreachable:____
>
> __ __
>
> A picture containing text, screenshot, font Description
> automatically generated____
>
> --
> To unsubscribe from this list:
> https://lists.internet2.edu/sympa/signoff/perfsonar-user
> <https://lists.internet2.edu/sympa/signoff/perfsonar-user>
>
>
> --
> To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user
--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user