Skip to Content.
Sympa Menu

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

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] update to 4.0


Chronological Thread 
  • From: Brian Tierney <>
  • To: "Maciolek, Mark" <>
  • Cc: Andrew Lake <>, "" <>
  • Subject: Re: [perfsonar-user] update to 4.0
  • Date: Wed, 19 Apr 2017 11:22:06 -0700
  • Ironport-phdr: 9a23:SYd08hSUTgK294bU9eZtNZ9Eudpsv+yvbD5Q0YIujvd0So/mwa6yYxON2/xhgRfzUJnB7Loc0qyN4v6mAjRLuMzY+Fk5M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aFRrwLxd6KfroEYDOkcu3y/qy+5rOaAlUmTaxe71/IRG3oAnLuMQanYRuJrsvxhfUv3BFZ/lYyWR0KFyJgh3y/N2w/Jlt8yRRv/Iu6ctNWrjkcqo7ULJVEi0oP3g668P3uxbDSxCP5mYHXWUNjhVIGQnF4wrkUZr3ryD3q/By2CiePc3xULA0RTGv5LplRRP0lCsKMSMy/XrJgcJskq1UvBOhpwR+w4HKZoGVKOF+db7Zcd8DWGZNQtpdWylHD4ihbYUAEvABMP5Cr4b/qVsArRWwCwqxCu3x1jBFnWX50bEg3uk7DQ3KwA4tEtQTu3rUttX1M6ISXPiowanSzDXMdfVW0irj5ojJbB8hu/eMUqxwcMHMzkQgDAfFjkmRqYP7JTOV0PoCsmiA4uV+TuKjkWgnpB9tojW2wMonl4fHhoUQyl/e9CV5xp44KsOjSEJhZ96rDodQuzmHN4twQsMuWX9ntzsnyrEepJK2cjYGxI46yxPdafGLaZWE7g7/WOqLPDt1i2xpdbSijBix6Uit0vDwWte33VpQoCdJiNbBum0X2xHR98SLUuVx8lul1DqV1A3e6vtILV4qmabHMZIt3KI8moYVvE/eBCH5gl/2g7WTdkg8+uin9eDnYrL+q5+SKYB5hRvyMqA1lcy7G+g4PQ8OX3aD9eS90r3s41H5Ta1XgvEokaTVqp7XKd4Uq6KkGQNY0Jsv5w66Dzi80dQYmXcHLEhCeBKCl4XmIFXOIOz5DfihmVSslilkxvDdM7L/GZXBNH7Dn6n9fbpl8U5T1BIzzcxD55JTErwBOOz8WlX/tNzDCR85NRa7w/z+BNVgzYMRR3iPD7SdMKPTql+I+vkvL/eWaI8Uvjb9N+Yq5+TojXAnhV8RY7Ol0oUKZ3ClTbxaJBDTRHPng9AFHGRO9i83Vu+gwAmnWCRQIVO7VKM74jw4IJ+gDcHOSp3704aMxCOqIpoDbGRaC12WF3r5X4ifHfEBdHG8OMhkxxYeVLGnA7Mg2AuouR6yn7BjMuvZ4CsVpLruz55z6vGFxkJ6ziB9E8nIizLFdGpzhG5dAmZuhK0=


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