perfSONAR User Q&A and Other Discussion

["Murilo Vetter" <>]

Hi Sowmya,

I am sending other errors:
2012/05/31 17:30:48 (25898) INFO> daemon.pl:567 main::psService - Received
incoming connection from:    131.225.110.2
2012/05/31 17:30:48 (25916) ERROR> gLS.pm:2366
perfSONAR_PS::Services::LS::gLS::handleMessage - Service was not registered
in this LS.
2012/05/31 17:30:48 (25916) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
131.225.110.2: 0.312703 seconds
2012/05/31 17:30:48 (25917) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
159.178.30.77: 0.224484 seconds
2012/05/31 17:30:48 (25898) INFO> daemon.pl:567 main::psService - Received
incoming connection from:    131.225.110.2
2012/05/31 17:30:49 (25918) ERROR> XMLDB.pm:1453
perfSONAR_PS::DB::XMLDB::insertIntoContainer - Error "Error: Db::put:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Sleepycat/DbXml.pm,
line 395".
2012/05/31 17:30:49 (25918) ERROR> XMLDB.pm:1453
perfSONAR_PS::DB::XMLDB::insertIntoContainer - Error "Error: Db::put:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Sleepycat/DbXml.pm,
line 395".
2012/05/31 17:30:49 (25918) ERROR> XMLDB.pm:1453
perfSONAR_PS::DB::XMLDB::insertIntoContainer - Error "Error: Db::put:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Sleepycat/DbXml.pm,
line 395".
2012/05/31 17:30:49 (25918) ERROR> gLS.pm:2366
perfSONAR_PS::Services::LS::gLS::handleMessage - Database errors prevented
the transaction from completing.
2012/05/31 17:30:49 (25918) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
131.225.110.2: 0.233763 seconds
2012/05/31 17:30:49 (25899) INFO> gLS.pm:2179
perfSONAR_PS::Services::LS::gLS::cleanLSAux - cleanLSAux complete for
container "glsstore.dbxml".
2012/05/31 17:30:50 (25907) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
61.190.88.134: 9.217592 seconds
2012/05/31 17:30:49 (25899) INFO> gLS.pm:2179
perfSONAR_PS::Services::LS::gLS::cleanLSAux - cleanLSAux complete for
container "glsstore-summary.dbxml".
2012/05/31 17:30:49 (25899) INFO> gLS.pm:2009
perfSONAR_PS::Services::LS::gLS::cleanLS - cleanLS complete
2012/05/31 17:30:51 (25892) ERROR> Common.pm:820
perfSONAR_PS::Common::consultArchive - Error while sending request to
server: 500 alarm
2012/05/31 17:30:51 (25892) ERROR> Echo.pm:174
perfSONAR_PS::Client::Echo::ping - Error contacting service
"http://ndb1.internet2.edu:9991/perfSONAR_PS/services/gLS"; : Error while
sending request to server: 500 alarm
2012/05/31 17:30:53 (25899) INFO> gLS.pm:1525
perfSONAR_PS::Services::LS::gLS::summarizeLS - Summarization complete
2012/05/31 17:31:00 (25898) INFO> daemon.pl:567 main::psService - Received
incoming connection from:    200.237.193.14
2012/05/31 17:31:00 (25919) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
200.237.193.14: 0.022192 seconds
2012/05/31 17:31:03 (25901) ERROR> Common.pm:820
perfSONAR_PS::Common::consultArchive - Error while sending request to
server: 500 alarm
2012/05/31 17:31:03 (25901) ERROR> Echo.pm:174
perfSONAR_PS::Client::Echo::ping - Error contacting service
"http://ndb1.internet2.edu:9991/perfSONAR_PS/services/gLS"; : Error while
sending request to server: 500 alarm
2012/05/31 17:31:06 (25890) INFO> daemon.pl:567 main::psService - Received
incoming connection from:    134.68.240.167
2012/05/31 17:31:06 (25922) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
134.68.240.167: 0.09982 seconds
2012/05/31 17:31:06 (25890) INFO> daemon.pl:567 main::psService - Received
incoming connection from:    192.41.231.41

Thanks,
Murilo

-----Mensagem original-----
De: Murilo Vetter 
[mailto:]
 
Enviada em: quinta-feira, 31 de maio de 2012 17:05
Para: 'Sowmya Balasubramanian'; 'Herbert Monteiro'
Cc: 
''
Assunto: RES: [perfsonar-user] LS configuration questions

Hi Sowmya,

I was seeing the logs from LS/hLS and the following lines are appearing:

2012/05/31 16:59:39 (25550) ERROR> XMLDB.pm:322
perfSONAR_PS::DB::XMLDB::openDB - Error "Error: Db::open:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
287".
2012/05/31 16:59:39 (25550) WARN> gLS.pm:387
perfSONAR_PS::Services::LS::gLS::prepareDatabase - Waiting on DBXML error.
2012/05/31 16:59:39 (25082) INFO> daemon.pl:567 main::psService - Received
incoming connection from:    131.225.110.2
2012/05/31 16:59:39 (25082) INFO> daemon.pl:567 main::psService - Received
incoming connection from:    128.104.55.253
2012/05/31 16:59:39 (25082) INFO> daemon.pl:567 main::psService - Received
incoming connection from:    147.231.19.51
2012/05/31 16:59:40 (25595) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
131.225.110.2: 0.387806 seconds
2012/05/31 16:59:41 (25567) ERROR> XMLDB.pm:322
perfSONAR_PS::DB::XMLDB::openDB - Error "Error: Db::open:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
287".
2012/05/31 16:59:41 (25567) WARN> gLS.pm:387
perfSONAR_PS::Services::LS::gLS::prepareDatabase - Waiting on DBXML error.
2012/05/31 16:59:41 (25566) ERROR> XMLDB.pm:322
perfSONAR_PS::DB::XMLDB::openDB - Error "Error: Db::open:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
287".
2012/05/31 16:59:41 (25566) WARN> gLS.pm:387
perfSONAR_PS::Services::LS::gLS::prepareDatabase - Waiting on DBXML error.
2012/05/31 16:59:41 (25593) ERROR> XMLDB.pm:322
perfSONAR_PS::DB::XMLDB::openDB - Error "Error: Db::open:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
287".
2012/05/31 16:59:41 (25593) WARN> gLS.pm:387
perfSONAR_PS::Services::LS::gLS::prepareDatabase - Waiting on DBXML error.
2012/05/31 16:59:41 (25538) ERROR> XMLDB.pm:322
perfSONAR_PS::DB::XMLDB::openDB - Error "Error: Db::open:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
287".
2012/05/31 16:59:41 (25538) ERROR> gLS.pm:391
perfSONAR_PS::Services::LS::gLS::prepareDatabase - There was an error
opening "/var/lib/perfsonar/lookup_service/xmldb/glsstore.dbxml": Error
"Error: Db::open: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
in /opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm,
line 287".
2012/05/31 16:59:41 (25538) FATAL> gLS.pm:2313
perfSONAR_PS::Services::LS::gLS::__ANON__ - There was an error opening
"/var/lib/perfsonar/lookup_service/xmldb/glsstore.dbxml":
2012/05/31 16:59:41 (25538) ERROR> gLS.pm:2366
perfSONAR_PS::Services::LS::gLS::handleMessage - There was an error opening
"/var/lib/perfsonar/lookup_service/xmldb/glsstore.dbxml":
2012/05/31 16:59:41 (25546) ERROR> XMLDB.pm:322
perfSONAR_PS::DB::XMLDB::openDB - Error "Error: Db::open:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
287".
2012/05/31 16:59:41 (25546) ERROR> gLS.pm:391
perfSONAR_PS::Services::LS::gLS::prepareDatabase - There was an error
opening "/var/lib/perfsonar/lookup_service/xmldb/glsstore.dbxml": Error
"Error: Db::open: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
in /opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm,
line 287".
2012/05/31 16:59:41 (25546) FATAL> gLS.pm:2313
perfSONAR_PS::Services::LS::gLS::__ANON__ - There was an error opening
"/var/lib/perfsonar/lookup_service/xmldb/glsstore.dbxml":
2012/05/31 16:59:41 (25546) ERROR> gLS.pm:2366
perfSONAR_PS::Services::LS::gLS::handleMessage - There was an error opening
"/var/lib/perfsonar/lookup_service/xmldb/glsstore.dbxml":
2012/05/31 16:59:41 (25546) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
192.124.227.150: 37.776461 seconds
2012/05/31 16:59:41 (25576) ERROR> XMLDB.pm:322
perfSONAR_PS::DB::XMLDB::openDB - Error "Error: Db::open:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
287".
2012/05/31 16:59:41 (25576) WARN> gLS.pm:387
perfSONAR_PS::Services::LS::gLS::prepareDatabase - Waiting on DBXML error.
2012/05/31 16:59:41 (25538) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
146.57.255.17: 38.553625 seconds
2012/05/31 16:59:43 (25596) ERROR> Request.pm:145
perfSONAR_PS::Request::parse - Received message with incorrect message URI
2012/05/31 16:59:43 (25596) ERROR> daemon.pl:792 main::__ANON__ - Error
handling request: error.transport.parse_error => "Error parsing request:
Received message with incorrect message URI"
2012/05/31 16:59:43 (25596) INFO> Request.pm:357
perfSONAR_PS::Request::finish - Total service time for request from
128.104.55.253: 0.014212 seconds
2012/05/31 16:59:43 (25579) ERROR> XMLDB.pm:322
perfSONAR_PS::DB::XMLDB::openDB - Error "Error: Db::open:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock in
/opt/perfsonar_ps/lookup_service/bin/../lib/perfSONAR_PS/DB/XMLDB.pm, line
287".
2012/05/31 16:59:43 (25579) WARN> gLS.pm:387
perfSONAR_PS::Services::LS::gLS::prepareDatabase - Waiting on DBXML error.

Could these errors influencing in the summarization process?

Thanks,
Murilo Vetter

-----Mensagem original-----
De: 

[mailto:]
 Em nome de Sowmya
Balasubramanian Enviada em: quinta-feira, 31 de maio de 2012 13:58
Para: Herbert Monteiro
Cc: 

Assunto: Re: [perfsonar-user] LS configuration questions

Hi Herbert,

I think there is some issue with the hLS summarization. Your hLS appears in
the gLS but there is nothing in the summarization info. I have attached the
output for your reference.

Hope this helps!

Sowmya


On 5/31/12 7:14 AM, Herbert Monteiro wrote:
> Hi,
>
> we are testing a new Command Line MP register in our  hLS 3.2.1 (our 
> old CLMP doesn't registered the eventTypes tools queried by 
> perfAdmin). But the hLS began to stop unexpectedly after a while. So 
> we decide to configure the hLS to restart every two hours. Now the 
> registers are ok but the perfAdmin doesn`t show the tools.
>
> I think in some possibilities?:
>
> * The restart time is very short for the summarization in the gLS;
> * The hLS summarization in the gLS doesn't contain the eventtype;
> * There is some problem with hLS summarization.
>
> Regards
>
>