perfsonar-user - [perfsonar-user] RE: limits.conf file

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] RE: limits.conf file

From: Zhi-Wei Lu <>
To: Zhi-Wei Lu <>, "" <>
Subject: [perfsonar-user] RE: limits.conf file
Date: Mon, 7 Jan 2019 19:47:01 +0000
Accept-language: en-US
Authentication-results: spf=none (sender IP is ) ;
Ironport-phdr: 9a23:CQOvRB9uKmRhg/9uRHKM819IXTAuvvDOBiVQ1KB21OwcTK2v8tzYMVDF4r011RmVBdWds6oMotGVmpioYXYH75eFvSJKW713fDhBt/8rmRc9CtWOE0zxIa2iRSU7GMNfSA0tpCnjYgBaF8nkelLdvGC54yIMFRXjLwp1Ifn+FpLPg8it2O2+557ebx9UiDahfLh/MAi4oQLNu8cMnIBsMLwxyhzHontJf+RZ22ZlLk+Nkhj/+8m94odt/zxftPw9+cFAV776f7kjQrxDEDsmKWE169b1uhTFUACC+2ETUmQSkhpPHgjF8BT3VYr/vyfmquZw3jSRMMvrRr42RDui9b9mRh/2hikaKz43/mLZisJyg6JavB2uqAdyzJTIbI2JLvdyYr/Rcc0cSGFcXshRTStBAoakYoQMD+oBPP9UoInjqFsPsBCwAxSsD/7oxz5JiH722bA63v88EQ7awQMvBcwOsHXPrNnvKqgdTP21wbDOwD7eYf1W3jL955LJchAnufyMQK5/ftfLxkkxFgPFlU+cppL4MDOI0OkGrmuV7/J4WO6xkWErtxx9rz2yyssxl4XEg4wVx1/Y+SllxYs1K8O3RUF7bNOhFZZdtj+WOoVuTs8/QmxlvDw2xqMItJO5ZiQG1okryhDFZ/CZb4SE+hzjW/iSLDtkgX9ofa6wihWv/Uiuz+DxVse03VhFoydAj9XDrW0C2ADW58ecRPZw8Fmt1DCS3A7J8O5EO1o7la/DJp4h3LEwkp0TvFzbECLqn0v6kLGaelw69+eq9ujre7LmqYSCOINujQH+L7gulde4AeQlNAgBQnKX+fym1L3k4U32XqlFjuE3kqnetpDWP8MbprOlAw9R1YYj7BW/Ay2639QfmHkLNFNFeBSZgIj1I1zCPur3Aeuij1mpjTtn2u3KM7jvApjCMnTPjLLsfbhj5ENTyAc+yNVS6pNKBrwPOP7zX1X+tN3cDh83KQy0xOPnBc1814IQXWKPH7SUML7OvlCV/O0vPeiMZJQPtDnjNvcl+ubijWUlll8FYampwZwXZWigHvt4OUWZb2HsgtAHEWgQpAoyVfHqiEacXj5JfHuyW6M85ionCIK9E4vPXIGtgLqd3CilBJ1WYH5JCkySHXvyaYqLRuoMO2quJZpTkj1BarWgA6s8nUW8qwvn46dsIuPK+zZeuJ7+gpw9rfXejx8p8jp9FYGAyGyXZ2Bygm4SQTIqhuZyrVE3ggOb3LJ2mPteHMYW+uhESC87M4LR1ep3F4q0Vw7cKISnUlGjF+emAHQOQ9N558JGN1RiH8iKkxvP1jSrGPkYm6HdV898yb7Vw3Wkf5U18H3BzqR01wN8EMJSKW2rgLJ+/AHPBonP1l+UjLuuab9BjXzW7GnWy22IsQkYSwN2XajfFVEnLkrN5ZWchAvZSqO2T7EuMw9P08mHf7lVbsDBkF5KTeniI5LTb3/i02o=
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99

After I put

"127.0.0.1/32",

"::1/128"

In the limits.conf file in the “allow” hosts,

pscheduler troubleshoot

worked just fine for the “localhost” trouble shooting. However, pscheduler still fail between a few servers.

On pb.noc.ucdavis.edu, I had problem to talk to pscheduler on p0.noc.ucdavis.edu

pscheduler troubleshoot p0.noc.ucdavis.edu

Performing basic troubleshooting of localhost and p0.noc.ucdavis.edu.

localhost:

Checking path MTU... Unsafe or unknown: Found only one MTU in trace to localhost

Checking for pScheduler... OK.

Checking clock... OK.

Idle test.... 9 seconds.... Checking archiving... OK.

p0.noc.ucdavis.edu:

Checking path MTU... Unsafe or unknown: Error: Process took too long to run.

Checking for pScheduler... Failed.

Request timed out

I wonder what it prevents pscheduler to talk to p0.noc.ucdavis.edu from pb.noc.ucdavis.edu.

Thank you.

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

From: <> On Behalf Of Zhi-Wei Lu
Sent: Monday, January 07, 2019 9:52 AM
To:
Subject: [perfsonar-user] limits.conf file

Hi all,

After I have upgraded our servers to CentOS7 and perfsonar 4.1.x, I managed to get the test going. However, tests started to fail again. It appears that pscheduler is failing on one of my servers:

pscheduler troubleshoot

Performing basic troubleshooting of localhost.

localhost:

Checking path MTU... Unsafe or unknown: Found only one MTU in trace to localhost

Checking for pScheduler... OK.

Checking clock... OK.

Idle test... Failed.

Unable to post task: Task forbidden by limits:

Hints:

requester: ::1

server: ::1

Made no identifications.

I did modified the limits.conf, but I after I move the perfsonar default limits.conf file back and restarted pscheduler-X daemons, I am still getting the same errors. I would love to hear what I should do next.