Difference: WmsBugs3dot1dot100 (20 vs. 21)

Revision 212008-09-03 - AlessioGianelle

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"

glite_wms_R_3_1_100

WMPROXY - UI

Changed:
<
<
  • After two consecutive fails due to error System load is too high the glite_wms_job_submit command returns this error:
>
>
  • After two consecutive fails due to error System load is too high the glite_wms_job_submit command returns this error:
 
22 July 2008, 12:31:19 -I- PID: 16522 (Debug) - Calling the WMProxy delegationns__getProxyReq service
Line: 14 to 13
 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:delegationns="http://www.gridsite.org/namespaces/delegation-1" xmlns:ns1="http://glite.org/wms/wmproxy"><SOAP-ENV:Body>RSXb2eAtvje_8qidBLPN4g</SOAP-ENV:Body></SOAP-ENV:Envelope>
Changed:
<
<
  • If you try a job-info of a parametrics node, you receive an Aborted signal:
>
>
  • If you try a job-info of a parametrics node, you receive an Aborted signal:
 [ale@cream-15 src]$ glite-wms-job-info --jdl https://devel17.cnaf.infn.it:9000/xgTd_SELrAYKvwXShOuFXw terminate called after throwing an instance of 'glite::wms::wmproxyapi::BaseException*' Aborted
Changed:
<
<
  • Command glite-wms-job-info --jdl doesn't work with nodes of a collection #38689
>
>
  • Command glite-wms-job-info --jdl doesn't work with nodes of a collection #38689
 [ale@cream-15 UI]$ glite-wms-job-info --jdl https://devel17.cnaf.infn.it:9000/RAeQ1KgqrjHK4MYzB8t8Hw

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

Line: 36 to 32
 Method: getJDL
Changed:
<
<
  • Sometimes wmproxy returns this error message submitting a job:
>
>
  • Sometimes wmproxy returns this error message submitting a job:
 Connection failed: HTTP Error 500 Internal Server Error
Line: 57 to 52
 Error code: SOAP-ENV:Server
Changed:
<
<
  • I submit a job with a proxy of a VO which is not enabled on the WMS; the error message is not so clear:
>
>
  • I submit a job with a proxy of a VO which is not enabled on the WMS; the error message is not so clear:
 Warning - Unable to delegate the credential to the endpoint: https://devel19.cnaf.infn.it:7443/glite_wms_wmproxy_server Unknown Soap fault Method: Soap Error
Changed:
<
<
  • BUG #23443: NOT FIXED
    • Required documents are not put into the glite doc template in edms
    • For the R6 (JDL howto) document a broken link is given

  • BUG #39217. Submitting a "parametric" jobs it always failed with this error:
>
>
  • BUG #39217. Submitting a "parametric" jobs it always failed with this error:
 *********************************************************** BOOKKEEPING INFORMATION:
Line: 80 to 69
 ***********************************************************
Changed:
<
<
To help debugging:
>
>
To help debugging:
 27 Jun, 13:42:53 -D- PID: 5326 - "wmpgsoapoperations::ns1__jobStart": ------------------------------- Fault Description -------------------------------- 27 Jun, 13:42:53 -D- PID: 5326 - "wmpgsoapoperations::ns1__jobStart": Method: jobStart 27 Jun, 13:42:53 -D- PID: 5326 - "wmpgsoapoperations::ns1__jobStart": Code: 1502
Line: 96 to 83
 27 Jun, 13:42:53 -D- PID: 5326 - "wmpgsoapoperations::ns1__jobStart": ----------------------------------------------------------------------------------
Changed:
<
<
  • The status of a collection (or a dag) is corretly set to CLEARED after a "glite-wms-get-output", but its nodes remain in "Done (Success)" status.
>
>
  • The status of a collection (or a dag) is corretly set to CLEARED after a "glite-wms-get-output", but its nodes remain in "Done (Success)" status. (Bug #40951)
 *********************************************************** BOOKKEEPING INFORMATION:
Line: 130 to 116
 ***********************************************************
Changed:
<
<
  • One collection over 60 submissions remains in "Waiting" status due to a LB problem (its nodes are in status "Submitted"); this are the wmproxy logs:
 
>
>
  • One collection over 60 submissions remains in "Waiting" status due to a LB problem (its nodes are in status "Submitted"); this are the wmproxy logs: (Bug #40982)
     
 23 Jun, 18:58:18 -D- PID: 24834 - "WMPEventlogger::isAborted": Quering LB Proxy... 23 Jun, 18:58:18 -D- PID: 24834 - "WMPEventlogger::isAborted": LBProxy is enabled Unable to query LB and LBProxy
Line: 151 to 136
 23 Jun, 18:58:19 -I- PID: 24834 - "wmproxy::main": ----------------------------------------
Changed:
<
<
  • There is this warning in wmproxy submitting collections:
>
>
  • There is this warning in wmproxy submitting collections:
 19 Jun, 14:58:32 -W- PID: 2746 - "wmpcoreoperations::submit": Unable to find SDJRequirements in configuration file
Changed:
<
<
  • Fond a problem in the wmproxy. After some collections submissions it stops working and with the top command you can see that the glite-wms-proxy processes are using all the CPU (It seems that the problem is related with the porting to gsoap 2.7.10):
>
>
  • Fond a problem in the wmproxy. After some collections submissions it stops working and with the top command you can see that the glite-wms-proxy processes are using all the CPU (It seems that the problem is related with the porting to gsoap 2.7.10):
 [Thu Jun 19 15:43:50 2008] [warn] FastCGI: (dynamic) server "/opt/glite/bin/glite_wms_wmproxy_server" (pid 7938) terminated due to uncaught signal '11' (Segmentation fault)

WM

Changed:
<
<
  • If a job is in the WM's queue:
>
>
  • If a job is in the WM's queue:
 *********************************************************** BOOKKEEPING INFORMATION:
Line: 175 to 157
 ***********************************************************
Changed:
<
<
it is not possible to cancel it:
>
>
it is not possible to cancel it:
 ******************************************************************** LOGGING INFORMATION:
Line: 229 to 209
 ********************************************************************
Changed:
<
<
  • If you remove a pending node the request is not removed from the "old" directory of the jobdir:
>
>
  • If you remove a pending node the request is not removed from the "old" directory of the jobdir:
 /var/glite/workload_manager/jobdir/old: total 16 -rw-r--r-- 1 glite glite 250 Jul 9 13:37 20080709T113710.627592_3086920576
Line: 246 to 225
 
  • BUG #38509: The WM's recovery procedure hangs if no relevant events are found for a given request
Changed:
<
<
  • BUG #38366: Recovery doesn't work with a list-match request. FIXED
>
>
  • BUG #38366: Recovery doesn't work with a list-match request. FIXED
 25 Jun, 15:31:50 -I: [Info] operator()(dispatcher.cpp:754): Dispatcher: starting 25 Jun, 15:31:50 -I: [Info] operator()(dispatcher.cpp:757): Dispatcher: doing recovery 25 Jun, 15:31:50 -I: [Info] operator()(RequestHandler.cpp:389): RequestHandler: starting
Line: 282 to 260
 
  • Bug #39308
    • Remove "rgma" fron the enviroment variable GLITE_SD_PLUGIN
    • Add "globus gridftp" at the gliteservices list (gLiteservices)
Changed:
<
<
    • Modify the cron purger file
>
>
    • Modify the cron purger file
 # Execute the 'purger' command at every day except on Sunday with a frequency of six hours 3 */6 * * mon-sat glite . /opt/glite/etc/profile.d/grid-env.sh ; /opt/glite/sbin/glite-wms-purgeStorage.sh -l /var/log/glite/glite-wms-purgeStorage.log -p /var/glite/SandboxDir -t 604800 > /dev/null 2>&1
Line: 295 to 272
 
    • Remove IsmBlackList parameter
    • Set jobdir as the default for the DispatcherType parameter of wm
    • Add the parameter EnableRecovery = true; ti the wm configuration section
Changed:
<
<
    • Add this cron to create the host proxy:
>
>
    • Add this cron to create the host proxy:
 0 */6 * * * glite . /opt/glite/etc/profile.d/grid-env.sh ; /opt/glite/sbin/glite-wms-create-proxy.sh /var/glite/wms.proxy /var/log/glite/create_proxy.log
    • Rotate the logs of the purgeStorage
Line: 313 to 289
 
  • BUG #39215
    • If you use in the cron-purger the option -n, no check is done against option -t: e.g. nodes are purged also if they are in running state
Changed:
<
<
    • On script glite-wms-purgeStorage.sh the command glite-wms-create-proxy.sh has to be called with its path:
>
>
    • On script glite-wms-purgeStorage.sh the command glite-wms-create-proxy.sh has to be called with its path:
 [glite@devel19 ~]$ /opt/glite/sbin/glite-wms-purgeStorage.sh -l /var/log/glite/glite-wms-purgeStorage.log -p /var/glite/SandboxDir -t 302400 Certificate will expire /opt/glite/sbin/glite-wms-purgeStorage.sh: line 27: glite-wms-create-proxy.sh: command not found
Changed:
<
<
    • Probably on /opt/glite/sbin/glite-wms-create-proxy.sh it is better to use the --force option for command mv, instead the move commands should be blocked here:
>
>
    • Probably on /opt/glite/sbin/glite-wms-create-proxy.sh it is better to use the --force option for command mv, instead the move commands should be blocked here:
 [glite@devel19 ~]$ mv /var/glite/wms.proxy.14913 /var/glite/wms.proxy mv: overwrite `/var/glite/wms.proxy', overriding mode 0400?
Changed:
<
<
>
>
  • Bug #40967: Problems in script glite_wms_wmproxy_load_monitor
 
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback