perfSONAR User Q&A and Other Discussion

[Roberto Carna <>]

Thanks a lot for your help.

These are the outputs from the trobleoushooyting commands you mentioned:

1) root@perfsonar:/home/admin# 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... OK.
  Checking clock... OK.
  Idle test.... 13 seconds.... Checking archiving... OK.

pScheduler appears to be functioning normally.

2) root@perfsonar:/home/admin# pscheduler troubleshoot ameslab-owamp.es.net
Performing basic troubleshooting of localhost and ameslab-owamp.es.net.

localhost:

  Checking path MTU... Unsafe or unknown: Found only one MTU in trace
to localhost
  Checking for pScheduler... OK.
  Checking clock... OK.
  Idle test.... 13 seconds.... Checking archiving... OK.

ameslab-owamp.es.net:

  Checking path MTU... Unsafe or unknown: Error: Process took too long to run.
  Checking for pScheduler... Failed.
Request timed out

What can be the problem please?

Regards!!!

El mié., 5 sept. 2018 a las 13:54, Mark Feit 
(<>)
 escribió:
>
> Valentin Vidic writes:
>
>     You can try to check pscheduler logs for errors now or try running some
>     simple tests from the command line to see what happens there:
>
> Also try  "pscheduler troubleshoot" and "pscheduler troubleshoot hostname" 
> where hostname is the name of a remote pScheduler host.  That should help 
> narrow the cause down.
>
> --Mark
>
>
>