perfsonar development work

["Michael Bischoff" <>]

Hello Domenico,

Looking at the perfsonar base it handles this case, and it should report 
something like:

RequestHandler: Service sent a response with error information

Having not looked at the Lookupservice code yet, it seems the service is 
actualy creating
the error response and sends this response to the base, the base accepts it 
as a valid
document and prints this. The service should have not have created the error 
response but
thrown an exception and left it to the base to construct a error response.

Best regards,

Michael Bischoff

ps. sorry about the developer talk, it's probably not useful as a help desk 
message but then
again this is the developer list.

> Hello,
>
>
> I am writing you on behalf of the GEANT2 Service Desk. We are installing
> and configuring a monitoring server based on Nagios (equipped with 
> customized plugin to check
> perfsonar services) and on syslog parsing (we are running syslog-ng 
> receving, among the
> others, perfsonar logs).
>
> We have a remark and a request. The remark regards the fact that there
> is no perfsonar service name in the log messages, when the service is 
> dealing with a
> web-service request. As an example, having a look at the LS, AS or RRD-MA 
> logs those messages
> are all looking the same: 2008-06-04 12:40:36,278  INFO - RequestHandler: 
> Service received a
> request 2008-06-04 12:40:36,294  INFO - RequestHandler: Service sent a
> successful response
>
> with no specific tag. This would be fixed in future (as far as I 
> understood) according to the
>  http://wiki.perfsonar.net/jra1-wiki/index.php/Service_Log_List. Could
> you just confirm that it is correct?
>
> The request is related to log content. I tried this morning to simulate
> an error (I used a wrong schema in the request: in the eventType field), 
> basically a wrongly
> formatted request to a service (pS LS), using perfsonar UI. The error 
> message the web service
> returned was perfectly reflecting the problem occurred:
>
> <nmwg:eventType>error.ls.eventtype_not_supported</nmwg:eventType>
>
>
> On the other hand the log files reported:
>
>
> INFO - RequestHandler: Service received a request
> INFO - RequestHandler: Service sent a successful response
>
>
> Which is not true. It is true that, from a functional point of view the
> service was replying correctly to the response, but it is not true that the 
> response was
> successful. Our proposal is that the log should contain the error reported,
> something like:
>
> ERROR - RequestHandler: Service sent an error response - Error message:
> error.ls.eventtype_not_supported
>
> This would help us a lot in supporting users, debugging problems and
> taking the proper actions when a problem is detected.
>
> Many thanks in advance,
> Domenico
>
>
> --
> ______________________________________________________________________
>
>
> Domenico Vicinanza
> Services Support Engineer
>
>
> DANTE - www.dante.net
>
>
> Tel: +44 (0)1223 371 300
> Fax: +44 (0)1223 371 371
> Email: 
> 
>
>
>
> City House, 126-130 Hills Road
> Cambridge CB2 1PQ
> UK
> _____________________________________________________________________
>
>
>