Yup... but i only see instructions there for LB < =2.0.X. What exactly
to put/set for LB =3.0.X. ?
TIA
Goncalo
On 06/17/2011 11:29 AM, Daniela Bauer wrote:
> Hi Gonçalo
>
> You should keep the READ_ALL policy so you can put the RTM (see
> http://rtm.hep.ph.ic.ac.uk/) in, so all your jobs show up in these
> nice pretty plots we show people with money to convince them the grid
> is truely working.
>
> Cheers,
>
> Daniela
>
> 2011/6/17 Gonçalo Borges<[log in to unmask]>:
>> Haloo Maarten, Ciao Alessandro
>>
>> 1./ I have removed the empty "READ_ALL" policy
>> 2./ I have added wms02.ncg.ingrid.pt in the "ADMIN_ACCESS" policy
>> 3./ I kepted wms02.ncg.ingrid.pt in the "LOG_WMS_EVENTS" policy
>>
>>
>> After that, the message dissapeared.
>>
>> -bash-3.00$ glite-wms-job-output
>> https://lb02.ncg.ingrid.pt:9000/_HVBsOOKU5_c68hYW05jCw
>> Connecting to the service
>> https://wms02.ncg.ingrid.pt:7443/glite_wms_wmproxy_server
>> ================================================================================
>> JOB GET OUTPUT OUTCOME
>> Output sandbox files for the job:
>> https://lb02.ncg.ingrid.pt:9000/_HVBsOOKU5_c68hYW05jCw
>> have been successfully retrieved and stored in the directory:
>> /tmp/jobOutput/goncalo__HVBsOOKU5_c68hYW05jCw
>> ================================================================================
>>
>>
>> -bash-3.00$ glite-job-status
>> https://lb02.ncg.ingrid.pt:9000/_HVBsOOKU5_c68hYW05jCw
>> *************************************************************
>> BOOKKEEPING INFORMATION:
>> Status info for the Job :
>> https://lb02.ncg.ingrid.pt:9000/_HVBsOOKU5_c68hYW05jCw
>> Current Status: Cleared
>> Status Reason: user retrieved output sandbox
>> Destination: creamce01.ge.infn.it:8443/cream-lsf-cert
>> Submitted: Fri Jun 17 11:12:33 2011 WEST
>> *************************************************************
>>
>> Thanks!
>>
>> Cheers
>> Goncalo
>>
>> On 06/17/2011 10:12 AM, Alessandro Paolini wrote:
>>
>> Il 16/06/2011 17:21, Gonçalo Borges ha scritto:
>>
>> Hi All...
>>
>> 1./ We have configured a dedicated (and separated) WMS and LB server for
>> dedicated NAGIOS submissions. The versions running in the machines are:
>>
>> WMS:
>> # rpm -qa | grep WMS
>> glite-WMS-3.1.31-0.slc4
>>
>> LB:
>> # rpm -qa | grep glite-LB
>> glite-LB-3.2.12-8.sl5
>>
>> ---*---
>>
>> 2./ Everything seems to be working fine but when I try to retrieve the job,
>> I get the following warning:
>>
>> Warning - JobPurging not allowed
>> (The Operation is not allowed: Unable to complete job purge)
>>
>> although the output is indeed retrieved back to me. A status query to the
>> jobid also shows me that the job status continues as "Done (Success)"
>>
>> ---*---
>>
>> 3./ In /var/log/glite/wmsproxy.log, I found messages like:
>>
>> 16 Jun, 16:15:43 -E- PID: 1670 - "wmputils::doPurge": [Error]
>> query_job_status(purger.cpp:125):
>> https://lb02.ncg.ingrid.pt:9000/DasIZls0vcW9-OQRMNTPcg: edg_wll_JobStat [1]
>> Operation not permitted(matching jobs found but authorization failed)
>>
>> which point me to authorization issues between WMS and LB.
>>
>> ---*---
>>
>> 4./ There are several very old Savannah bugs regarding to this issue. Most
>> of the suggest changes in
>> /opt/glite/etc/LB-super-users
>> however, in the new LB 3.0 version I'm using, autorization is handled via
>> glite-lb-authz.conf
>>
>> In that file, generated via YAIM, I have
>>
>> ---*---
>>
>> # cat glite-lb-authz.conf
>> resource "LB" {
>>
>> action "ADMIN_ACCESS" {
>> rule permit {
>> subject = "/C=PT/O=LIPCA/O=LIP/OU=Lisboa/CN=Goncalo Borges"
>> }
>> }
>>
>> action "READ_ALL" {
>>
>> }
>>
>> action "REGISTER_JOBS" {
>> rule permit {
>> subject = ".*"
>> }
>> }
>>
>> action "LOG_WMS_EVENTS" {
>> rule permit {
>> subject = "/C=PT/O=LIPCA/O=LIP/OU=Lisboa/CN=wms02.ncg.ingrid.pt"
>> }
>> }
>>
>> action "LOG_CE_EVENTS" {
>> rule permit {
>> subject = ".*"
>> }
>> }
>>
>> action "LOG_GENERAL_EVENTS" {
>> rule permit {
>> subject = ".*"
>> }
>> }
>>
>> }
>> ---*---
>>
>> Any suggestion? I'm missing a specific action to purge jobs?
>>
>> Cheers
>> Goncalo
>>
>>
>>
>> Hi Goncalo,
>> try to add in the section ADMIN_ACCESS the WMS DN:
>>
>> rule permit {
>> subject = "/C=PT/O=LIPCA/O=LIP/OU=Lisboa/CN=wms02.ncg.ingrid.pt"
>> }
>>
>> and in LOG_WMS_EVENT set the wildcard instead the WMS subject:
>> subject = ".*"
>>
>> then restart the LB
>>
>> Cheers,
>> Alessandro
>>
>>
>>
>
>
