Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Problems with Debian pscheduler

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Problems with Debian pscheduler


Chronological Thread 
  • From: Antoine Delvaux <>
  • To: Alex Hsia <>
  • Cc:
  • Subject: Re: [perfsonar-user] Problems with Debian pscheduler
  • Date: Fri, 24 May 2019 17:52:47 -0400

Hello Alex,

Can you tell us which version of perfSONAR and pScheduler you're using?

Thanks,

-- Antoine --

Le 24 mai 2019 à 17:22, Alex Hsia (via perfsonar-user Mailing List) <> a écrit :

I've been encountering problems with my perfSONAR node since I've transitioned to a Debian O/S.  External partners are having difficulty scheduling tests via pscheduler.  Here's the output from a pscheduler troubleshooting run;

alex@sdmz-perfsonar-40g:~$ pscheduler troubleshoot nettest.boulder.noaa.gov
Performing basic troubleshooting of localhost and nettest.boulder.noaa.gov.

localhost:

  Checking path MTU... 65535 (Local)
  Checking for pScheduler... OK.
  Checking clock... OK.
  Idle test.... 9 seconds.... Checking archiving... OK.


  Checking path MTU... 9000+
  Checking for pScheduler... OK.
  Checking clock... OK.
  Idle test.... 13 seconds.... Checking archiving... OK.


  Checking path MTU... 9000+
  Checking timekeeping... OK.
  Simple stream test.... 12 seconds.... Failed.
Task failed to run properly.

2019-05-24T15:19:45-06:00 on localhost and nettest.boulder.noaa.gov with simplestreamer:

simplestream --dest nettest.boulder.noaa.gov

Run did not complete: Failed


Diagnostics from localhost:
  Try 1 failed: Failed to connect: [Errno 111] Connection refused
  Try 2 failed: Failed to connect: [Errno 111] Connection refused
  Try 3 failed: Failed to connect: [Errno 111] Connection refused
  Try 4 failed: Failed to connect: [Errno 111] Connection refused
  Try 5 failed: Failed to connect: [Errno 111] Connection refused
  Try 6 failed: Failed to connect: [Errno 111] Connection refused
  Try 7 failed: Failed to connect: [Errno 111] Connection refused
  Try 8 failed: Failed to connect: [Errno 111] Connection refused
  Try 9 failed: Failed to connect: [Errno 111] Connection refused
  Try 10 failed: Failed to connect: [Errno 111] Connection refused

Error from localhost:
  Failed to connect: [Errno 111] Connection refused

Diagnostics from nettest.boulder.noaa.gov:
  Nothing to see at the receiving end.

  Timed out

Relevant output from pscheduler:

May 24 15:19:23 nettest runner INFO     314447: With snooze: idle --duration PT5S
May 24 15:19:23 nettest scheduler INFO     8702: Posting non-starting run at 2019-05-25T15:08:16-06:00 for task 600a3d99-ebab-46ea-9883-4ee85a16855c: Error fetching task: Resource Not found.

Where should I look next to troubleshoot?

Alex Hsia ==============================================================
NOAA/OAR                                            Phone: (303)497-6351
Mailstop R/ESRL                                    GVoice: (303)536-5430
325 Broadway                                  e-mail:
Boulder, CO  80305                                   PGP keyid: 8A482A90
========================================================================




Archive powered by MHonArc 2.6.19.

Top of Page