Known issues in yaim core 4.0.5-7

  • The yaim version of the different yaim modules installed in a host will be missing until all the yaim modules are updated to implement the version mechanism. Moreover, there's a typo in yaim core and because of this reason only the yaim core version is currently printed.
  • Bug #40093: groups.conf per VO can't be used when the TORQUE server is installed in a separated host.
  • Bug #40092: YAIM exits with an error if debug level 7 is used.
  • Bug #40095: Affecting DPM. config_edgusers should be executed before config_mkgridmap since now the dpmmgr group used by config_mkgridmap is created in config_edgusers.
  • Affecting the site BDII. Everytime a site BDII is reconfigured, the bdii daemon fails with this error:
cat /opt/bdii/var/bdii.log
...
Error for mkdir /var/glite/tmp: Permission denied at /opt/glite/libexec/glite-info-provider-ldap line 86
...
And the site BDII doesn't publish anything. We think it can be related to the value of GLITE_LOCATION when this script is excuted. It seems the variable is defined but empty and this causes this funny error. We haven't been able to detect the real problem so far. The workaround is to restart the site BDII.

  • groups.conf per VO can't be used in the glexec WN. If you are installing a glexec WN, please define groups.conf as usual.
  • Bug #39022: affecting BDII. BDII_USER should always be the default 'edguser' for the time being until the mentioned bug is fixed.
  • Bug #39884: affecting BDII. INFOSYS_GROUP and BDII_GROUP conflict since they have the same gid in edgusers.conf.
  • Bug #39254: affecting WMS. The LCG VOMS host certificates rpm needs to be installed in the WMS. If you are planning to use only lsc files, you'll find the mentioned bug.

Known issues in yaim core 4.0.5-6

  • Affecting DPM. config_edgusers should be executed before config_mkgridmap since now the dpmmgr group used by config_mkgridmap is created in config_edgusers.
  • Affecting the site BDII. Everytime a site BDII is reconfigured, the bdii daemon fails with this error:
cat /opt/bdii/var/bdii.log
...
Error for mkdir /var/glite/tmp: Permission denied at /opt/glite/libexec/glite-info-provider-ldap line 86
...
And the site BDII doesn't publish anything. We think it can be related to the value of GLITE_LOCATION when this script is excuted. It seems the variable is defined but empty and this causes this funny error. We haven't been able to detect the real problem so far. The workaround is to restart the site BDII.

  • groups.conf per VO can't be used in the glexec WN. If you are installing a glexec WN, please define groups.conf as usual.
  • Bug #39022: affecting BDII. BDII_USER should always be the default 'edguser' for the time being until the mentioned bug is fixed.
  • Bug #39254: affecting WMS. The LCG VOMS host certificates rpm needs to be installed in the WMS. If you are planning to use only lsc files, you'll find the mentioned bug.

Known issues in yaim core 4.0.5-5

  • Affecting LFC_mysql. There's a typo in start_mysql utility. There's a "/" missing.

  • Affecting the TAR UI. Since the variable X509_CERT_DIR is now defined by default in yaim core, the TAR UI doesn't properly implement the certificates mechanism anymore. We have therefore realised that X509_CERT_DIR should be /etc/grid-security/certificates by default instead of the current ${GRID_EXTERNAL_ROOT}/etc/grid-security/certificates. The mechanism changes slightly anyway and we will document this properly in the TAR UI installation notes. No rpm is going to be regenerated for this at this moment since this is a very specific problem affecting only the TAR UI. This will be done at the end of the certification process if no other major issues are found. Moreover this variable should be defined in site-info.pre instead of site-info.post.

  • Affecting the site BDII. Everytime a site BDII is reconfigured, the bdii daemon fails with this error:
cat /opt/bdii/var/bdii.log
...
Error for mkdir /var/glite/tmp: Permission denied at /opt/glite/libexec/glite-info-provider-ldap line 86
...
And the site BDII doesn't publish anything. We think it can be related to the value of GLITE_LOCATION when this script is excuted. It seems the variable is defined but empty and this causes this funny error. We haven't been able to detect the real problem so far. The workaround is to restart the site BDII.

  • group.d/ defining the groups.conf per VO can't be used in the glexec WN. If you are installing a glexec WN, please define groups.conf as usual.
  • Bug #39022: affecting BDII. BDII_USER should always be the default 'edguser' for the time being until the mentioned bug is fixed.
  • Bug #39254: affecting WMS. The LCG VOMS host certificates rpm needs to be installed in the WMS. If you are planning to use only lsc files, you'll find the mentioned bug.

Known issues in yaim core 4.0.5-3

  • Affecting the site BDII. Everytime a site BDII is reconfigured, the bdii daemon fails with this error:
cat /opt/bdii/var/bdii.log
...
Error for mkdir /var/glite/tmp: Permission denied at /opt/glite/libexec/glite-info-provider-ldap line 86
...
And the site BDII doesn't publish anything. We think it can be related to the value of GLITE_LOCATION when this script is excuted. It seems the variable is defined but empty and this causes this funny error. We haven't been able to detect the real problem so far. The workaround is to restart the site BDII.

  • group.d/ defining the groups.conf per VO can't be used in the glexec WN. If you are installing a glexec WN, please define groups.conf as usual.
  • Bug #39022: affecting BDII. BDII_USER should always be the default 'edguser' for the time being until the mentioned bug is fixed.
  • Bug #39254: affecting WMS. The LCG VOMS host certificates rpm needs to be installed in the WMS. If you are planning to use only lsc files, you'll find the mentioned bug.

Known issues in yaim core 4.0.5-2

  • Affecting WMS: the variable GLITE_USER_HOME has to be defined in site-info.def as GLITE_USER_HOME=${GLITE_HOME_DIR} or the config_glite_wms function will fail.
  • group.d/ defining the groups.conf per VO can't be used in the glexec WN. If you are installing a glexec WN, please define groups.conf as usual.
  • Bug #39022: affecting BDII. BDII_USER should always be the default 'edguser' for the time being until the mentioned bug is fixed.
  • For the configuration of the TAR UI:
    • remove the following set of variables from site-info.pre:
X509_VOMS_DIR="/etc/grid-security/vomsdir/"
X509_CERT_DIR="/etc/grid-security/certificates/"
X509_HOST_CERT="/etc/grid-security/hostcert.pem"
X509_HOST_KEY="/etc/grid-security/hostkey.pem"
    • and include them in site-info.post appending the GLITE_EXTERNAL_ROOT variable:
X509_VOMS_DIR="${GLITE_EXTERNAL_ROOT}/etc/grid-security/vomsdir/"
X509_CERT_DIR="${GLITE_EXTERNAL_ROOT}/etc/grid-security/certificates/"
X509_HOST_CERT="${GLITE_EXTERNAL_ROOT}/etc/grid-security/hostcert.pem"
X509_HOST_KEY="${GLITE_EXTERNAL_ROOT}/etc/grid-security/hostkey.pem"

  • Bug #39174: affecting most of the node types: config_crl doesn't work properly because of an error introduced when trying to fix something. The "else" in line 98 should be removed.

  • In case we want to configure glexec in the TAR WN, the relevant files containing gridmap information, should take into account GLITE_EXTERNAL_ROOT. so probably, it's best to define the following variables in site-info.post like this:

GRIDMAPFILE="${GLITE_EXTERNAL_ROOT}/etc/grid-security/grid-mapfile"
GRIDMAPDIR="${GLITE_EXTERNAL_ROOT}/etc/grid-security/gridmapdir"
GROUPMAPFILE="${GLITE_EXTERNAL_ROOT}/etc/grid-security/groupmapfile"

-- MariaALANDESPRADILLO - 22 Jul 2008

Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r13 - 2008-08-13 - MariaALANDESPRADILLO
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback