Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Debugging pscheduler

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Debugging pscheduler


Chronological Thread 
  • From: Zhi-Wei Lu <>
  • To: "" <>
  • Subject: [perfsonar-user] Debugging pscheduler
  • Date: Wed, 26 Apr 2017 20:58:05 +0000
  • Accept-language: en-US
  • Authentication-results: internet2.edu; dkim=none (message not signed) header.d=none;internet2.edu; dmarc=none action=none header.from=ucdavis.edu;
  • Ironport-phdr: 9a23:8dbHQBLts7Li4S163NmcpTZWNBhigK39O0sv0rFitYgeLPnxwZ3uMQTl6Ol3ixeRBMOAuqwC17ad6v28EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQtFiT68bL9oIxi7ogrdutQWjIZtN6081gbHrnxUdupM2GhmP0iTnxHy5sex+J5s7SFdsO8/+sBDTKv3Yb02QaRXAzo6PW814tbrtQTYQguU+nQcSGQWnQFWDAXD8Rr3Q43+sir+tup6xSmaIcj7Rq06VDi+86tmTgLjhSEaPDA77W7XkNR9gqJFrhy8uxxxzY3aYICJO/VxZa7SZ88WSXZbU8pNSyBNHIWxZJYPAeobOuZYqpHwqFgOrRu/HAWjBP3gyj5VjXHwwK0xzuMsEADI3QwkAtIDq2nUo8noO6gIT+C1zbLIwS/dYPxLxDfw8Y7FeQ0vr/GLWLJ/a8vRyU83GgPYklqftJbqPy2U1uQWqWSU8fdvVf+3h2I6tQ18oSKjytoyhoXVnI4YyUzI+T97zYs2I9CzVU11Yca8HZdNqS2XNJF6Tt48T210oio3xKMKtYSmcCQUzJkr3wPTZv2DfoSS/B7uWuScLS1miH54dr+znQi+/VS4xuHiS8W50UxGoyRbntXWq3wA1ADf5tKHR/dh+EqqxCyB2BrJ6u5eJEA5jarbJIAlwr43jpcTqkHDHjPumEj4lqOWa1kr9fWy5OT5Y7XmvYWQOJFphQHjKqgum8q/DvokMgUWQmSX5+ex2Kf+8UHnXLlGlPM7nrfDvJzHO8gWora1AwpP3YYi7xa/AS2m0NMdnXQfLVNEdhaHj5XyNlHTPP/3EO2wg0qtkDdw3fzJIKDuAojVInjZjLjhZap961JbyAcr1dBQ+YhUCr8aIPL0XE/+rsbYAgYkMwyv3ennEs5w1ocfWWKUHq+ZK73evUWJ5uIpP+mDepUVuDDjJPg5+fLil2E2lkIAffrh4ZxCImi1BPp9JEOQez/xmdobOWYMogckSuH20huPXSMZLyKqUrgy/TY9AZjjEJzOXKishqCMxiG2AscQa2xbXAOiC3DtIreEWrIzZSPaBtIpxi4bUaWJVoQt3A+vr0n3x6cxfbmcwTERqZ+2jIs93ObUjxxnrTE=
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

Hi all,

 

After perfsonar 4.0 upgrade, I struggled to get one of our perfsonar boxes working again (with help from Andrew Lake).  It worked for a short while, and I noticed that it appears that pscheduler is not working properly.

 

pscheduler task rtt --dest p0.noc.ucdavis.edu --source 128.120.80.78

Submitting task...

Task URL:

https://128.120.80.78/pscheduler/tasks/8f17174e-2ca7-47d8-b98e-dd96b1d01e2b

Running with tool 'ping'

Fetching first run...

128.120.80.78 never scheduled a run for the task.

 

Reverse the source and dest, test worked

 

pscheduler task rtt --source p0.noc.ucdavis.edu --dest 128.120.80.78

Submitting task...

Task URL:

https://p0.noc.ucdavis.edu/pscheduler/tasks/b569b99a-bed7-431c-8948-b34238cdcacf

Running with tool 'ping'

Fetching first run...

 

Next scheduled run:

https://p0.noc.ucdavis.edu/pscheduler/tasks/b569b99a-bed7-431c-8948-b34238cdcacf/runs/d13ba8e6-6fcd-4aa6-8873-b411e9fb99a7

Starts 2017-04-26T13:43:28-07:00 (~7 seconds)

Ends   2017-04-26T13:43:39-07:00 (~10 seconds)

Waiting for result...

 

1       melange-owamp-v4.noc.ucdavis.edu (128.120.80.78)  64 Bytes  TTL 60  RTT   0.3550 ms

2       melange-owamp-v4.noc.ucdavis.edu (128.120.80.78)  64 Bytes  TTL 60  RTT   0.3540 ms

3       melange-owamp-v4.noc.ucdavis.edu (128.120.80.78)  64 Bytes  TTL 60  RTT   0.3680 ms

4       melange-owamp-v4.noc.ucdavis.edu (128.120.80.78)  64 Bytes  TTL 60  RTT   0.3570 ms

5       melange-owamp-v4.noc.ucdavis.edu (128.120.80.78)  64 Bytes  TTL 60  RTT   0.3420 ms

 

0% Packet Loss  RTT Min/Mean/Max/StdDev = 0.342000/0.355000/0.368000/0.014000 ms

 

No further runs scheduled.

 

Bwping works for both directions, though.

 

The pscheduer-scheduler daemon is “running”.  I wonder how I can trace down the real problem behind this issue.

 

Thank you.

 

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

 


Archive powered by MHonArc 2.6.19.

Top of Page