perfSONAR User Q&A and Other Discussion

[Tao Zhang <>]

the /etc/hosts file is in good shape.

cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.035 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.035 ms

Tao

On 2018-03-26, 12:45 PM, "Michael Johnson" 
<>
 wrote:

    Is your /etc/hosts missing localhost entries by chance? Or otherwise in a 
bad state?
    
    On Mon, Mar 26, 2018 at 04:06:30PM +0000, Tao Zhang wrote:
    >Hi Mark and Szymon,
    >Both “pscheduler troubleshoot” and “pscheduler ping localhost” commands 
timed out on the host.
    >pscheduler troubleshoot
    >Performing basic troubleshooting of localhost.
    >
    >Checking for pScheduler on localhost... Failed.
    >  Request timed out
    >
    >Tao
    >From: Mark Feit 
<>
    >Date: Monday, March 26, 2018 at 11:30 AM
    >To: Tao Zhang 
<>,
 David Szydloski 
<>
    >Cc: 
""
 
<>
    >Subject: Re: [perfsonar-user] pScheduler ping localhost failed
    >
    >Tao Zhang writes:
    >
    >2) Are you able to run "sudo pscheduler ping <host ip>" sucessfully?
    >sudo pscheduler ping 198.165.161.174
    >198.165.161.174: Request timed out
    >
    >I had a quick look at this from a host here at Internet2 and am seeing 
some interesting behavior.  The address pings successfully and the web server 
answers queries for the toolkit and endpoints that don’t exist (e.g., 
https://198.165.161.174/this-does-not-exist).  The connection times out when 
retrieving the URL that pscheduler ping does 
(https://198.165.161.174/pscheduler/), and the code behind that doesn’t 
produce anything more than a greeting.  Some remote poking around shows that 
many of the other endpoints involving GETs work and those involving POSTs do 
not.
    >
    >If you can log onto that host, run “pscheduler troubleshoot”.   If it 
completes successfully, pScheduler on the host is fine and the problem is 
either in the host firewall or somewhere else in the network.
    >
    >By the way, there’s no use sudo; the pScheduler CLI just makes HTTP 
requests and will work just fine when run as an ordinary user.
    >
    >--Mark
    >