perfSONAR User Q&A and Other Discussion

["Uhl, George D. (GSFC-423.0)[SGT INC]" <>]

Hi Mark,

The /etc/resov.conf file pointed to a blocked DNS server.  I have had our security team unblock it on the local firewall and it’s all working now.  This brings up an issue about installing perfsonar in closed and highly secured environments.  Is there a way to support private IP’s in perfsonar without DNS particularly If the test nodes don’t have and probably will never have a FQDN?

Thanks,

George

From: Mark Feit <>
Date: Monday, February 25, 2019 at 7:39 PM
To: George Uhl <>, "" <>
Subject: Re: [perfsonar-user] localhost pscheduler failing

"Uhl, George D. (GSFC-423.0)[SGT INC]" writes:

# pscheduler ping localhost

localhost: Request timed out

 

# 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... Failed.

Request timed out

 

# pscheduler clock

clock      2019-02-24T11:38:39.744653-05:00 synchronized   localhost

 

# curl -k https://localhost/pscheduler

"This is the pScheduler API server on localhost (wsgt-ps)."

 

There’s a lot of overlap in those:  The cURL, “pscheduler ping”,   and the “Checking for pScheduler” phase of troubleshooting all fetch the same URL (https://localhost/pscheduler) through the API.  The clock command does something marginally less trivial, fetching https://localhost/pscheduler/clock.  Neither does anything particularly taxing.

 

You mention that DNS is blocked, so there’s always the possibility that something is holding up queries and gumming up the works.  Does /etc/resolv.conf still point at a blocked server?

 

--Mark