Just to make sure, did you set the correct permissions on the audit
dir (/tmp/globus) in order to allow all users to write files in that
dir?
http://www.globus.org/toolkit/docs/4.0/execution/prewsgram/Pre_WS_GRAM_Audit_Logging.html#id2545146
-Stu
On Feb 12, 2008, at Feb 12, 11:21 AM, Frank Breitling wrote:
Hi Stuart,
Thanks for your reply.
We are using GT 4.05 and 4.0.6 but it does not work on either system.
Please find attached my $GLOBUS_LOCATION/etc/globus-job-manager.conf .
You can have access to these systems.
Frank
On 12.02.2008 17:49, Stuart Martin wrote:
Hi Frank,
I don't think either of those bugs should prevent the pre-ws gram
audit files from being created. The individual audit files created
for each job should definitely get created when it is configured in
the job manager config file.
http://www.globus.org/toolkit/docs/4.0/execution/prewsgram/Pre_WS_GRAM_Audit_Logging.html#id2545122
Can you double check that you did this and that your job was
submitted to the job manager where you made this change? What
version are you using? This was added in 4.0.5, so that or 4.0.6
should work?
-Stu
On Feb 12, 2008, at Feb 12, 10:09 AM, Frank Breitling wrote:
Hi Martin,
Thank you for pointing this out.
Just for the records I have filed a bug report on this:
http://bugzilla.globus.org/globus/show_bug.cgi?id=5863 .
I guess I should have done this before.
Good fixing!
Frank
On 12.02.2008 16:45, [EMAIL PROTECTED] wrote:
Frank,
There are existing bugs for very similar topics. See
http://bugzilla.globus.org/globus/show_bug.cgi?id=5777
http://bugzilla.globus.org/globus/show_bug.cgi?id=5778
We hope to get to those bugs hopefully rather soon.
I think if we fixed them your problem should be fixed too.
Thanks for reporting!
Martin
Hello,
Following instructions provided at
http://www.globus.org/toolkit/docs/4.0/execution/wsgram/WS_GRAM_Audit_Logging.html
we have activated WS GRAM audit logging to a PostgreSQL database.
Unfortunately the connection from GRAM to the audit database is
lost,
whenever the database is restarted. Thereafter no audit
information
about new jobs is written to the database. A way to restore the
connection is to restart of the Globus container. However, this
is no
practical solution if many Globus nodes share the same audit
database.
If the database goes down, all Globus containers would have to be
restarted. This of course complicated due to permissions issues
and a
missing automatic restart mechanism of the Globus containers in
those
situations.
In consideration of this problem we have also tried to use the
Pre WS
GRAM audit logging discussed at
http://www.globus.org/toolkit/docs/4.0/execution/prewsgram/Pre_WS_GRAM_Audit_Logging.html
.
Despite following all steps until Section 7.3 no audit files
were found
in the designated folder (/tmp/globus/).
Any help with getting audit logging to work would be very
appreciated.
Frank
-home "/work1/globus/gt4.0.5-x86_64_rhas_4-installer/"
-globus-gatekeeper-host photon.aip.de
-globus-gatekeeper-port 2119
-globus-gatekeeper-subject "/C=DE/O=GermanGrid/OU=AIP/CN=host/
photon.aip.de"
-globus-host-cputype x86_64
-globus-host-manufacturer unknown
-globus-host-osname Linux
-globus-host-osversion 2.6.18
-globus-toolkit-version 4.0.5
-save-logfile on_error
-state-file-dir /work1/globus/gt4.0.5-x86_64_rhas_4-installer//tmp/
gram_job_state
-machine-type unknown
-audit-directory /tmp/globus/
