perfSONAR User Q&A and Other Discussion

["Nina Jeliazkova" <>]

Roman, 

Thanks for the update. Sounds like the issue is somewhere else, I'll be
waiting for the log file.

Nina

> >>     
> >
> > That's strange, the only difference from message point of view should be
> that
> > the request for interface utilization are aggregated differently.  The
issue
> > with aggregated request is that if the query for just one of the
interfaces
> > fails (e.g. has configuration errors), then the entire requests fails. At
> >   
> 
> If the request contains more than one data trigger (sub-requests) then 
> even if one of them fails the rest may give correct results. In this 
> case the response will have an error code for that failing data trigger 
> (sub-request) and correct data for other data triggers.
> 
> Roman
> 
> 
> 
> > least this was with pre 2.0 perfsonar, but it might be the same with 2.0
> > distribution. Anyway, could you check all interfaces for configuration
> errors
> > (missing rrd files, etc.)?
> >
> > Regards,
> > Nina
> >
> >   
> >>> Also, could you look into perfsonar.log (JWS is now configured in debug
> >>>       
> >> mode,
> >>     
> >>> so it creates perfsonar.log file on start , in Windows it is in your
> >>>       
> >> desktop,
> >>     
> >>> on Linux I guess on some temporary directory or you home directory).
> >>>   
> >>>       
> >> I will check the perfsonar.log and keep you posted.
> >>     
> >>> Is there any chance to test your service from outside?
> >>>   
> >>>       
> >> I will ask the local LAN administrators and tell you if/when the service 
> >> would be available.
> >>     
> >>> Regards,
> >>> Nina
> >>>   
> >>>       
> >> Anayway, many thanks for your usual support Nina ! ;-)
> >> Bgrds/Fred
> >>     
> >
> >
> >
> >   
>