gLite > gLite 3.1 > glite-TORQUE_utils > Update to glite-TORQUE_utils 3.1.10-0  
 
 

 

 

gLite 3.1

glite-TORQUE_utils - Update to version 3.1.10-0


Date 31.08.2009
Priority Normal

Description



glite-MON, lcg-CE, glite-TORQUE_utils, glite-CONDOR_utils, glite-SGE_utils, glite-LSF_utils, glite-CREAM

APEL upgrade
When applying this new release, sites should make sure that the APEL publisher XML configuration file contains the new variable Limit (see example configuration file included with the code).The main fixes are:
  • Publisher OutOfMemory error when publishing large amounts of records. APEL will now publish records in batches instead of selecting all records in one go. However, there is still an out of memory error when processing large numbers of grid_jobmap files. In that case, follow this recipe.
  • The value for the ExecutingCE in the accounting records will be taken from the configuration file in each CE and not from the log files, which will stop sites having records with the hostname for the scheduler.
  • APEL database schema changes. Some of the fields in the APEL local database have been changed. The APEL parser needs to be run at least once with the following setting enabled to have the changes applied: <DBProcessor inspectTables="yes"/>
  • YAIM changes:
    • There's a new variable APEL_PUBLISH_LIMIT, in order to be able to configure the number of records to be selected. Default value is 300000.
    • A number of outstanding YAIM bugs have been addressed.
    • The configuration no longer attempts to fix problems in the tomcat installation as this code was rather fragile. According to the precise version of tomcat you may need to set JAVA_HOME yourself in the /etc/tomcat/tomcat5.conf file.
    • YAIM no longer assumes that you have one tomcat service called tomcat5. You can set the YAIM variable TOMCAT_SERVICE if needed. It defaults to "tomcat5". The corresponding entry in /etc/sysconfig is modified.
    • ulimit is no longer set by modifying /etc/init.d/rc.d/tomcat5 but is set by a line at the end of the /etc/sysconfig/ file. This file is sourced by the init.d script.
    • YAIM sets up the glite-info-provider-service to make the R-GMA status available via the BDII.
    • There is an known problem with the version of urllib used by the MON gip plugins, where the provider does not return the correct information in the case where the site uses a HTTP proxy. The problem is due to an issue in the OS vendor supplied urllib. A workaround, which requires a minor modification to YAIM /opt/glite/yaim/functions/config_info_service_mon. This fix unsets the https_proxy variable for the duration of running the GIP scripts. Full details may be found in Bug 40764.
glite-AMGA_oracle, glite-AMGA_postgres, glite-BDII, glite-CONDOR_utils, glite-CREAM, glite-FTA_oracle, glite-FTM, glite-FTS_oracle, glite-HYDRA_mysql, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-LSF_utils, glite-MON, glite-MPI_utils, glite-PX, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dcache_pool, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-SGE_utils, glite-TORQUE_client, glite-TORQUE_server, glite-TORQUE_utils, glite-UI, glite-VOBOX, glite-WMS, glite-WN, lcg-CE

New version of yaim core
  • Configuration changes needed for a new version of trustmanager and util-java. These changes are included in a new function not used yet by any yaim module. The idea is that any service configuring tomcat will use this function in the future.
  • The creation of users specifying a home directory wasn't working. This is fixed now.
  • GLOBUS_TCP_PORT_RANGE is not defined for the WN and it's properly defined for the TAR UI. MYPROXY_TCP_PORT_RANGE is not defined any more.
  • YAIM checks whether fetch-crl is installed and fails otherwise.
  • groups.d/ structure is now available for all the node types.
  • gridview is configured only if it's installed.
  • The verify-proxy plugin is not present in the lcmaps configuration for gridftp.
  • /opt/edg/var/info directories for the software tags are again created by yaim.
  • New site-info.pre and .post variables:
    • BDII_ARCHIVE_SIZE: It is the number of dumps of the database to keep for debugging purposes. Default is 0.
    • BDII_BREATHE_TIME: It is the time in seconds between updates of the bdii. Default is 120.
    • BDII_PASSWD: This is the password for the LDAP database used by the bdii. Default is $(mkpasswd -s 0).
    • BDII_READ_TIMEOUT: It is the amount of time to wait until an information is assumed to have timed out. Default is 300.
    • CONFIG_GRIDMAPDIR: It enables or disables the creation of the gridmap file. If set to yes, it creates it. If set to no, it doesn't create the gridmap file. Default is yes.
    • TRUSTMANAGER_CRL_UPDATE_INTERVAL: This variable is used in the trustmanager configuration and it defines how often the X509_CERT_DIR is polled for changes in the files. It's a number followed by h,m or s time units. Default is 2h.
    • TOMCAT_HOSTCERT_LOCATION: path of the tomcat host certificate. Default is /etc/grid-security/tomcat-cert.pem.
    • TOMCAT_HOSTKEY_LOCATION: path of the tomcat host key. Default is /etc/grid-security/tomcat-key.pem.
    • TOMCAT_USER: tomcat user. Default is "tomcat".


Please also have a look at the list of known issues.

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #27375 Apel Encryption
 #29962 apel uses (hardcoded ?) /tmp temporary directory for SQL queries
 #32435 apel infinite loop when archiver is dead
 #33664 SubmitHost in EventRecords table not taken from configuration file
 #33909 [ yaim-core ] Add configurable timeouts to the BDII
 #33936 [ YAIM ] remove JAVA_HOME definition
 #34506 APEL publisher OutOfMemory error
 #35253 APEL doesn't parser message log files with format message.100
 #36860 APEL OutOfMemory exception in parser when parsing too many message files
 #36879 Out of date apel-schema.sql DB conf with glite-apel-core-2.0.9-8
 #37895 [ YAIM ] RGMA should stop using JAVA_HOME and JAVA_LOCATION
 #39692 [ yaim-mon ] YAIM version for yaim mon
 #39805 config-rgma-server does not set ulimit in latest tomcat5 init.d script
 #40208 [ YAIM ] LCG_GFAL_INFOSYS variable is defined in two places
 #40764 [ yaim-mon ] Implement config_info_service_mon
 #43985 [ yaim-mon ] YAIM packages
 #44820 [ yaim-core ] The lcg-cp parallel data transfer failed on UI_TAR installed gLite-UI 3.1 nodes
 #45269 [ yaim-core ] yaim only recognizes the groups.d dir structure for a restrict set of nodes
 #45418 [ yaim-core ] Check grid-env.sh exists if -r option is used
 #46194 [ yaim-core ] YAIM config_crl should check for /usr/sbin/fetch-crl
 #46369 [ yaim-core ] Remove verify-proxy from lcmaps config file for gridftp
 #48206 [ yaim-core ] YAIM defines a default for JAVA_LOCATION
 #48452 [ yaim-core ] WN should not define GLOBUS_TCP_PORT_RANGE
 #48932 [ yaim-core] output is not helpful when a conf target is wrongly stated
 #48991 [ yaim-core ] needed to change config_edgusers
 #49017 [ yaim-core ] configuration changes for new trustmanager and util-java
 #49464 [ yaim-core ] configure gridview only if it's installed
 #49575 [ yaim-core ] MYPROXY_TCP_PORT_RANGE can be deleted
 #49803 [ glite-yaim-core ] objectClass 'GlueTop' not allowed
 #49831 [ yaim-core ] /opt/edg/var/info should still be created by YAIM
 #50735 [ yaim-core ] queue_GROUP_ENABLE fails for "/vo" FQAN
 #52885 bug in config_gip_vo_tag of glite-yaim-core-4.0.7-9

Updated rpms

Name Version Full RPM name Description
glite-TORQUE_utils 3.1.10-0 glite-TORQUE_utils-3.1.10-0.i386.rpm gLite metapackage (glite-TORQUE_utils)
glite-apel-core 2.0.9-13 glite-apel-core-2.0.9-13.noarch.rpm Core components of the Apel accounting application
glite-apel-pbs 2.0.5-4 glite-apel-pbs-2.0.5-4.noarch.rpm PBS log parser plugin
glite-yaim-core 4.0.8-7 glite-yaim-core-4.0.8-7.noarch.rpm YAIM core package

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Not needed.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)