perfSONAR User Q&A and Other Discussion

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

 I have a managed host that’s addressed in 1918 space. It’s NTP synched but DNS is blocked by a local firewall so I’ve added entries into /etc/hosts.  pscheduler is failing to run even the most basic localhost functions except for clock checks. httpd is running and accessible as verified by curl.  This host was built and hardened by another party after the perfsonar-testpoint bundle was installed.

# cat /etc/redhat-release 

CentOS Linux release 7.6.1810 (Core) 

# 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)."

pscheduler.log contents with debugging:

——————————————————————

Feb 24 10:09:31 [localhost] journal: pscheduler-api INFO     Started

Feb 24 10:09:32 [localhost] journal: pscheduler-api INFO     Limits loaded from /etc/pscheduler/limits.conf

Feb 24 10:09:53 [localhost] journal: ticker DEBUG    Debug started

Feb 24 10:09:53 [localhost] journal: ticker DEBUG    Tick

Feb 24 10:09:53 [localhost] journal: ticker DEBUG    Next check in 7 seconds

Feb 24 10:09:53 [localhost] journal: scheduler DEBUG    Debug started

Feb 24 10:09:53 [localhost] journal: scheduler DEBUG    Interrupted during select

Feb 24 10:09:53 [localhost] journal: runner DEBUG    Debug started

Feb 24 10:09:53 [localhost] journal: archiver DEBUG    Debug started

Feb 24 10:09:53 [localhost] journal: runner DEBUG    No workers to run.

Feb 24 10:09:53 [localhost] journal: runner DEBUG    Next run or check in 0:01:00

Feb 24 10:10:00 [localhost] journal: pscheduler-api DEBUG    Debug started

Feb 24 10:10:00 [localhost] journal: pscheduler-api DEBUG    REQUEST: GET https://localhost/pscheduler/mtu-safe?dest=localhost

Feb 24 10:10:00 [localhost] journal: pscheduler-api DEBUG    Response 200+JSON: {"message": "Found only one MTU in trace to localhost", "safe": false}

Feb 24 10:10:00 [localhost] journal: pscheduler-api INFO     Started

Feb 24 10:10:01 [localhost] journal: ticker DEBUG    Tick

Feb 24 10:10:01 [localhost] journal: ticker DEBUG    Next check in 14 seconds

Feb 24 10:10:01 [localhost] journal: pscheduler-api INFO     Limits loaded from /etc/pscheduler/limits.conf

Feb 24 10:10:02 [localhost] journal: ticker DEBUG    QM: Processing

Feb 24 10:10:08 [localhost] journal: archiver DEBUG    Nothing happened.

Feb 24 10:10:08 [localhost] journal: archiver DEBUG    Nothing to archive; finding time until next archiving.

Feb 24 10:10:08 [localhost] journal: archiver DEBUG    Nothing in the future.

Feb 24 10:10:08 [localhost] journal: archiver DEBUG    Waiting 15.0 for change or notification

Feb 24 10:10:09 [localhost] journal: ticker DEBUG    Debug discontinued

Feb 24 10:10:09 [localhost] journal: scheduler DEBUG    Debug discontinued

Feb 24 10:10:09 [localhost] journal: runner DEBUG    Debug discontinued

Feb 24 10:10:09 [localhost] journal: archiver DEBUG    Debug discontinued

Feb 24 10:10:09 [localhost] journal: pscheduler-api DEBUG    Debug started

Feb 24 10:10:09 [localhost] journal: pscheduler-api DEBUG    REQUEST: PUT https://localhost/pscheduler/debug?state=0