perfSONAR User Q&A and Other Discussion

["hsuan" <>]

Hi all :
I've installed Lookup Service and SNMPMA, but Lookup Service seems have some
problem. 
Following is detail information.
1. Symptom
When I launch new Lookup Service, I can see it on the Service Tree Web page.
https://dc211.internet2.edu/cgi-bin/perfAdmin/tree.cgi ,Then, new SNMPMA is
launched and have registered to new Lookup Service.
But sometimes later , my lookup service and ma have disappear . then I'm
using client.pl send an echo test to my lookup service , 
I got the msg as follow:
" Error sending request to service: 500 alarm
 at ./bin/client.pl line 165"
then I Remove everything except 'DB_CONFIG' from this directory
/var/lib/perfsonar/lookup_service/xmldb and restart the hLS , 
 I can see my lookup service in the service tree web page again . but
sometime later the same problem occurred again . 

2.Software Version
perl-perfSONAR_PS-LookupService-3.1
perl-perfSONAR_PS-SNMPMA-3.1

3.log  - I find some error msg in the lookup service log 
2009/07/09 19:02:29 (32179) ERROR> XMLDB.pm:1049
perfSONAR_PS::DB::XMLDB::updateByName - Error "Error: Document not
found: 9b00ceaf9107ac8c4fb6bfcf6eda0776-control in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
1039".
2009/07/09 19:02:29 (32179) ERROR> gLS.pm:2221
perfSONAR_PS::Services::LS::gLS::handleMessage - Database errors prevented
the transaction from completing.
2009/07/09 19:02:29 (32179) INFO> Request.pm:350
perfSONAR_PS::Request::finish - Total service time for request from
211.79.63.67: 0.270522 seconds
2009/07/09 19:02:29 (15927) INFO> daemon.pl:508 main::psService - Received
incoming connection from:       211.79.63.67
2009/07/09 19:02:29 (32181) ERROR> XMLDB.pm:1049
perfSONAR_PS::DB::XMLDB::updateByName - Error "Error: Document not
found: a103f7946c1c8be1a76905c6e5fff236-control in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
1039".
2009/07/09 19:02:29 (32181) ERROR> gLS.pm:2221
perfSONAR_PS::Services::LS::gLS::handleMessage - Database errors prevented
the transaction from completing.

So what's happening about the lookup service ? Why the sudden cessation of
lookup service? 
I find some error msg about XMLDB . Maybe the problem is caused by DBXML or
others .

Any ideas on how to solve this?

Vicky