Difference: CreamCliP3671 (11 vs. 12)

Revision 122010-04-08 - AlessioGianelle

Line: 1 to 1
 
Line: 115 to 115
 Status = [RUNNING] Service Property = [cemon_url]->[https://cream-38.pd.infn.it:8443/ce-monitor/services/CEMonitor]
Changed:
<
<
  • Bug #58784 CREAM CLI: possible problem when there is a wildcard in InputSandbox NOT TESTED

  • Bug #59063 ICE can fail to start due to socket bind error NOT TESTED
>
>
  • Bug #58784 CREAM CLI: possible problem when there is a wildcard in InputSandbox FIXED
    • Submit this JDL:
      [ale@egee-rb-03 CREAM-cli]$ cat example.jdl 
      [
      JobType = "Normal";
      Executable = "/bin/sleep";
      InputSandBox = "CVS/*";
      Arguments = "30";
      StdOuput="out.txt";
      StdError="err.txt";
      ]
      [ale@egee-rb-03 CREAM-cli]$ ls CVS/
      Entries  Repository  Root  Template
    • Verify on the CE the InputSandBox dir of the job:
      [root@cream-20 CREAM505718957]# ls -l ISB/
      total 12
      -rw-r--r-- 1 dteam004 dteam 999 Apr  8 16:16 Entries
      -rw-r--r-- 1 dteam004 dteam  41 Apr  8 16:16 Repository
      -rw-r--r-- 1 dteam004 dteam  45 Apr  8 16:16 Root
      -rw-r--r-- 1 dteam004 dteam   0 Apr  8 16:16 Template

  • Bug #59063 ICE can fail to start due to socket bind error FIXED
    • Start a first glite-ce-monitor-consumer:
      [ale@egee-rb-03 ~]$ glite-ce-monitor-consumer 56655
      Socket connection successful on port 56655 master socket 3
      Accepting connection ... 
    • And then a second one on the same port:
      [ale@egee-rb-03 ~]$ glite-ce-monitor-consumer 56655
      error message=Address already in use
      error code   =SOAP-ENV:Server
      Retrying in 5 seconds...
      error message=Address already in use
      error code   =SOAP-ENV:Server
      Retrying in 5 seconds...
      error message=Address already in use
      error code   =SOAP-ENV:Server
      Retrying in 5 seconds...
      error message=Address already in use
      error code   =SOAP-ENV:Server
      Retrying in 5 seconds...
 
  • Bug #60381 Problem in proxy time left calculation when VOMS extensions expire before proxy FIXED
    [ale@egee-rb-03 CREAM-cli]$ voms-proxy-info -all
Line: 162 to 199
  ]
Changed:
<
<
  • Bug #61437 bug in expiration proxy validation in cream-client-api-c NOT TESTED
>
>
  • Bug #61437 bug in expiration proxy validation in cream-client-api-c Internal fix
 
  • Bug #61523 Problem in proxy expiration detection in cream-client-api-c FIXED
    [ale@egee-rb-03 CREAM-cli]$ voms-proxy-info -all
Line: 185 to 222
 [ale@egee-rb-03 CREAM-cli]$ glite-ce-job-submit -a -r devel05.cnaf.infn.it:8443/cream-pbs-creamtest1 example.jdl 2010-03-18 11:02:16,225 FATAL - Problems with proxyfile [/tmp/x509up_u500]: The proxy is EXPIRED!
Changed:
<
<
  • Bug #61894 Bad string name mapping for REALLY-RUNNING status in CREAM client API C++ NOT TESTED
>
>
  • Bug #61894 Bad string name mapping for REALLY-RUNNING status in CREAM client API C++ Internal fix
 
  • Bug #62066 A better check of proxy file existance is needed in the CREAM Client C++ API FIXED
    [ale@egee-rb-03 CREAM-cli]$ rm /tmp/x509up_u500 
 
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