perfSONAR User Q&A and Other Discussion

[Tao Zhang <>]

Thanks David, for the quick response.

 

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

fgrep ' ERROR ' /var/log/pscheduler/pscheduler.log

Did find any ERROR in today’s pscheduler.log file.

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

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?"

 

If I run the CLI to initiate the test with other nodes on the host:

owping lat-vctr3pfs1.canarie.ca

owping: FILE=protocol.c, LINE=1515, _OWPReadAcceptSession:Unable to read from socket.

owping: FILE=owping.c, LINE=200, Session Failed!

 

bwctl –T iperf3 –s 198.165.161.174 –c lat-vctr3pfs1.canarie.ca

bwctl: Unable to connect to 205.189.32.174

 

 

sudo pscheduler schedule +PT5H -PT5H

Nothing scheduled 2018-03-26T06:44:17-02:30 to 2018-03-26T16:44:17-02:30

 

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

It’s perfSONAR toolkit version 4.0.2.3-1.el7

 

 

Thanks

 

Tao

 

From: David Szydloski <>
Date: Monday, March 26, 2018 at 9:48 AM
To: Tao Zhang <>
Cc: "" <>
Subject: Re: [perfsonar-user] pScheduler ping localhost failed

 

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.