, view all tags

Attivita' di test sul trasporto dati di DGAS tramite Active MQ

L'installazione del tesbed, la configurazione e i test sono stati effettuati seguendo il piano di test proposto da Andrea Guarise.

For ex. https://cert-wms-01:8443/wmsmon/details/details.php?wms=wms001.cnaf.infn.it

(Static screenshot are available in the screenshots section)

You can go back to the main page clicking on the wmsmon log or on the correspondent part of the navigation bar (ex.):

Installazione e confugurazione CE

I pacchetti delle dipendenze aggiuntive installati sono i seguenti:

  • APR: apr-1.4.2.tar.gz

Vista la mancanza di compilatore C per apr, abbiamo installato gcc versione 4.1.2-48.el5

In particolare:

gcc.x86_64 0:4.1.2-48.el5

Dependency Installed:

cpp.x86_64 0:4.1.2-48.el5

glibc-devel.x86_64 0:2.5-49

glibc-headers.x86_64 0:2.5-49

kernel-headers.x86_64 0:2.6.18-194.11.3.el5

libgomp.x86_64 0:4.4.0-6.el5

apr installato sotto /usr/lib/apr

  • APR-util: apr-util-1.3.9.tar.gz

  • ACTIVEMQ: activemq-cpp-library-3.2.2-src.tar.gz

Lanciando ./configure --prefix=/opt/activemq/lib/ si ottiene questo errore:

checking for pthread_create in -lpthread... no

configure: error: libpthread not found!

A questo punto abbiamo installato un versione piu’ vecchia di apr (apr-1.3.12). Poi abbiamo installato I seguenti pacchetti:









E poi configurato e installato activemq-cpp-library

A questo punto provo ad installare org.glite.dgas.hlr-activemq-producer

rpm -ivh glite-dgas-hlr-activemq-producer-0.0.0-0.centos5.x86_64.rpm

error: Failed dependencies: libactivemq-cpp.so.11()(64bit) is needed by glite-dgas-hlr-activemq-producer-0.0.0-0.centos5.x86_64 libapr-1.so.0()(64bit) is needed by glite-dgas-hlr-activemq-producer-0.0.0-0.centos5.x86_64 libaprutil-1.so.0()(64bit) is needed by glite-dgas-hlr-activemq-producer-0.0.0-0.centos5.x86_64

Ma cio’ e’ normale in quanto le librerie sono state installate da tgz.

Allora ho riprovato con –nodeps ed e’ stato installato il dgas.hlr-activemq-producer

Before describing the available info in detail, notice that various kinds of data are collected:

- WMSLB service and HW status variables (such as daemons status, condor jobs status statistics, File descriptors opened by main processes..) for which the value at the time of measurement is shown. These data are collected by the mean of a client application in python running on the WMS and LB instance.

- Mean job flow rates between wms components (WMproxy, Workload Manager, Job Controller, Condor) across a given time interval reported as well. Time interval is past 15 min by default. These data are collected by the mean of a client application in python running a mysql query on specific LB instance.

- Resource usage statistics for that wms (available only from 2.0 version)

Components Details BOX




It is possible to create CUSTOM CHART selecting this option from the top page menu under "WMS MENU".

It is possible to access a LOAD BALANCING section plot selecting this option from the top page menu under "WMS MENU".

You can access the VOs View section from the main menu ont he top of the page under "VO VIEW"

-- EnricoFattibene - 2010-09-23

Edit | Attach | PDF | History: r14 | r4 < r3 < r2 < r1 | Backlinks | Raw View | More topic actions...
Topic revision: r2 - 2010-09-23 - EnricoFattibene
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback