Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] update to 4.0

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] update to 4.0


Chronological Thread 
  • From: Brian Tierney <>
  • To: "Maciolek, Mark" <>
  • Cc: Andrew Lake <>, "" <>
  • Subject: [perfsonar-user] update to 4.0
  • Date: Wed, 19 Apr 2017 11:48:01 -0700
  • Ironport-phdr: 9a23:sIKp1B1CedAjaIFZsmDT+DRfVm0co7zxezQtwd8ZseMXLPad9pjvdHbS+e9qxAeQG96KtbQf06GP6PmocFdDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXdrXKo8DEdBAj0OxZrKeTpAI7SiNm82/yv95HJbQhFgDuwbal8IRmqogndq8cbjZZ/Iast1xXFpWdFdf5Lzm1yP1KTmBj85sa0/JF99ilbpuws+c1dX6jkZqo0VbNXAigoPGAz/83rqALMTRCT6XsGU2UZiQRHDg7Y5xznRJjxsy/6tu1g2CmGOMD9UL45VSi+46ptVRTlkzkMOSIn/27Li8xwlKNbrwynpxxj2I7ffYWZOONjcq/BYd8WQGxMUNtMVyxaGoO8bpcAD+sGPeZFtIn2ulUBowe4CwKxAO/iyiNEinrw0KYn0eouDBvG0RQ6H90MvnTarNv7OqQPX+6r0KbF1i/MY+9M1Drn9ITEbhIsrPeRVrxwa8rRzkwvGhvYg1WKqIzqJTWV3fkTvWia8eVgT+SvhHAnqgpspTWg3cMsipXIho0L0FDE8zt2wYYuKNKmU053e9ikH4VMtyyDMYZ9X80sQ2ZtuCkgy70Gv4a2czYRyJg9wR7QdeCHf5CV4hLlVOadOyl3i294eL6nmhq//1asxvfhWsS20ltGtDdJnsXQunwXyhDe5daLR/1g9UmiwTaCzx3f5v9HLEwum6fXMZEszqMqmpcRrEjPBjH6lFnygaOMdUgp+vKk5/r6brjnvJOQKot5hwL4P68zgMKwG/44PRILX2WD+eSzyrnj/UrhTbVEkPI7nbPVsJTBKsQfvKK5DAhV0pg75xa+CTepzsgYkGEaIF5bex+LlYbkN0vBLfzlF/uygUmgnC9ux//cP73hBpvNLmLEkLfkZbty8EpcyBYyzd9B/ZJUDK8OIfLoV0Dvr9zUFBk5PBKow+r/EtVyypseWX6TAq+eKK7SqUGH5vghI+mXY48VvizyK+I86/7zln82h0UdcLKt3ZsWc3C4Au9mL1uDbXrthNcBDXkFvhA4TOP0lF2OTyRfaGivUKIhtXkHD9fsKI7IR4epjb/FlAKyBJ4cLjRjA0qPV1LhfISDX/oPQD+UIolsniFSBoKsU4sw6Rb7vgvmyrd9KOfF0iAD85TuyItb/erWwDso9DVyR/ic3nuLQnA8ymkMWz47xqZysGRw0RGF3LQu0K8QLsBa+/4cClRyDpXb1eEvTo2qVw==


That is odd.

Can you try this, and see if that fixes it:

yum reinstall pscheduler-server


On Wednesday, April 19, 2017, Maciolek, Mark <> wrote:

Hi,

 

2017/04/19 13:07:38 (9225) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test, continuing with rest of config: 422 UNPROCESSABLE ENTITY: Unable to complete request: Limit processor is not initialized: Limit processor is not initialized.  See system logs.

2017/04/19 13:07:38 (9225) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test, continuing with rest of config: 500 INTERNAL SERVER ERROR: Error while tasking 132.177.100.142: Unable to post task to 132.177.100.142: Unable to complete request: Limit processor is not initialized: Limit processor is not initialized.  See system logs.

 

 

pscheduler-api CRITICAL Failed to load limit file /etc/pscheduler/limits.conf

 

The limits.conf file is there and it’s the same size as the file on my second perfsonar box where the tests are running.

6150 Apr 18 04:40 limits.conf

 

https://perf-rcc.unh.edu/toolkit/

 

Funny thing my other perfsonar box updated yesterday and its tests are working

 

Mark

 

--Mark Maciolek

Network Administrator

Morse Hall Rm 338

http://www.unh.edu/research/support-units/research-computing-center

 

 

Hi,

 

What is in /var/log/pscheduler/pscheduler.log and /var/log/perfsonar/meshconfig-agent.log? Also,does the host have a public address so I can look at the web frontend?

 

Thanks,

Andy

 

 

 

On April 19, 2017 at 11:57:59 AM, Mark Maciolek () wrote:

Hi,

I let the system auto update to version 4 yesterday. I rebooted the server
yesterday. Since the reboot the tests have not run.

This is from the logs:

perf-rcc bwctld[13065]: FILE=sapi.c, LINE=391, BWLControlAccept(): Unable to
read ClientGreeting message

Do I have to remake all the tests?

Mark





--
Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net





Archive powered by MHonArc 2.6.19.

Top of Page