Tags:
, view all tags

Certification report internal patch 3777

Author(s): Elisabetta Molinari & Alessio Gianelle

Outcome: In Certification..

Information

Patch 3777 https://savannah.cern.ch/patch/index.php?3777
Build reports http://etics-repository.cern.ch/repository/reports/id/b67cc5fe-8ebf-4d04-89e1-0b741c1654a6/sl5_x86_64_gcc412/-/reports/index.html
Repository http://etics-repository.cern.ch/repository/pm/registered/repomd/name/patch_3777_3/index.html

Upgrade from production

Test Report

[ale@cream-03 UI]$ ./UI-certtest.sh 
Using ./UI-certconfig
START Wed Nov  3 17:20:21 CET 2010 
------------------------------------------------
Enter the test user pass:
Log files will be stored in /tmp/logs_101103172024
*SL4 tests skipped
*Running SL5 tests
UI-commands-exist-all.sh PASSED
UI-libraries-exist.sh PASSED
UI-security-myproxy-init-info-destroy.sh PASSED
UI-security-voms-proxy-init-info-destroy.sh PASSED
*Running COMMON tests
UI-environment.csh PASSED
UI-environment.sh PASSED
UI-exec-help-glite-delegation.sh PASSED
UI-exec-help-glite-sd-query.sh PASSED
UI-exec-help-lcg-info.sh PASSED
UI-exec-help-lcgtags.sh PASSED
UI-exec-help-managevotag.sh PASSED
UI-exec-version-glite-transfer.sh PASSED
UI-exec-version-glite-wms-job.sh PASSED
UI-exec-version-grid-proxy.sh PASSED
UI-exec-version-lcg.sh PASSED
UI-exec-version-myproxy.sh PASSED
UI-exec-version-uberftp.sh PASSED
UI-exec-version-voms-proxy.sh PASSED
UI-glite-environment.csh PASSED
UI-glite-environment.sh PASSED
UI-inf-lcg-info-ce.sh PASSED
UI-inf-lcg-info-se.sh PASSED
UI-inf-lcg-infosites.sh PASSED
UI-inf-ldapsearch.sh PASSED
UI-security-grid-cert-info.sh PASSED
UI-security-grid-proxy-info.sh PASSED
UI-security-grid-proxy-init-info-destroy.sh PASSED
UI-security-myproxy-change-pass-phrase.sh PASSED
UI-security-voms-proxy-info.sh PASSED
UI-tags-lcgtags.sh PASSED
UI-tags-managevotag.sh PASSED
UI-workload-glite-submit-wait-output.sh PASSED
UI-workload-glite-wms-deleg-submit-wait-output.sh PASSED
UI-workload-glite-wms-errors.sh PASSED
UI-workload-glite-wms-job-list-match.sh PASSED
UI-workload-glite-wms-submit-wait-output.sh PASSED
TEST_PASSED

Zipped log should be found here

Check Bugs

Bug #50761 : segmentation fault in glite-brokerinfo on glite-WN SL5/x86_64 FIXED

  • Install the required rpm
[root@cream-03 ~]# yum install glite-wms-brokerinfo-access
Loaded plugins: kernel-module, protectbase
Repository sl-base is listed more than once in the configuration
Repository sl-security is listed more than once in the configuration
Repository sl-fastbugs is listed more than once in the configuration
Repository sl-contrib is listed more than once in the configuration
3 packages excluded due to repository protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package glite-wms-brokerinfo-access.x86_64 0:3.3.1-1.sl5 set to be updated
--> Finished Dependency Resolution
Beginning Kernel Module Plugin
Finished Kernel Module Plugin

Dependencies Resolved

=============================================================================================================================
 Package                                Arch              Version                   Repository                          Size
=============================================================================================================================
Installing:
 glite-wms-brokerinfo-access            x86_64            3.3.1-1.sl5               ETICS-name-patch_3777_1            124 k

Transaction Summary
=============================================================================================================================
Install       1 Package(s)
Upgrade       0 Package(s)

Total download size: 124 k
Is this ok [y/N]: y
Downloading Packages:
glite-wms-brokerinfo-access-3.3.1-1.sl5.x86_64.rpm                                                    | 124 kB     00:00     
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing     : glite-wms-brokerinfo-access                                                                           1/1 

Installed:
  glite-wms-brokerinfo-access.x86_64 0:3.3.1-1.sl5                                                                           

Complete!
  • Test it
[ale@cream-03 ~]$ glite-brokerinfo -f test 

glite-brokerinfo: please specify a function with parameters
use glite-brokerinfo --help for functions and parameters list

Bug #56034 : Matchmaking with JobType=Normal does not take NodeNumber into account FIXED

  • Submit this jdl:
    [ale@cream-03 ~]$ cat test.jdl 
    [
    Executable = "/bin/ls" ;
    Arguments = "-lha " ;
    Stdoutput = "ls.out" ;
    JobType = "normal";
    CpuNumber = 4;
    Retrycount = 2;
    ShallowRetryCount = -1;
    requirements = other.GlueCEStateStatus == "Production" || other.GlueCEStateStatus == "testbedb";
    usertags = [ exe = "ls" ];
    VirtualOrganisation="dteam";
    ]
  • And verify the submitted jdl:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --debug  test.jdl 
    [...]
    02 Nov 2010, 15:43:32 -I- PID: 16559 (Debug) - Submitting JDL [ Retrycount = 2; Arguments = "-lha "; MyProxyServer = "myproxy.cnaf.infn.it"; DefaultNodeRetryCount = 5; JobType = "normal"; Executable = "/bin/ls"; VirtualOrganisation = "dteam"; SignificantAttributes = { "Requirements","Rank" }; CpuNumber = 4; Stdoutput = "ls.out"; ShallowRetryCount =  -1; requirements = ( ( other.GlueCEStateStatus == "Production" || other.GlueCEStateStatus == "testbedb" ) && ( other.GlueCEStateStatus == "Production" || other.GlueCEStateStatus == "CREAMPreCertTests" || other.GlueCEStateStatus == "testbedb" ) ) && other.GlueCEInfoTotalCPUs >= 4; usertags = [ exe = "ls" ]; rank =  -other.GlueCEStateEstimatedResponseTime; Type = "job"; DefaultRank =  -other.GlueCEStateEstimatedResponseTime; AllowZippedISB = false ]
    [...]

Bug #59611 : WMS UI: should transfer files even if size is 0 bytes FIXED

[ale@cream-03 ~]$  cat test.jdl | grep -v ^#
[
Executable = "/bin/ls" ;
Arguments = "-lha " ;
Stdoutput = "ls.out" ;
InputSandbox = { "test.empty"} ;
OutputSandbox = { ".BrokerInfo", "ls.out"} ;
Retrycount = 2;
ShallowRetryCount = -1;
usertags = [ exe = "ls" ];
VirtualOrganisation="dteam";
]

[ale@cream-03 ~]$ ls -l test.empty
-rw-rw-r-- 1 ale ale 0 Oct 29 17:22 test.empty

[ale@cream-03 ~]$  glite-wms-job-submit -a test.jdl 

Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server


====================== glite-wms-job-submit Success ======================

The job has been successfully submitted to the WMProxy
Your job identifier is:

https://devel07.cnaf.infn.it:9000/3IBVL8mGKQxNQmdrPM4QOw

==========================================================================

[ale@cream-03 ~]$ glite-wms-job-status https://devel07.cnaf.infn.it:9000/3IBVL8mGKQxNQmdrPM4QOw


======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:

Status info for the Job : https://devel07.cnaf.infn.it:9000/3IBVL8mGKQxNQmdrPM4QOw
Current Status:     Done (Success)
Logged Reason(s):
    - job completed
    - Job Terminated Successfully
Exit code:          0
Status Reason:      Job Terminated Successfully
Destination:        infnlns-ce-01.ct.pi2s2.it:8443/cream-lsf-cert
Submitted:          Tue Nov  2 15:50:24 2010 CET
==========================================================================

[ale@cream-03 ~]$ glite-wms-job-output https://devel07.cnaf.infn.it:9000/3IBVL8mGKQxNQmdrPM4QOw

Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server


================================================================================

         JOB GET OUTPUT OUTCOME

Output sandbox files for the job:
https://devel07.cnaf.infn.it:9000/3IBVL8mGKQxNQmdrPM4QOw
have been successfully retrieved and stored in the directory:
/tmp/ale_3IBVL8mGKQxNQmdrPM4QOw

================================================================================

[ale@cream-03 ~]$ cat /tmp/ale_3IBVL8mGKQxNQmdrPM4QOw/ls.out 
total 12K
drwxr-xr-x 2 dteam035 dteam 4.0K Nov  2 15:50 .
drwxr-xr-x 3 dteam035 dteam 4.0K Nov  2 15:50 ..
-rw-r--r-- 1 dteam035 dteam 2.3K Nov  2 15:50 .BrokerInfo
-rw-r--r-- 1 dteam035 dteam    0 Nov  2 15:50 ls.out
-rw-r--r-- 1 dteam035 dteam    0 Nov  2 15:50 test.empty
-rw-r--r-- 1 dteam035 dteam    0 Nov  2 15:50 .tmp_file

Bug #60175 : Job Collections using option not working as gLite 3.1 UI FIXED

[ale@cream-03 ~]$ ls -l collection/
total 4
-rw-rw-r-- 1 ale ale 344 Nov  2 15:55 test.jdl
[ale@cream-03 ~]$ cat collection/test.jdl 
[
JobType="MPICH";
CpuNumber = 2;
Executable = "/bin/ls" ;
Arguments = "-lha " ;
Stdoutput = "ls.out" ;
OutputSandbox = { ".BrokerInfo", "ls.out"} ;
Retrycount = 2;
ShallowRetryCount = 3;
requirements = other.GlueCEStateStatus == "Production" || other.GlueCEStateStatus == "testbedb";
usertags = [ exe = "ls" ];
VirtualOrganisation="dteam";
]


[ale@cream-03 ~]$ glite-wms-job-submit -a --collection collection/

Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server


====================== glite-wms-job-submit Success ======================

The job has been successfully submitted to the WMProxy
Your job identifier is:

https://devel07.cnaf.infn.it:9000/W0dGTWgC5GDU-el1dAf24Q

==========================================================================


[ale@cream-03 ~]$ glite-wms-job-status https://devel07.cnaf.infn.it:9000/W0dGTWgC5GDU-el1dAf24Q


======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:

Status info for the Job : https://devel07.cnaf.infn.it:9000/W0dGTWgC5GDU-el1dAf24Q
Current Status:     Waiting 
Submitted:          Tue Nov  2 16:07:01 2010 CET
==========================================================================

- Nodes information for: 
    Status info for the Job : https://devel07.cnaf.infn.it:9000/_PjO4jNq7Ju6VUdgGIUbYQ
    Current Status:     Ready 
    Destination:        ce01-lcg.cr.cnaf.infn.it:8443/cream-lsf-dteam
    Submitted:          Tue Nov  2 16:07:01 2010 CET
==========================================================================

Bug #67054 : cancel of node in Submitted state connects to ghemon.cnaf.infn.it FIXED

[ale@cream-03 ~]$ glite-wms-job-submit -a --register-only test.jdl

Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server


====================== glite-wms-job-submit Success ======================

The job has been successfully registered to the WMProxy
Your job identifier is:

https://devel07.cnaf.infn.it:9000/7OOMitZ4VWAd8_NV7-30_Q

==========================================================================

To complete the operation, the following InputSandbox files need to be transferred:

==========================================================================================================
InputSandbox file : /home/ale/test.empty
Destination : gsiftp://devel14.cnaf.infn.it:2811/var/glite/SandboxDir/7O/https_3a_2f_2fdevel07.cnaf.infn.it_3a9000_2f7OOMitZ4VWAd8_5fNV7-30_5fQ/input/test.empty
-----------------------------------------------------------------------------

then start the job by issuing a submission with the option:
 --start https://devel07.cnaf.infn.it:9000/7OOMitZ4VWAd8_NV7-30_Q



[ale@cream-03 ~]$ strace glite-wms-job-submit --start  https://devel07.cnaf.infn.it:9000/7OOMitZ4VWAd8_NV7-30_Q 2> err

Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server


====================== glite-wms-job-submit Success ======================

The job has been successfully started to the WMProxy
Your job identifier is:

https://devel07.cnaf.infn.it:9000/7OOMitZ4VWAd8_NV7-30_Q

==========================================================================


[ale@cream-03 ~]$  grep 131.154.100.122 err
[ale@cream-03 ~]$ 
[ale@cream-03 ~]$ glite-wms-job-status https://devel07.cnaf.infn.it:9000/7OOMitZ4VWAd8_NV7-30_Q


======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:

Status info for the Job : https://devel07.cnaf.infn.it:9000/7OOMitZ4VWAd8_NV7-30_Q
Current Status:     Scheduled 
Status Reason:      unavailable
Destination:        cream-ce.research-infrastructures.eu:8443/cream-pbs-cert
Submitted:          Tue Nov  2 16:13:11 2010 CET
==========================================================================

Bug #68052 : glite-wms-job-output produces no JSON compliant formatting NOT FIXED

  • getOutput with Success for one sandbox retrieved:
  • getOutput with Success with multiple sandbox retrieved (more jobs):
  • getOutput without success with sandobox retrieved:
  • getOutput of a collection of jobs:

Bug #68307 : WMS-UI: syntax error for correct JDL when substr is used FIXED

  • To test this bug you need to install glite-jdl-api-cpp-3.2.4-2.sl5 on a WMS, then try a list-match or a submission with this jdl:
    [ale@cream-03 ~]$ cat 68307.jdl 
    [
    Executable = "/bin/ls" ;
    Arguments = "-lha " ;
    Stdoutput = "ls.out" ;
    OutputSandbox = { "ls.out"} ;
    requirements = int(substr(other.GLUECECapability[0],size("CPUScalingReferenceSI00="))) == 1000; 
    VirtualOrganisation="dteam";
    ]
    
    [ale@cream-03 test]$ glite-wms-job-list-match -a -e https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server --rank 68307.jdl 
    
    Connecting to the service https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server
    
    ==========================================================================
    
               COMPUTING ELEMENT IDs LIST 
     The following CE(s) matching your job requirements have been found:
    
       *CEId*                                                   *Rank*
    
     - ce106.cern.ch:2119/jobmanager-lcglsf-grid_2nh_dteam              0
     - ce106.cern.ch:2119/jobmanager-lcglsf-grid_dteam                  0
     - ce107.cern.ch:2119/jobmanager-lcglsf-grid_2nh_dteam              0
     - ce107.cern.ch:2119/jobmanager-lcglsf-grid_dteam                  0
     - ce124.cern.ch:2119/jobmanager-lcglsf-grid_2nh_dteam              0
     - ce124.cern.ch:2119/jobmanager-lcglsf-grid_dteam                  0
     - ce125.cern.ch:2119/jobmanager-lcglsf-grid_2nh_dteam              0
     - ce125.cern.ch:2119/jobmanager-lcglsf-grid_dteam                  0
     - ce126.cern.ch:2119/jobmanager-lcglsf-grid_2nh_dteam              0
     - ce126.cern.ch:2119/jobmanager-lcglsf-grid_dteam                  0
     - ce127.cern.ch:2119/jobmanager-lcglsf-grid_2nh_dteam              0
     - ce127.cern.ch:2119/jobmanager-lcglsf-grid_dteam                  0
    
    ==========================================================================
    

Bug #68465 : glite-wms-job-cancel produces no JSON compliant formatting FIXED

  • Cancel a single job:
    [ale@cream-03 ~]$ glite-wms-job-submit -a test.jdl
    
    Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
    
    
    ====================== glite-wms-job-submit Success ======================
    
    The job has been successfully submitted to the WMProxy
    Your job identifier is:
    
    https://devel07.cnaf.infn.it:9000/Plkq83qvM9G0UfdsbnQDrQ
    
    ==========================================================================
    
    
    [ale@cream-03 ~]$ glite-wms-job-cancel --json https://devel07.cnaf.infn.it:9000/Plkq83qvM9G0UfdsbnQDrQ
    {    "result": "success",    "jobs": { "https://devel07.cnaf.infn.it:9000/Plkq83qvM9G0UfdsbnQDrQ": { "endpoint": "https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server", "status": "cancel requested" }    } } 
    [ale@cream-03 ~]$ glite-wms-job-status https://devel07.cnaf.infn.it:9000/Plkq83qvM9G0UfdsbnQDrQ
    
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/Plkq83qvM9G0UfdsbnQDrQ
    Current Status:     Cancelled 
    Destination:        cale.uniandes.edu.co:8443/cream-pbs-dteam
    Submitted:          Tue Nov  2 16:56:10 2010 CET
    ==========================================================================
  • Cancel of single job using --pretty-print option
[ale@cream-03 ~]$ glite-wms-job-submit -a test.jdl

Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server


====================== glite-wms-job-submit Success ======================

The job has been successfully submitted to the WMProxy
Your job identifier is:

https://devel07.cnaf.infn.it:9000/B4Pyutn2BU3bhbaxIUgPdA

==========================================================================
[ale@cream-03 ~]$ glite-wms-job-cancel --json --pretty-print https://devel07.cnaf.infn.it:9000/B4Pyutn2BU3bhbaxIUgPdA
{
   result: success
   jobs: {
     https://devel07.cnaf.infn.it:9000/B4Pyutn2BU3bhbaxIUgPdA: {
       endpoint: https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
       status: cancel requested
     } 
  }
}

[ale@cream-03 ~]$ glite-wms-job-status https://devel07.cnaf.infn.it:9000/B4Pyutn2BU3bhbaxIUgPdA


======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:

Status info for the Job : https://devel07.cnaf.infn.it:9000/B4Pyutn2BU3bhbaxIUgPdA
Current Status:     Cancelled 
Destination:        creamce.grid.rug.nl:8443/cream-pbs-medium
Submitted:          Tue Nov  2 16:58:05 2010 CET
==========================================================================
  • Cancel of multiple jobs:
    [ale@cream-03 ~]$ glite-wms-job-submit -a -o jobid test.jdl
    
    Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
    
    
    ====================== glite-wms-job-submit Success ======================
    
    The job has been successfully submitted to the WMProxy
    Your job identifier is:
    
    https://devel07.cnaf.infn.it:9000/9IU8sgB_T-882aqSR8_nAQ
    
    The job identifier has been saved in the following file:
    /home/ale/jobid
    
    ==========================================================================
    
    
    [ale@cream-03 ~]$ glite-wms-job-submit -a -o jobid test.jdl
    
    Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
    
    
    ====================== glite-wms-job-submit Success ======================
    
    The job has been successfully submitted to the WMProxy
    Your job identifier is:
    
    https://devel07.cnaf.infn.it:9000/_eixgfYvYWoCiZ21ER4vYw
    
    The job identifier has been saved in the following file:
    /home/ale/jobid
    
    ==========================================================================
    
    
    [ale@cream-03 ~]$ glite-wms-job-submit -a -o jobid test.jdl
    
    Connecting to the service https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
    
    
    ====================== glite-wms-job-submit Success ======================
    
    The job has been successfully submitted to the WMProxy
    Your job identifier is:
    
    https://devel07.cnaf.infn.it:9000/fAJnQQPFMqrXT1xAFXVxxg
    
    The job identifier has been saved in the following file:
    /home/ale/jobid
    
    ==========================================================================
    
    
    [ale@cream-03 ~]$ glite-wms-job-cancel --json --noint -i jobid 
    {    "result": "success",    "jobs": { "https://devel07.cnaf.infn.it:9000/9IU8sgB_T-882aqSR8_nAQ": { "endpoint": "https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server", "status": "cancel requested" } , "https://devel07.cnaf.infn.it:9000/_eixgfYvYWoCiZ21ER4vYw": { "endpoint": "https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server", "status": "cancel requested" } , "https://devel07.cnaf.infn.it:9000/fAJnQQPFMqrXT1xAFXVxxg": { "endpoint": "https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server", "status": "cancel requested" }    } } 
    [ale@cream-03 ~]$ glite-wms-job-status -v 0 --noint -i jobid 
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/9IU8sgB_T-882aqSR8_nAQ
    Current Status:     Cancelled 
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/_eixgfYvYWoCiZ21ER4vYw
    Current Status:     Aborted 
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/fAJnQQPFMqrXT1xAFXVxxg
    Current Status:     Cancelled 
    ==========================================================================
  • Cancel of multiple jobs using option --pretty-print:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --nomsg -o jobid test.jdl
    https://devel07.cnaf.infn.it:9000/PYxQsEgVrmHDD4IOqJj1jw
    [ale@cream-03 ~]$ glite-wms-job-submit -a --nomsg -o jobid test.jdl
    https://devel07.cnaf.infn.it:9000/brJPQT6fohm3K3lbZ-XDRg
    [ale@cream-03 ~]$ glite-wms-job-submit -a --nomsg -o jobid test.jdl
    https://devel07.cnaf.infn.it:9000/9tF8yxDrIKD8eUbSBcoXYg
    [ale@cream-03 ~]$ glite-wms-job-cancel --json --pretty-print --noint -i jobid 
    {
       result: success
       jobs: {
         https://devel07.cnaf.infn.it:9000/PYxQsEgVrmHDD4IOqJj1jw: {
           endpoint: https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
           status: cancel requested
         } 
         https://devel07.cnaf.infn.it:9000/brJPQT6fohm3K3lbZ-XDRg: {
           endpoint: https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
           status: cancel requested
         } 
         https://devel07.cnaf.infn.it:9000/9tF8yxDrIKD8eUbSBcoXYg: {
           endpoint: https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
           status: cancel requested
         } 
      }
    }
    
    [ale@cream-03 ~]$ glite-wms-job-status -v 0 --noint -i jobid 
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/PYxQsEgVrmHDD4IOqJj1jw
    Current Status:     Scheduled 
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/brJPQT6fohm3K3lbZ-XDRg
    Current Status:     Cancelled 
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/9tF8yxDrIKD8eUbSBcoXYg
    Current Status:     Cancelled 
    ==========================================================================
    
    
                               *** Log file created ***
    Possible Errors and Debug messages have been printed in the following file:
    /tmp/glite-wms-job-status_500_21640_1288713882.log
  • Cancel of a collection:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --nomsg --collection collection/
    https://devel07.cnaf.infn.it:9000/k3MKhhKFhvm1GcfLS5cwlA
    [ale@cream-03 ~]$ glite-wms-job-cancel --json https://devel07.cnaf.infn.it:9000/k3MKhhKFhvm1GcfLS5cwlA
    {    "result": "success",    "jobs": { "https://devel07.cnaf.infn.it:9000/k3MKhhKFhvm1GcfLS5cwlA": { "endpoint": "https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server", "status": "cancel requested" }    } } 
    [ale@cream-03 ~]$ glite-wms-job-status -v 0 https://devel07.cnaf.infn.it:9000/k3MKhhKFhvm1GcfLS5cwlA
    
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/k3MKhhKFhvm1GcfLS5cwlA
    Current Status:     Cancelled 
    - Nodes information for: 
        Status info for the Job : https://devel07.cnaf.infn.it:9000/9eL5KT1JxUG_eJVe9k4N4Q
        Current Status:     Cancelled 
        Status info for the Job : https://devel07.cnaf.infn.it:9000/vEyClv387UCVvDM2dM148Q
        Current Status:     Cancelled 
    ==========================================================================
  • Cancel of a collection with --pretty-print option:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --nomsg --collection collection/
    https://devel07.cnaf.infn.it:9000/pegAcMKjqXVbr1bp0auCLw
    [ale@cream-03 ~]$ glite-wms-job-cancel --json --pretty-print https://devel07.cnaf.infn.it:9000/pegAcMKjqXVbr1bp0auCLw
    {
       result: success
       jobs: {
         https://devel07.cnaf.infn.it:9000/pegAcMKjqXVbr1bp0auCLw: {
           endpoint: https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
           status: cancel requested
         } 
      }
    }
    
    [ale@cream-03 ~]$ glite-wms-job-status -v 0 https://devel07.cnaf.infn.it:9000/pegAcMKjqXVbr1bp0auCLw
    
    
    ======================= glite-wms-job-status Success =====================
    BOOKKEEPING INFORMATION:
    
    Status info for the Job : https://devel07.cnaf.infn.it:9000/pegAcMKjqXVbr1bp0auCLw
    Current Status:     Cleared 
    - Nodes information for: 
        Status info for the Job : https://devel07.cnaf.infn.it:9000/NbDqnxsx4h_qYLxZggvU_w
        Current Status:     Cancelled 
        Status info for the Job : https://devel07.cnaf.infn.it:9000/S0-KZuWnvjyiX5a90feA9g
        Current Status:     Cancelled 
    ==========================================================================
    

Bug #68786 : "InputSandboxBaseURI" JDL attribute work only in some circumstances... TO CHECK

Bug #69440 : json format of output isn't correct in glite-wms-job-submit FIXED

  • Submit a single job:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --json test.jdl 
    {"result": "success", "jobid": "https://devel07.cnaf.infn.it:9000/UU4KKhu4aX0FaeuOkv_BkA", "endpoint": "https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server"}
  • Submit a sinlge job using a human readble output format:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --pretty-print  --json test.jdl  
    {
      result: success
      jobid: https://devel07.cnaf.infn.it:9000/8ZQ5OPvhEZSJJWFirsYBOw
      endpoint: https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
    }
  • Submit a collection:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --json  --collection collection/
    {"result": "success", "parent": "https://devel07.cnaf.infn.it:9000/5Ny6EjvKg_LG8TmK7NT8rA", "endpoint": "https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server", "children": {"Node_test2_jdl": "https://devel07.cnaf.infn.it:9000/OoY60YLJ1pK0PcosZpj_PA", "Node_test_jdl": "https://devel07.cnaf.infn.it:9000/fzUsEBd6l2YR2gNfdDlTBg"}}
  • Submit a collection using a human readble output format:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --json --pretty-print --collection collection/
    {
      result: success
      parent: https://devel07.cnaf.infn.it:9000/HhuIuOxlwzh8kK6C66BdYw
      endpoint: https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
      children: {
          Node_test2_jdl: https://devel07.cnaf.infn.it:9000/8Fm1jPyKnerg6y4LcxhiUw
          Node_test_jdl: https://devel07.cnaf.infn.it:9000/onM_xsLVvkhQsFdc41Kddg
         }
    }
  • Submit a dag:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --json  dag.jdl 
    {"result": "success", "parent": "https://devel07.cnaf.infn.it:9000/4iw1HxQAyHPkunnKe1aEBw", "endpoint": "https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server", "children": {"nodeB": "https://devel07.cnaf.infn.it:9000/9dcTFYy6R04r7ZryVQP8bw", "nodeC": "https://devel07.cnaf.infn.it:9000/bKQKsvFMI6XYkkcJxaw-pw", "nodeA": "https://devel07.cnaf.infn.it:9000/Dgb54L4oGOlptBQVDEtsWQ"}}
  • Submit a dag using a human readble output format:
    [ale@cream-03 ~]$ glite-wms-job-submit -a --json --pretty-print dag.jdl 
    {
      result: success
      parent: https://devel07.cnaf.infn.it:9000/KTOaW_lu_fAafiR3FZ3GsA
      endpoint: https://devel14.cnaf.infn.it:7443/glite_wms_wmproxy_server
      children: {
          nodeB: https://devel07.cnaf.infn.it:9000/XZBKG1oLQbF89LdKRMldyQ
          nodeC: https://devel07.cnaf.infn.it:9000/l5lxlKRrdLVYr9QkK7VUvw
          nodeA: https://devel07.cnaf.infn.it:9000/HvE6OIOTTy871zYTh2f4pA
         }
    }

Bug #72675 : json format of output isn't correct in glite-wms-job-cancel FIXED

  • See tests on bug #68465

Bug #72870 : The UI does not check type mismatch for SMPGranularity, WholeNodes and HostNumber FIXED

  • To test this bug you need to install glite-jdl-api-cpp-3.2.4-2.sl5 on a WMS, then try a list-match or a submission with this jdl:
    [
    executable="/bin/sleep";
    arguments="$[$RANDOM%72]";
    wholenodes = "true";
    hostnumber = 4.3;
    smpgranularity = 2.2;
    ]
  • Check "wholenodes":
    [ale@cream-03 ~]$  glite-wms-job-submit -a -e https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server 72870.jdl 
    
    Connecting to the service https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server
    
    
    Warning - Unable to submit the job to the service: https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server
    WholeNodes: wrong type caught for attribute
    
    Method: jobSubmit
    
    
    Error - Operation failed
    Unable to find any endpoint where to perform service request
  • Check "smpgranularity":
    [ale@cream-03 ~]$  glite-wms-job-submit -a -e https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server 72870.jdl 
    
    Connecting to the service https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server
    
    
    Warning - Unable to submit the job to the service: https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server
    SMPGranularity: wrong type caught for attribute
    
    Method: jobSubmit
    
    
    Error - Operation failed
    Unable to find any endpoint where to perform service request
  • Check "HostNumber":
    [ale@cream-03 ~]$  glite-wms-job-submit -a -e https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server 72870.jdl 
    
    Connecting to the service https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server
    
    
    Warning - Unable to submit the job to the service: https://cream-44.pd.infn.it:7443/glite_wms_wmproxy_server
    HostNumber: wrong type caught for attribute
    
    Method: jobSubmit
    
    
    Error - Operation failed
    Unable to find any endpoint where to perform service request

Bug #73286 : glite-wms-job-status and glite-wms-job-logging info wrongly see a corrupted help file FIXED

  • glite-wms-job-status
[ale@cream-03 ~]$ glite-wms-job-status --help


glite-wms-job-status full help


        SYNOPSIS
glite-job-status [options] <jobId>

options:

        --version
        --help
        --config, -c <configfile>
        --debug
        --logfile <filepath>
        --noint
        --input, -i <filepath>
        --output, -o <filepath>
        --all
        --config-vo <configfile>
        --verbosity, -v <level>
        --from <[MM:DD:]hh:mm[:[CC]YY]>
        --to <[MM:DD:]hh:mm[:[CC]YY]>
        --user-tag <<tag name>=<tag value>>
        --status, -s <<status code>>
        --exclude, -e <<status code>>
        --nonodes


        DESCRIPTION

This command prints the status of a job previously submitted using glite-job-submit.
The job status request is sent to the LB that provides the requested information.
This can be done during the whole job life.
glite-job-status can monitor one or more jobs: the jobs to be checked are identified by one or more job identifiers (jobIds returned by glite-job-submit) provided as arguments to the command and separated by a blank space.

        OPTIONS

        --version
displays UI version.

   --help
displays command usage

   --config, -c <configfile>
if the command is launched with this option, the configuration file pointed by configfile is used. This option is meaningless when used together with "--vo" option

   --debug
When this option is specified, debugging information is displayed on the standard output and written into the log file, whose location is eventually printed on screen.
The default UI logfile location is:
glite-wms-job-<command_name>_<uid>_<pid>_<time>.log  located under the /var/tmp directory
please notice that this path can be overriden with the '--logfile' option

   --logfile <filepath>
when this option is specified, all information is written into the specified file pointed by filepath.
This option will override the default location of the logfile:
glite-wms-job-<command_name>_<uid>_<pid>_<time>.log  located under the /var/tmp directory

   --noint
if this option is specified, every interactive question to the user is skipped and the operation is continued (when possible)

   --input, -i <filepath>
Allow the user to select the JobId(s) from an input file located in filepath.
The list of jobIds contained in the file is displayed and the user is prompted for a choice. Single jobs can be selected specifying the numbers associated to the job identifiers separated by commas. E.g. selects the first,the third and the fifth jobId in the list.
Ranges can also be selected specifying ends separated by a dash. E.g. selects jobIds in the list from third position (included) to sixth position (included). It is worth mentioning that it is possible to select at the same time ranges and single jobs. E.g. selects the first job id in the list, the ids from the third to the fifth (ends included) and finally the eighth one.
When specified toghether with '--noint', all available JobId are selected.
This option cannot be used when one or more jobIds have been specified as extra command argument

   --output, -o <filepath>
writes the results of the operation in the file specified by filepath instead of the standard output. filepath can be either a simple name or an absolute path (on the submitting machine). In the former case the file filepath is created in the current working directory.

   --all
displays status information about all job owned by the user submitting the command. This option can't be used
either if one or more jobIds have been specified or if the --input option has been specified. All LBs
listed in the vo-specific UI configuration file $GLITE_WMS_LOCATION/etc/<vo_name>/glite_wmsui.conf are contacted to
fulfil this request.

   --config-vo <configfile>
if the command is launched with this option, the VO-specific configuration file pointed by configfile is used. This option is meaningless when used together with "--vo" option

   --verbosity, -v <level>
sets the detail level of information about the job displayed to the user. Possible values for verb_level are 0 (only JobId and status/event displayed),1 (timestamp and source information added), 2 (all information but jdls displayed), 3 (complete information containing all Jdl strings)

   --from <[MM:DD:]hh:mm[:[CC]YY]>
makes the command query LB for jobs that have been submitted (more precisely entered the "Submitted" status) after the specified date/time.
If only hours and minutes are specified then the current day is taken into account. If the year is not specified then the current year is taken into account.

   --to <[MM:DD:]hh:mm[:[CC]YY]>
makes the command query LB for jobs that have been submitted (more precisely entered the "Submitted" status) before the specified date/time.
If only hours and minutes are specified then the current day is taken into account.
If the year is not specified then the current year is taken into account.

   --user-tag <<tag name>=<tag value>>
makes the command include only jobs that have defined specified usertag name and value

   --status, -s <<status code>>
makes the command query LB for jobs that are in the specified status.
The status value can be either an integer or a (case insensitive) string; the following possible values are allowed:
UNDEF (0), SUBMITTED(1), WAITING(2), READY(3), SCHEDULED(4), RUNNING(5), DONE(6), CLEARED(7), ABORTED(8), CANCELLED(9),
UNKNOWN(10), PURGED(11).
This option can be repeated several times, all status conditions will be considered as in a logical OR operation

(i.e.  -s SUBMITTED --status 3  will query all jobs that are either in SUBMITTED or in READY status)

   --exclude, -e <<status code>>
makes the command query LB for jobs that are NOT in the specified status.
The status value can be either an integer or a (case insensitive) string; the following possible values are allowed:
UNDEF (0), SUBMITTED(1), WAITING(2), READY(3), SCHEDULED(4), RUNNING(5), DONE(6), CLEARED(7), ABORTED(8), CANCELLED(9),
UNKNOWN(10), PURGED(11).
This option can be repeated several times, all status conditions will be considered as in a logical AND operation

(i.e.  -e SUBMITTED --exclude 3  will query all jobs that are neither in SUBMITTED nor in READY status)

   --nonodes
This option will not display any information of (if present) sub jobs of any dag, only requested JobId(s) info will be taken into account


   ENVIRONMENT

GLITE_WMSUI_CONFIG_VAR:  This variable may be set to specify the path location of the custom default attribute configuration

GLITE_WMSUI_CONFIG_VO: This variable may be set to specify the path location of the VO-specific configuration file

GLITE_WMS_LOCATION:  This variable must be set when the Glite WMS installation is not located in the default paths: either /opt/glite or /usr/local

GLITE_LOCATION: This variable must be set when the Glite installation is not located in the default paths: either /opt/glite or /usr/local


GLOBUS_LOCATION: This variable must be set when the Globus installation is not located in the default path /opt/globus.
It is taken into account only by submission and get-output commands

GLOBUS_TCP_PORT_RANGE="<val min> <val max>" This variable must be set to define a range of ports to be used for inbound connections in the interactivity context.
It is taken into account only by submission of interactive jobs and attach commands

X509_CERT_DIR: This variable may be set to override the default location of the trusted certificates directory, which is normally /etc/grid-security/certificates.

X509_USER_PROXY: This variable may be set to override the default location of the user proxy credentials, which is normally /tmp/x509up_u<uid>.

   FILES

One of the following paths must exist (seeked with the specified order):
- $GLITE_WMS_LOCATION/etc/
- $GLITE_LOCATION/etc/
- /opt/glite/etc/
- /usr/local/etc/
- /etc/

and contain the following UI configuration files:
glite_wmsui_cmd_var.conf, glite_wmsui_cmd_err.conf, glite_wmsui_cmd_help.conf, <voName>/glite_wmsui.conf

- glite_wmsui_cmd_var.conf will contain custom configuration default values
A different configuration file may be specified either by using the --config option or by setting the GLITE_WMSUI_CONFIG_VAR environment variable
here follows a possible example:
[
RetryCount = 3 ;
ErrorStorage= "/tmp" ;
OutputStorage="/tmp";
ListenerStorage = "/tmp" ;
LoggingTimeout = 30 ;
LoggingSyncTimeout = 30 ;
NSLoggerLevel = 0;
DefaultStatusLevel = 1 ;
DefaultLogInfoLevel = 1;
]

- glite_wmsui_cmd_err.conf will contain UI exception mapping between error codes and error messages (no relocation possible)

- glite_wmsui_cmd_help.conf will contain UI long-help information (no relocation possible)

- <voName>/glite_wmsui.conf  will contain User VO-specific attributes.
A different configuration file may be specified either by using the --config-vo option or by setting the GLITE_WMSUI_CONFIG_VO environment variable
here follows a possible example:
[
LBAddresses = { "tigerman.cnaf.infn.it:9000" };
VirtualOrganisation = "egee";
NSAddresses = { "tigerman.cnaf.infn.it:7772" }
]

Besides those files, a valid proxy must be found inside the following path:
/tmp/x509up_u<uid> ( use the X509_USER_PROXY environment variable to override the default location JDL file)

   AUTHORS

Alessandro Maraschini (egee@datamat.it)
  • glite-wms-job-logging-info
[ale@cream-03 ~]$ glite-wms-job-logging-info --help


glite-wms-job-logging-info full help


   SYNOPSIS
glite-job-logging-info [options] <jobId>

options:

   --version
   --help
   --config, -c <configfile>
   --debug
   --logfile <filepath>
   --noint
   --input, -i <filepath>
   --output, -o <filepath>
   --config-vo <configfile>
   --verbosity, -v <level>
   --from <[MM:DD:]hh:mm[:[CC]YY]>
   --to <[MM:DD:]hh:mm[:[CC]YY]>
   --user-tag <<tag name>=<tag value>>
   --event <<event code>>
   --exclude, -e <<event code>>


   DESCRIPTION

This command queries the LB persistent DB for logging information about jobs previously submitted using glite-job-submit.
The job logging information are stored permanently by the LB service and can be retrieved also after the job has terminated its life-cycle, differently from the bookkeeping information that are in some way "consumed" by the user during the job existence.

   OPTIONS

   --version
displays UI version.

   --help
displays command usage

   --config, -c <configfile>
if the command is launched with this option, the configuration file pointed by configfile is used. This option is meaningless when used together with "--vo" option

   --debug
When this option is specified, debugging information is displayed on the standard output and written into the log file, whose location is eventually printed on screen.
The default UI logfile location is:
glite-wms-job-<command_name>_<uid>_<pid>_<time>.log  located under the /var/tmp directory
please notice that this path can be overriden with the '--logfile' option

   --logfile <filepath>
when this option is specified, all information is written into the specified file pointed by filepath.
This option will override the default location of the logfile:
glite-wms-job-<command_name>_<uid>_<pid>_<time>.log  located under the /var/tmp directory

   --noint
if this option is specified, every interactive question to the user is skipped and the operation is continued (when possible)

   --input, -i <filepath>
Allow the user to select the JobId(s) from an input file located in filepath.
The list of jobIds contained in the file is displayed and the user is prompted for a choice. Single jobs can be selected specifying the numbers associated to the job identifiers separated by commas. E.g. selects the first,the third and the fifth jobId in the list.
Ranges can also be selected specifying ends separated by a dash. E.g. selects jobIds in the list from third position (included) to sixth position (included). It is worth mentioning that it is possible to select at the same time ranges and single jobs. E.g. selects the first job id in the list, the ids from the third to the fifth (ends included) and finally the eighth one.
When specified toghether with '--noint', all available JobId are selected.
This option cannot be used when one or more jobIds have been specified as extra command argument

   --output, -o <filepath>
writes the results of the operation in the file specified by filepath instead of the standard output. filepath can be either a simple name or an absolute path (on the submitting machine). In the former case the file filepath is created in the current working directory.

   --config-vo <configfile>
if the command is launched with this option, the VO-specific configuration file pointed by configfile is used. This option is meaningless when used together with "--vo" option

   --verbosity, -v <level>
sets the detail level of information about the job displayed to the user. Possible values for verb_level are 0 (only JobId and status/event displayed),1 (timestamp and source information added), 2 (all information but jdls displayed), 3 (complete information containing all Jdl strings)

   --from <[MM:DD:]hh:mm[:[CC]YY]>
makes the command query LB for jobs that have been submitted (more precisely entered the "Submitted" status) after the specified date/time.
If only hours and minutes are specified then the current day is taken into account. If the year is not specified then the current year is taken into account.

   --to <[MM:DD:]hh:mm[:[CC]YY]>
makes the command query LB for jobs that have been submitted (more precisely entered the "Submitted" status) before the specified date/time.
If only hours and minutes are specified then the current day is taken into account.
If the year is not specified then the current year is taken into account.

   --user-tag <<tag name>=<tag value>>
makes the command include only jobs that have defined specified usertag name and value

   --event <<event code>>
makes the command query specified events for requested jobid(s)
The event code can be either an integer or a (case insensitive) string; the following possible values are allowed:
UNDEF, TRANSFER, ACCEPTED, REFUSED, ENQUEUED, DEQUEUED, HELPERCALL, HELPERRETURN, RUNNING, RESUBMISSION, DONE,
CANCEL, ABORT, CLEAR, PURGE, MATCH, PENDING, REGJOB, CHKPT, LISTENER, CURDESCR, USERTAG, CHANGEACL, NOTIFICATION,
RESOURCEUSAGE, REALLYRUNNING
This option can be repeated several times, all event conditions will be considered as in a logical OR operation

(i.e.  --event  PURGE --event 4  will query, for specified jobid(s), all PURGE and ENQUEUED events)

   --exclude, -e <<event code>>
makes the command exclude specified events for requested jobid(s)
The event code can be either an integer or a (case insensitive) string; the following possible values are allowed:
UNDEF, TRANSFER, ACCEPTED, REFUSED, ENQUEUED, DEQUEUED, HELPERCALL, HELPERRETURN, RUNNING, RESUBMISSION, DONE,
CANCEL, ABORT, CLEAR, PURGE, MATCH, PENDING, REGJOB, CHKPT, LISTENER, CURDESCR, USERTAG, CHANGEACL, NOTIFICATION,
RESOURCEUSAGE, REALLYRUNNING
This option can be repeated several times, all event conditions will be considered as in a logical AND operation

(i.e.  -e PURGE --exclude 4  will query, for specified jobid(s), all events BUT PURGE and ENQUEUED)


   ENVIRONMENT

GLITE_WMSUI_CONFIG_VAR:  This variable may be set to specify the path location of the custom default attribute configuration

GLITE_WMSUI_CONFIG_VO: This variable may be set to specify the path location of the VO-specific configuration file

GLITE_WMS_LOCATION:  This variable must be set when the Glite WMS installation is not located in the default paths: either /opt/glite or /usr/local

GLITE_LOCATION: This variable must be set when the Glite installation is not located in the default paths: either /opt/glite or /usr/local


GLOBUS_LOCATION: This variable must be set when the Globus installation is not located in the default path /opt/globus.
It is taken into account only by submission and get-output commands

GLOBUS_TCP_PORT_RANGE="<val min> <val max>" This variable must be set to define a range of ports to be used for inbound connections in the interactivity context.
It is taken into account only by submission of interactive jobs and attach commands

X509_CERT_DIR: This variable may be set to override the default location of the trusted certificates directory, which is normally /etc/grid-security/certificates.

X509_USER_PROXY: This variable may be set to override the default location of the user proxy credentials, which is normally /tmp/x509up_u<uid>.

   FILES

One of the following paths must exist (seeked with the specified order):
- $GLITE_WMS_LOCATION/etc/
- $GLITE_LOCATION/etc/
- /opt/glite/etc/
- /usr/local/etc/
- /etc/

and contain the following UI configuration files:
glite_wmsui_cmd_var.conf, glite_wmsui_cmd_err.conf, glite_wmsui_cmd_help.conf, <voName>/glite_wmsui.conf

- glite_wmsui_cmd_var.conf will contain custom configuration default values
A different configuration file may be specified either by using the --config option or by setting the GLITE_WMSUI_CONFIG_VAR environment variable
here follows a possible example:
[
RetryCount = 3 ;
ErrorStorage= "/tmp" ;
OutputStorage="/tmp";
ListenerStorage = "/tmp" ;
LoggingTimeout = 30 ;
LoggingSyncTimeout = 30 ;
NSLoggerLevel = 0;
DefaultStatusLevel = 1 ;
DefaultLogInfoLevel = 1;
]

- glite_wmsui_cmd_err.conf will contain UI exception mapping between error codes and error messages (no relocation possible)

- glite_wmsui_cmd_help.conf will contain UI long-help information (no relocation possible)

- <voName>/glite_wmsui.conf  will contain User VO-specific attributes.
A different configuration file may be specified either by using the --config-vo option or by setting the GLITE_WMSUI_CONFIG_VO environment variable
here follows a possible example:
[
LBAddresses = { "tigerman.cnaf.infn.it:9000" };
VirtualOrganisation = "egee";
NSAddresses = { "tigerman.cnaf.infn.it:7772" }
]

Besides those files, a valid proxy must be found inside the following path:
/tmp/x509up_u<uid> ( use the X509_USER_PROXY environment variable to override the default location JDL file)

   AUTHORS

Alessandro Maraschini (egee@datamat.it)

-- ElisabettaMolinari - 2010-07-06

Topic attachments
I Attachment Action Size Date Who Comment
Compressed Zip archivetgz TestUI-log.tgz manage 902.6 K 2010-10-29 - 14:54 AlessioGianelle Log files about UI test Suite
Texttxt update.txt manage 18.8 K 2010-11-03 - 16:15 AlessioGianelle Update log
Texttxt wms-cli-test_20101029165516.log.txt manage 50.7 K 2010-11-02 - 14:28 AlessioGianelle List match log
Texttxt wms-cli-test_20101029165550.log.txt manage 38.8 K 2010-11-02 - 14:29 AlessioGianelle Cancel log
Texttxt wms-cli-test_20101029165612.log.txt manage 37.6 K 2010-11-02 - 14:29 AlessioGianelle Delegation log
Texttxt wms-cli-test_20101029171518.log.txt manage 102.1 K 2010-11-02 - 14:30 AlessioGianelle Job info log
Texttxt wms-cli-test_20101029171641.log.txt manage 76.5 K 2010-11-02 - 14:30 AlessioGianelle Job output log
Texttxt wms-cli-test_20101029181932.log.txt manage 32.7 K 2010-11-02 - 14:31 AlessioGianelle Logging info log
Texttxt wms-cli-test_20101029182137.log.txt manage 11.2 K 2010-11-02 - 14:31 AlessioGianelle Job status log
Texttxt wms-cli-test_20101102111611.log.txt manage 103.2 K 2010-11-02 - 14:32 AlessioGianelle Job submission log
Texttxt wms-cli-test_20101102125222.log.txt manage 78.1 K 2010-11-02 - 14:32 AlessioGianelle Job perusal log
Texttxt wms-cli-test_20101102135418.log.txt manage 31.4 K 2010-11-02 - 14:33 AlessioGianelle Submission cycle
Edit | Attach | PDF | History: r33 < r32 < r31 < r30 < r29 | Backlinks | Raw View | More topic actions...
Topic revision: r30 - 2010-11-03 - AlessioGianelle
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback