perfSONAR User Q&A and Other Discussion

[David Szydloski <>]

Tao,

First off, I'm using perfSONAR in a corporate environment that doesn't have rDNS records and I have no issue with the service so I don't think its that.

Here are some questions I have for you:

1) Are there any errors in /var/log/pscheduler/pscheduler.log?

2) Are you able to run "sudo pscheduler ping <host ip>" sucessfully? 

3) You say "We cannot do any tests with this node" do you mean you have tests defined on the host and those tests aren't being scheduled? What are the results of running "sudo pscheduler schedule +PT1H -PT1H?"

4) What perfsonar package are you running on this host?

Cheers,

David

On Mon, Mar 26, 2018 at 8:25 AM, Tao Zhang <> wrote:

Hello Group,

 

We have a perfSONAR node: 198.165.161.174. We cannot do any test with this node.

I run pscheduler ping localhost on the host and I got “localhost: Request timed out”.

 

I checked today’s pscheduler.log file, only two lines showed up in the file:

Mar 25 06:27:46 pS-mun-stj journal: pscheduler-api INFO     Started

Mar 25 06:27:47 pS-mun-stj journal: pscheduler-api INFO     Limits loaded from /etc/pscheduler/limits.conf

 

I checked and restarted the four pscheduler services on the node, they are all up and running.

pscheduler-archiver  

pscheduler-runner    

pscheduler-scheduler 

pscheduler-ticker

 

Could it be related to DNS? This node doesn’t have reverse records in our DNS server at this moment.

 

Any suggestions?

 

Tao

 

--

David Szydloski

Core Deployment Engineer

VidScale, Inc.