perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Louis-Berthier Soullière writes:

 

I'm trying to run this command with no success :

 

# pscheduler ping 10.x.x.1

10.x.x.1 : Encountered end of file

…

- Running pS-Toolkit-4.2.0b1-CentOS7-FullInstall-x86_64-2019Jul09.iso on both side

 

One key difference between the beta and production versions is the introduction of different library to do the HTTP(S) operations.  It’s cURL, which has an established track record, and we’ve had it in the test bed for months.  The error you’re seeing comes from cURL.

 

“pscheduler ping 10.x.x.1” does the equivalent of “curl -sk https://10.x.x.1/pscheduler/”.  If you can do that on the command line and get the same result, the problem isn’t likely a problem with pScheduler.

 

- High latency between the two server : 530ms

- Tried to simulate latency between two local server and cannot replicate the issue (not a latency problem)

- The test work one way but not the other. (Server A to B = OK, B to A = issue)

 

Is this the same pair of systems you were working with in ticket #884?  Your last comment indicates that there’s a MTU mismatch between the two systems, which would cause problems in the larger-to-smaller direction.  If you’re on satellite, some providers have been known to do things that make path MTU discovery not work.

 

Is it possible to disable all limits for testing purpose?

 

This isn’t a limits-related problem, but you can disable the limit system by deleting or renaming /etc/pscheduler/limits.conf.  The change will take effect within 30 seconds.

 

--Mark