Hi Winnie,
ARC Accounting record publishing is not the cleanest application I've
come across. It's done by a program called Jura and it reads its config
from the /etc/arc.conf file.
> It also didn't have archiving turned on but it was THOUGHT to be on
> since all the job
> records & etc data were still on it! (But that was because publishing
> was
> failing & failing daily.)
jobreport="APEL:http://mq.cro-ngi.hr:6162"
jobreport_options="urbatch:1000,archiving:/var/run/arc/urs,topic:/queue/global.accounting.cpu.central,gocdb_name:UKI-NORTHGRID-LIV-HEP,use_ssl:true,Network:PROD,benchmark_type:Si2k,benchmark_value:2500.00"
jobreport_credentials="/etc/grid-security/hostkey.pem
/etc/grid-security/hostcert.pem /etc/grid-security/certificates"
jobreport_publisher="jura_dummy"
# Disable (1 month !)
jobreport_period=2500000
These settings seem to work for us (ignore the jura_dummy and
jobreport_period settings – that's just a little experiment I'm doing,
using a cron job. You should set these as told here (or leave them
out/use the defaults):
http://www.nordugrid.org/documents/jura-tech-doc.pdf
> we realized archiving was not configured on it.
Archiving is useful if you ever need to re-report the records, i.e. if
they go missing downsteam in the APEL system.
> But it looks like stuff was still getting deleted after a while
> (unknown how). In backup indices,
> files timestamped 7 July are seen, but have been deleted by don't know
> what. However,
> publishing was working (APEL getting data from it.)
It's wrong if records go missing from the archive_dir, which is
/var/run/arc/urs in our setup.
But perhaps it's an error in my setup to put those files in a “run” dir
– which is reputed to be volatile, they get flushed on reboot!!!
(Note to self: move the archiving dir out of /var/run – that's a Bad
place. You were mad to put it there in the first place. Pull your socks
up, Jones)
Ste
|