Skip to Content.
Sympa Menu

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

Subject: perfSONAR User Q&A and Other Discussion

List archive

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


Chronological Thread 
  • From: Mark Feit <>
  • To: Zhi-Wei Lu <>, "" <>
  • Subject: Re: [perfsonar-user] RE: limits.conf file
  • Date: Tue, 8 Jan 2019 14:02:13 +0000
  • Accept-language: en-US
  • Authentication-results: ucdavis.edu; dkim=none (message not signed) header.d=none;ucdavis.edu; dmarc=none action=none header.from=internet2.edu;
  • Ironport-phdr: 9a23:QOpeeRTAEryFwR7z/1IHPVtGOtpsv+yvbD5Q0YIujvd0So/mwa6zbBCN2/xhgRfzUJnB7Loc0qyK6/CmATRIyK3CmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+KPjrFY7OlcS30P2594HObwlSizexfbB/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbDVwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4qF2QxHqlSgHLSY0/mHJhMJtkKJVrhGvpxJ9zI7VfI6aO+FzcbnBcdMfX2dNQtpdWi5HD4ihb4UPFe0BPeNAoof6vVQOtxi+DhSsCuzxyz9ImmL90Ko/0+QvDw7G3RAgEskPsHTSsNX6Kr0SUearw6nU0znPde1Z1irg6IXRdB0qvP+CXbV1ccXLyEkvERvIjkiMpoP4JTyVyOUNs3OB4+V+SO2vlmgqoBxyrDi33soglJPGip4Ixl3B6Cl13Zs5KNi2SEN0fdKoDJ5duiOEOIZ5XM8vRmRltDgmxrEYoZK3YSoHxZo9yxPdb/GLaZWE7gz+WOqLPDt1inNodKqxhxms8kWs1ujxW8y73VpWqydKjtfBum4Q2xHW9MSHRPlw8V2k1DmSzA/e5fxLLEYpnqTBMZEh2KQ/lp8LvETDACD2nEL2gbeOeEg4/eak9/nrbqz7q5CeKYN4kwb+Pb8wlcClBuQ4LxQOUHOc+eSh0r3s4Ff1QK1Qjv0xjqnWrozVJdgapq6+BQ9ZyIEj6wujDzei19QYmnoHIEhZdxKAiojlI1DOIPbmAvejm1mgji1ky+zbMrDkH5nBM2XPnbLvfbty90JQ1A8+wNJB6J9bFL0MJff+VlHtuNDGFhM5Nha7w+fjCNVzzIMeXmePD7ecMKPcr1CI5/4vLvKNZI8TpDbyNeIl5/jwgn8lh1MRZ7em0oYKaHygBPRpP12ZYWbwgtcGCWoKphQxTPbkiF2ZVj5TYWy9X7gl6jEmE4KpE53DS5upgLyAxye7AoZWan5cBlCNF3foa5uLW+0KaC2MPs9tjCYIWqa8RI88hlmSs1rIy7siEefVsgkF/cbxy9xoz/DYmRgs9CcyAsiAhSXFBXl5hG0TQDk/xuViukFn4laFzaVihfFET5pe6+4DGlMiOITS1Ot8Asq3RxnMZP+ITkqrWNOrHWt3Q94slYwgeUF4TvCrlBOL8SerH/dBkrKGBYAc86TA0mL3KtonjXvKyf9y3BEdXsJTODj+1eZE/A/JCtuRyR/Lnru2dakawC/G/XuCymzLpkxDTQpsSvyfByICbUffs9XioE7OUuzmBbcmN15HzsiPYutPZ8byhFpLDPHkJJzFYm23lmvxYHTAxr6FYIfwPWlI2iLbBRsZmAwa43edcwUyG3Tpr2fXFjc7E1Xpbgvl+vV/r3XuSEgywkmKYkRt2qDz9AQSgKmdTe8exLQJpH1npjlpT1s=
  • Spamdiagnosticoutput: 1:0

Zhi-Wei Lu writes:

 

On my host pb.noc.ucdavis.edu, I can run rtt to p0.noc.ucdavis.edu, but not throughput.

 

Throughput is one of a few tests that require two pSchedulers (we call them “participants”) to work together to find a time when the test can be run.  The communication between them happens via pScheduler’s REST API, which uses HTTPS, so if that’s blocked, nothing is going to work.  The troubleshooter’s “checking for pScheduler” is the equivalent of “pscheduler ping HOSTNAME,” which attempts to fetch the API’s root resource.  ( You can try that yourself with “curl -Lk https://HOSTNAME/pscheduler”.)

 

All of the other tests (RTT, trace, idle, etc.) are single-participant, which means the machine where it runs is the only one involved and pScheduler doesn’t have to do anything off-host.

 

--Mark

 




Archive powered by MHonArc 2.6.19.

Top of Page