gLite > gLite 3.1 > glite-MON > Update to glite-MON 3.1.1-0  
 
 

 

 

gLite 3.1

glite-MON - Update to version 3.1.1-0


Date 07.04.08
Priority Normal

Description

glite-MON

This update introduces the gLite 3.1 monitoring system collector server (glite-MON).

Configuration

Update for glite 3.1 redundant configuration steps have been removed and there is the addition of 2 new variables in yaim/defaults/glite-mon.pre:
  • APEL_PUBLISH_USER_DN If it is set to yes, it will enable UserDN encryption. The default is no. The config_apel_rgma function has been modified to be able to set up the new variable in the configuration file of the APEL publisher.
  • GIN_BDII If this is set to yes it will configure GIN to use the site BDII to populate the Glue tables in R-GMA. If set to no it will use the fmon to populate the tables. Default is yes.
RGMA_HOME is set in the CATALINA_OPTS and is for future use when it is removed from the web.xml configuration file supplied with the server war file. Also added -Dsun.net.inetaddr.ttl=1800 which alters the DNS caching behaviour of the server. Currently the DNS lookups are disabled by default for java applications this parameter sets the caching time to 30 mins and will mean that services do not need to be restarted when DNS changes are made they will automatically pick these up when they have been propagated to local DNS servers.

The yaim.mon configuration now configures gip and bdii - there has been a script added in cron for a service proxy for dymanic gip script. The reliance on the trustmanager configuration script has been removed as this has a bug in it and does not set classpaths correctly. The apel configuration works around incorrectly set classpaths for bcprov and log4j in the apel provider scripts. See the bug:

http://savannah.cern.ch/bugs/?32661

Addition of new variable in yaim/defaults/glite-mon.pre:
MYSQL_REMOTE_USER with the default as "root" this is used if the mysql server is located remotely. Can be overridden in site-info.def.

Addition of new variable in yaim/defaults/glite-mon.pre:
MYSQL_HOST with the default as "localhost" This is the location of the mysql server. Can be overridden in site-info.def.

glite-yaim-mon now checks to see if mysql is installed locally before attempting to configure it. If it is not installed locally it will attempt to configure the server remotely.

glite-MON meta package has not dependency on MySQL rpm packages any more since MySQL server is not necessary the same node as RGMA server. In case that you install MySQL server on the same node, you need to install MySQL rpm packages by hand.

If /etc/init.d/mysqld fails to start on MON server, it is necessary to modify /etc/my.cnf configuration file:
[mysqld]
...
...
# set skip-bdb=1 for /etc/init.d/mysql service
skip-bdb=1
...
Known Issue

Please note the following known issue:
https://savannah.cern.ch/bugs/?34436


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
 #24641 LD_ASSUME_KERNEL no longer needed
 #31015 YAIM should configure UserDN and FQAN processing in APEL
 #33501 yaim-mon attempts to start mysql even if it is not insatalled

Updated rpms

Name Version Full RPM name Description
bdii 3.9.1-5 bdii-3.9.1-5.noarch.rpm bdii
fetch-crl 2.6.3-1 fetch-crl-2.6.3-1.noarch.rpm Tool for periodic retrieval of Certificate Revocation Lists
glite-MON 3.1.1-0 glite-MON-3.1.1-0.i386.rpm gLite metapackage (glite-MON)
glite-apel-core 2.0.9-7 glite-apel-core-2.0.9-7.noarch.rpm Core components of the Apel accounting application
glite-apel-publisher 2.0.9-3 glite-apel-publisher-2.0.9-3.noarch.rpm Apel account record publisher
glite-info-generic 2.0.2-3 glite-info-generic-2.0.2-3.noarch.rpm glite-info-generic
glite-info-templates 1.0.0-8 glite-info-templates-1.0.0-8.noarch.rpm glite-info-templates
glite-rgma-api-java 5.0.5-3 glite-rgma-api-java-5.0.5-3.noarch.rpm org.glite.rgma.api-java v. 5.0.5
glite-rgma-api-python 5.0.12-3 glite-rgma-api-python-5.0.12-3.noarch.rpm org.glite.rgma.api-python v. 5.0.12
glite-rgma-base 5.0.7-1 glite-rgma-base-5.0.7-1.noarch.rpm R-GMA basic configuration and documentation
glite-rgma-command-line 5.0.5-2 glite-rgma-command-line-5.0.5-2.noarch.rpm org.glite.rgma.command-line v. 5.0.5
glite-rgma-flexible-archiver 5.0.3-1 glite-rgma-flexible-archiver-5.0.3-1.noarch.rpm org.glite.rgma.flexible-archiver v. 5.0.3
glite-rgma-gin 5.0.11-2 glite-rgma-gin-5.0.11-2.noarch.rpm R-GMA Gin
glite-rgma-glue-archiver 5.0.7-2 glite-rgma-glue-archiver-5.0.7-2.noarch.rpm org.glite.rgma.glue-archiver v. 5.0.7
glite-rgma-server-servlet 5.0.49-1 glite-rgma-server-servlet-5.0.49-1.noarch.rpm Servlet-based R-GMA server implementation
glite-rgma-servicetool 5.0.5-1 glite-rgma-servicetool-5.0.5-1.noarch.rpm R-GMA service tool
glite-rgma-standard-tables 5.0.6-1 glite-rgma-standard-tables-5.0.6-1.noarch.rpm A set of standard table schemas for R-GMA
glite-rgma-stubs-servlet-java 5.0.10-2 glite-rgma-stubs-servlet-java-5.0.10-2.noarch.rpm org.glite.rgma.stubs-servlet-java v. 5.0.10 NO-GLITE BUILD VERSION
glite-security-trustmanager 1.8.15-1 glite-security-trustmanager-1.8.15-1.noarch.rpm org.glite.security.trustmanager v. 1.8.15-1
glite-security-util-java 1.4.0-1 glite-security-util-java-1.4.0-1.noarch.rpm org.glite.security.util-java v. 1.4.0-1
glite-version 3.1.0-1.slc4 glite-version-3.1.0-1.slc4.i386.rpm glite-version
glite-yaim-core 4.0.3-13 glite-yaim-core-4.0.3-13.noarch.rpm glite-yaim-core
glite-yaim-mon 4.0.2-6 glite-yaim-mon-4.0.2-6.noarch.rpm glite-yaim-mon is the module that configures the 3.1 RGMA.
glue-schema 1.3.0-3 glue-schema-1.3.0-3.noarch.rpm glue-schema
lcg-service-proxy 1.0.3-2 lcg-service-proxy-1.0.3-2.noarch.rpm LCG Service Proxy
vdt_globus_essentials VDT1.6.1x86_rhas_4-6 vdt_globus_essentials-VDT1.6.1x86_rhas_4-6.i386.rpm Virtual Data Toolkit

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

Service restart after update

Service must be restarted.

How to apply the fix

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