Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "APEL/Documentation"

From EGIWiki
Jump to navigation Jump to search
(Created page with "{{Template:Op menubar}} {{TOC_right}} Category:Accounting == Republishing Accounting Data to APEL == === Do I need to republish? === For grid accounting, APEL has 'Sync Test...")
 
 
(3 intermediate revisions by 2 users not shown)
Line 4: Line 4:


== Republishing Accounting Data to APEL ==
== Republishing Accounting Data to APEL ==
=== Do I need to republish? ===
=== Do I need to republish? ===
For grid accounting, APEL has 'Sync Tests' to confirm the central repository has the same number of jobs that you do locally.
For grid accounting, APEL has 'Sync Tests' to confirm that the central repository has the same number of jobs that you do locally.


To find your sites Sync Test, follow this link after replacing SITE-NAME with your GOCDB site name.
To find your site's Sync Test, follow this link after replacing SITE-NAME with your GOCDB site name.


http://goc-accounting.grid-support.ac.uk/rss/SITE-NAME_Sync.html
http://goc-accounting.grid-support.ac.uk/rss/SITE-NAME_Sync.html


If you're Sync Tests are showing an ERROR for a given month, you will need to republish.
If your Sync Tests are showing an ERROR for a given month, you will need to republish.


Because republishing sends a months’ worth (or more) of accounting data, it can affect the central repositories' QoS. We ask that you open a GGUS ticket to the APEL support unit checking it is okay to republish. We should also be able to tell you what CE's need republishing. For each CE that needs republishing, please see the appropriate subsection below.
Because republishing sends a months’ worth (or more) of accounting data, it can affect the central repositories' QoS. We ask that you open a GGUS ticket to the APEL support unit checking it is okay to republish. We should also be able to tell you what CE's need republishing. For each type of CE that needs republishing, please see the appropriate subsection below.


=== CREAM-CEs ===
=== CREAM-CEs ===
CREAM-CEs use the APEL Client to extract accounting data and send it to the central repository. To republish, you will need to set 'interval = gap' in your client.cfg and to set the start and end of the range you want to republish by setting 'gap_start' and 'gap_end'.
CREAM-CEs use the APEL Client to extract accounting data and send it to the central repository. To republish, you will need to set 'interval = gap' in your client.cfg and to set the start and end of the range you want to republish by setting 'gap_start' and 'gap_end'.


Then run /usr/bin/apelclient to send the data.
Then run /usr/bin/apelclient to send the data.
Remember to revert the config once you have republished successfully.


=== ARC-CEs ===
=== ARC-CEs ===
To republish accounting data from ARC-CEs, you need to use the jura command line tool as below; where <archire dir> is the directory ARC keeps it accounting data, typically /var/spool/arc/urs.data.
To republish accounting data from ARC-CEs, please look at the official documentation (ARC 6.4 version and above): http://www.nordugrid.org/arc/arc6/admins/details/accounting-ng.html#republishing-records
 
<nowiki>jura -u APEL:https://mq.cro-ngi.hr:6162 -r <start time>-<end time> <archive dir></nowiki>
 
For full details on the jura tool, see http://www.nordugrid.org/documents/jura-tech-doc.pdf


=== I have republished, but the Sync Tests are still failing ===
=== I have republished, but the Sync Tests are still failing ===
It may take 24 hours for the new data to propagate to the Sync Tests. If over 24 hours have passed and the Sync Tests still show an ERROR, there may be a configuration error that the APEL team can help you debug.
It may take 24 hours for the new data to propagate to the Sync Tests. If over 24 hours have passed and the Sync Tests still show an ERROR, there may be a configuration error that the APEL team can help you debug.

Latest revision as of 13:00, 21 June 2021

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Republishing Accounting Data to APEL

Do I need to republish?

For grid accounting, APEL has 'Sync Tests' to confirm that the central repository has the same number of jobs that you do locally.

To find your site's Sync Test, follow this link after replacing SITE-NAME with your GOCDB site name.

http://goc-accounting.grid-support.ac.uk/rss/SITE-NAME_Sync.html

If your Sync Tests are showing an ERROR for a given month, you will need to republish.

Because republishing sends a months’ worth (or more) of accounting data, it can affect the central repositories' QoS. We ask that you open a GGUS ticket to the APEL support unit checking it is okay to republish. We should also be able to tell you what CE's need republishing. For each type of CE that needs republishing, please see the appropriate subsection below.

CREAM-CEs

CREAM-CEs use the APEL Client to extract accounting data and send it to the central repository. To republish, you will need to set 'interval = gap' in your client.cfg and to set the start and end of the range you want to republish by setting 'gap_start' and 'gap_end'.

Then run /usr/bin/apelclient to send the data.

Remember to revert the config once you have republished successfully.

ARC-CEs

To republish accounting data from ARC-CEs, please look at the official documentation (ARC 6.4 version and above): http://www.nordugrid.org/arc/arc6/admins/details/accounting-ng.html#republishing-records

I have republished, but the Sync Tests are still failing

It may take 24 hours for the new data to propagate to the Sync Tests. If over 24 hours have passed and the Sync Tests still show an ERROR, there may be a configuration error that the APEL team can help you debug.