Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 and now broken

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 and now broken


Chronological Thread 
  • From: Mark Feit <>
  • To: Onno Zweers <>, "" <>
  • Subject: Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 and now broken
  • Date: Tue, 18 Apr 2023 15:23:12 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=l6zDW0GUN1+RI2EpOP6NWcesr4KR78ec5NMKN6qxc1I=; b=c4dMlGqH32tPOB38TWSz5h9qQdgiR/v+fmtHNOPw2sVI2c/AoORNWdKFlDwqr5V7oceZOQf5F44lEpMxXrJ84VJDhYb1yAaPjOmcTmunB9dz37dt1gN+vqf8JsEKc4XT4niPjDQfLbY0NvY50NXpBIrJIk+sIvw8NHYM8nqf7AWvE5kdBbSiP33U6SYh89H2ZZIQY4FOdJMKdmbnsmY1iPCvIjrU5FIK1tTS+7DMAcxTgTzuxzV8AswnlMLn6kul0hc8RBCHPonr44dRu8oKW0PmDYwweHzBERhwTXokbdjnmfVAGz8myLzZa0mrG+46lHTfjWVuRdwrPZ3H53z3UQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UIiD+1nTZiXY/a41nATIatxIFw59KQPvA6RzUYU4j63wPq8PAGIthzs4Uj5cCq3tvKphBVnGaDgTh97EaEZhEYXF407JZX7yHPv6Emye2wXNFmTQx1z/ePHXqVj8tek1KTD1+fR1FaJ205YrsxDC2W4ymv9eCz192KuF+QzqV2duwint50/vpcAFf5SAUSu15aMiy8T0DdbEoQtkfipNasNvqeSAXB//bNm+m7zTolVEydClqBa3AB4j6KTRhTEjpeMSydVPsNWrs0S7NhMwHPBkNLZ5cntQA9BmBkwyAzjyJ8zsgwalBfL+WnwHYArBAJzshD92w0ryBg4U4CWJ/A==

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

 

 




Archive powered by MHonArc 2.6.24.

Top of Page