OLIVIER DEVROEDE omdevroe@vub.ac.be at 12:54, 9 February 2018

2018-02-09T12:54:20Z

← Older revision		Revision as of 12:54, 9 February 2018
Line 52:		Line 52:
	</pre>		</pre>

			=== In case of data not being published ===
			In case the data is not being published, the gap needs to be closed. <br>
			the info on how to do this can be found in this page: [[ApelGapPublishing]]


	{{TracNotice\|{{PAGENAME}}}}		{{TracNotice\|{{PAGENAME}}}}

Maintenance script: Created page with " === APEL === ncm-apel only writes the configuration file for both the ce/gk and the rgma-server RGMA_SERVER: /opt/glite/etc/glite-apel-publisher/publisher-config.xml CE..."

2015-08-26T12:28:12Z

Created page with " === APEL === ncm-apel only writes the configuration file for both the ce/gk and the rgma-server *RGMA_SERVER: /opt/glite/etc/glite-apel-publisher/publisher-config.xml *CE..."

New page

=== APEL ===
ncm-apel only writes the configuration file for both the ce/gk and the rgma-server
*RGMA_SERVER: /opt/glite/etc/glite-apel-publisher/publisher-config.xml
*CE/GK: /opt/glite/etc/glite-apel-pbs/parser-config.xml

What is needed (only once) is to configure the mysql-server on the RGMA-server to accept the APEL data.
This data is fed into the db through cron-jobs
*RGMA_SERVER: /etc/cron.d/apel-publisher.ncm-cron.cron
*CE/GK: /etc/cron.d/apel-pbs-log-parser.ncm-cron.cron

Run the commands in these jobs to see if all is working well.
==== Initial configuration ====
*set APEL_HOME vairable (eg check the cron job)
<pre>
export APEL_HOME=/opt/glite
</pre>
Run the following script to setup the accounting DB-structure on the RGMA-server only: <tt>/opt/glite/share/glite-apel-core/scripts/apel-db-config.py</tt>
Follow the instructions on what to add as variables (values such as user, db adn password can be found in the /opt/glite/etc/glite-apel-publisher/publisher-config.xml file). Eg.
<tt> /opt/glite/share/glite-apel-core/scripts/apel-db-config.py --user accounting --password yeah_right --database accounting --gkhost gridce.iihe.ac.be --cehost gridce.iihe.ac.be -o ./accounting.sql </tt>
It will create a .sql-file. Then one has to run
<pre>
mysql -u root -p < ./accounting.sql
</pre>
Then run the cron-jobs to test the config.

'''Remark 1''': when you see something like
<pre>
apel-publisher - Checking valid CPU spec data exists
apel-publisher - program aborted
apel-publisher - Cannot generate any accounting records because no cpu spec value is defined in the SpecRecords table,
spec values are added when running the CPUProcessor, check user documentation for more help
</pre>
First run the cron-job on the CE, it will fix this.

'''Remark 2''': because we have separate private routes from our CE to pur RGMA-server, we had to add an extra line in the accounting.sql to allow connection through this interface (CE is gridce.iihe.ac.be, private address is gridce.wn.iihe.ac.be).
<pre>
use mysql;
INSERT INTO user (host,user,password,create_priv, drop_priv) VALUES ('gridce.wn.iihe.ac.be','accounting',password('yeah_right'),'Y','Y');
flush privileges;
</pre>

=== Accessing the mysql database ===

*To access the database on APEL
<pre>
mysql -u accounting -h apel.iihe.ac.be -p
</pre>
*The password can be found in
<pre>
cat /etc/accounting.conf
</pre>

{{TracNotice|{{PAGENAME}}}}

APEL - Revision history

OLIVIER DEVROEDE omdevroe@vub.ac.be at 12:54, 9 February 2018

Maintenance script: Created page with " === APEL === ncm-apel only writes the configuration file for both the ce/gk and the rgma-server *RGMA_SERVER: /opt/glite/etc/glite-apel-publisher/publisher-config.xml *CE..."

Maintenance script: Created page with " === APEL === ncm-apel only writes the configuration file for both the ce/gk and the rgma-server RGMA_SERVER: /opt/glite/etc/glite-apel-publisher/publisher-config.xml CE..."