Version glite_wms_R_3_1_100

2008-06-24 (Ale)

• The status of a collection is corretly set to CLEARED after a "glite-wms-get-output", but its nodes remain in "Done (Success)" status.
• One collection over 60 submissions remain in "Waiting" status due to a LB problem (its nodes are in status "Submitted"); this are the wmproxy logs:

 
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
edg_wll_QueryEvents[Proxy]
Exit code: 4
LB[Proxy] Error: Interrupted system call
(edg_wll_plain_read())
23 Jun, 18:58:18 -D- PID: 24834 - "wmpcoreoperations::jobStart": Logging LOG_ENQUEUE_FAIL
23 Jun, 18:58:18 -D- PID: 24834 - "WMPEventlogger::logEvent": Logging to LB Proxy...
23 Jun, 18:58:18 -D- PID: 24834 - "WMPEventlogger::logEvent": Logging Enqueue FAIL event...
23 Jun, 18:58:19 -D- PID: 24834 - "WMPEventlogger::testAndLog": LB call succeeded
23 Jun, 18:58:19 -D- PID: 24834 - "wmpcoreoperations::jobStart": Removing lock...
23 Jun, 18:58:19 -I- PID: 24834 - "wmpgsoapoperations::ns1__jobStart": jobStart operation completed

23 Jun, 18:58:19 -I- PID: 24834 - "wmproxy::main": -------- Exiting Server Instance -------
23 Jun, 18:58:19 -I- PID: 24834 - "wmproxy::main": Signal code received: 15
23 Jun, 18:58:19 -I- PID: 24834 - "wmproxy::main": ----------------------------------------

2008-06-20 (Ale)

• 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

• 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 process aer using all the CPU:

[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)

2008-06-19 (Ale)

• Add glite-wms-ice at the metapackage dependencies
• Remove "rgma" fron the enviroment variable GLITE_SD_PLUGIN
• Add "globus gridftp" at the gliteservices list (gLiteservices)
• Remove from the metapackage these rpms:
  • checkpointing
  • partitioner
  • interactive (and thirdparty-bypass)
  • rgma-* (and service-discovery-rgma-c)
• glite-lb-interlogd doesn't stop (you need a "kill -9")
• 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

# Execute the 'purger' command on each Sunday (sun) forcing removal of dag nodes,
# orphan dag nodes without performing any status checking (threshold of 2 weeks).
0 1 * * sun 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 -o -s -n -t 1296000 > /dev/null 2>&1

• Set the ICE configuration section
• Remove IsmBlackList parameter
• Set jobdir as the default for the DispatcherType parameter of wm
• Add the parameter EnableRecovery = true; ti the wm configuration section
• 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

-- AlessioGianelle - 20 Jun 2008