perfSONAR User Q&A and Other Discussion

[Roberto Carna <>]

Sorry, I modify some things and now the output from the
troubleshooting command is this:

root@MITLTPSR01:~# 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... OK.
  Checking clock... OK.
  Idle test... Failed.
Unable to post task: Task forbidden by limits:
Hints:
  requester: 179.0.151.2
  server: 198.124.238.138
Identified as everybody
Classified as default
Application: Reject otherwise uncategorized hosts
  Group 1: Limit 'never' failed: Forced failure
  Group 1: Want all, 0/1 passed, 1/1 failed: FAIL
  Group 1: Failed; stopping here.
  Application FAILS
Proposal does not meet limits

Can you explain me what can be wrong ?

Special thanks!!!
El jue., 6 sept. 2018 a las 11:20, Roberto Carna
(<>)
 escribió:
>
> 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
> >
> >
> >