perfsonar development work

[maxim <>]

Hi Vedrin,
May I suggest that it should not be an empty response at all.
If something is missing then it should be exception catched and reported
through
the faultstring  and if it’s the case where there is no data indeed 
in the database then it should be again fault with "no data" faultstring.
Any client API should be able to deal with that (catch and ignore "no data"
with mild warning
and full debug info in debugging mode). It will help enormously to catch 
any problems on the server side.
 Thanks,
         Maxim Grigoriev.
 

> -----Original Message-----
> From: Vedrin Jeliazkov 
> [mailto:]
>  
> Sent: Tuesday, September 26, 2006 9:32 AM
> To: Sven Ubik
> Cc: 
> 
> Subject: [pS-dev] Re: [I2G2-Proto] Empty response from RRD MA
> 
> Hi Sven,
> 
> Sven Ubik 
> <>
>  wrote:
> 
> > Hi,
> > 
> > I am getting empty response from our RRD MA, while rrdtool 
> fetch with 
> > the same parameters produces valid data. Does anybody have any 
> > suggestion where can be the problem?
> > 
> > RRD MA configuration, request and response files are in attachments.
> > 
> > rrdtool fetch returns the following:
> > 
> > # rrdtool fetch /usr/local/snmp_mp/cesnet_gn2.rrd AVERAGE -r 60 -s 
> > 1159254960 -e 1159255080
> >                        bytes_in           bytes_out
> > 
> > 1159255020: 9.4378377833e+06 8.5923076833e+06
> > 1159255080: 1.1388552250e+07 1.0209844850e+07
> > 1159255140: 1.1294331500e+07 9.4089445833e+06
> > 
> > Regards,
> > 
> > Sven Ubik
> 
> This sounds like a linker problem. Java RRD MA uses JNI 
> (native) library for accessing RRDs. The library must exist 
> and ld should know where to find it.
> So, please ensure that the files libjrrd.so and rrdjtool.jar 
> exist in the $PERFSONAR/contrib/rrdjtool/build folder AND 
> this location is known to ld (either by setting and exporting 
> LD_LIBRARY_PATH or by adding a corresponding line in ld.so.conf).
> 
> If you're going to use LD_LIBRARY_PATH, don't forget to 
> re-initialize it on each reboot. Some people have reported 
> problems with LD_LIBRARY_PATH being unexpectedly changed on 
> some Linux flavours, so probably it's better to edit ld.so.conf
> 
> Best regards,
> Vedrin
> 
> 
> 
> 
>