Enable Accounting on gliteCE

From EGEE-see WIki

Jump to: navigation, search

Contents

[edit]

Introduction

Latest glite-apel-* RPMs, available from the GOC accounting web site, make possible enabling of accounting data parsing and publishing for gliteCEs. These instructions are results of the work done at EGEE-SEE-CERT site of the University of Athens (in particular, by Dimitrios Apostolou and Nikos Voutsinas), and were verified at the AEGIS01-PHY-SCL site of the Institute of Physics Belgrade (Antun Balaz).


[edit]

On the gliteCE host 

 touch /opt/glite/etc/blah.config 
 echo 'BLAHPD_ACCOUNTING_INFO_LOG=/var/log/glite/accounting/blahp.log' >> /opt/glite/etc/blah.config 
 mkdir /var/log/glite/accounting 
 chmod u+s /opt/glite/bin/BDlogger 

 rpm -Uvh http://goc.grid-support.ac.uk/gridsite/accounting/glite-apel-rpms/LatestBuild/glite-apel-core-2.0.4-1.noarch.rpm http://goc.grid-support.ac.uk/gridsite/accounting/glite-apel-rpms/LatestBuild/glite-apel-pbs-2.0.2-1.noarch.rpm 
 /opt/glite/yaim/scripts/run_function site-info.def config_apel_pbs


You should now replace the CPUProcessor with static information, because apel-pbs-log-parser tries to retrieve the relevant information from the LCG-CE GIIS. This is not very convenient solution, just the current workaround - fixing of this behaviour should be requested.

Therefore, first the following command should be performed 

 sed -i -e 's/.*<DefaultCPUSpec>.*/-->&/' /opt/glite/etc/glite-apel-pbs/parser-config-yaim.xml

After that, the appropriate values of SpecInt and SpecFp should be entered into /opt/glite/etc/glite-apel-pbs/parser-config-yaim.xml by hand, and the following text should be appended before the ending tag of this file: 

      <BlahdLogProcessor> 
              <SubmitHost>YOUR.GLITECE.HOST</SubmitHost> 
              <BlahdLogPrefix>blahp.log</BlahdLogPrefix> 
              <Logs searchSubDirs="yes" reprocess="no"> 
                <Dir>/var/log/glite/accounting</Dir> 
              </Logs> 
      </BlahdLogProcessor>


[edit]

On the lcg-CE host

It is also advisable to do the following on the lcg-CE host: 

 rpm -Uvh http://goc.grid-support.ac.uk/gridsite/accounting/glite-apel-rpms/LatestBuild/glite-apel-core-2.0.4-1.noarch.rpm http://goc.grid-support.ac.uk/gridsite/accounting/glite-apel-rpms/LatestBuild/glite-apel-pbs-2.0.2-1.noarch.rpm 
 /opt/glite/yaim/scripts/run_function site-info.def config_apel_pbs


[edit]

On the MON host 

 rpm -Uvh http://goc.grid-support.ac.uk/gridsite/accounting/glite-apel-rpms/LatestBuild/glite-apel-core-2.0.4-1.noarch.rpm http://goc.grid-support.ac.uk/gridsite/accounting/glite-apel-rpms/LatestBuild/glite-apel-publisher-2.0.5-1.noarch.rpm http://goc.grid-support.ac.uk/gridsite/accounting/glite-apel-rpms/LatestBuild/glite-apel-pbs-2.0.2-1.noarch.rpm http://goc.grid-support.ac.uk/gridsite/accounting/glite-apel-rpms/LatestBuild/glite-apel-lsf-2.0.3-1.noarch.rpm 
 /opt/glite/yaim/scripts/run_function site-info.def config_apel_rgma

The last step should be done several times, once for each computing element you haave, lcg-CEs and gliteCEs counting as well: each time CE_HOST variable in site-info.def should be set to one of FQDNs of CEs you have; this will enable access for all CEs to the mysql server on the MON host.

[edit]

Testing new setup

Finally test if apel-pbs-parser cron job returns any errors on each CE, and if apel-pbs-publisher works OK on MON host.

Parsing: 

 env RGMA_HOME=/opt/glite APEL_HOME=/opt/glite /opt/glite/bin/apel-pbs-log-parser -f /opt/glite/etc/glite-apel-pbs/parser-config-yaim.xml

If there are no errors returned, the gLiteCE (and other CEs tested this way) publishes information correctly to the MON host.

Publishing: 

 env RGMA_HOME=/opt/glite APEL_HOME=/opt/glite /opt/glite/bin/apel-publisher -f /opt/glite/etc/glite-apel-publisher/publisher-config-yaim.xml

If there are no errors, accounting data is correctly published to the central Registry.

Retrieved from "http://wiki.egee-see.org/index.php/Enable_Accounting_on_gliteCE"
Personal tools