EMI 2 (Matterhorn) - Update 3 (25.09.2012) - v. 2.3.0-1

The Update contains:

  • minor releases of EMIR v. 1.2.0, dCache v. 2.2.41 & UNICORE/X6 v. 5.0.0-2
  • revision releases of CREAM v. 1.14.1 & WNoDES v. 2.0.2

CREAM v. 1.14.1 , task #31337

What's new:

  • This is an update of the CREAM providing some bug fixes. In particular it
addresses the following bugs:
    • #89153 : JobDBAdminPurger cannot purge jobs if CREAM DB is on another host
    • #93091 : Add some resubmission machinery to CREAM
    • #95480 : CREAM doesn't transfert the output files remotely under well known conditions
    • #95356: Better parsing for static definition files in lcg-info-dynamic-scheduler
    • #95552 : Malformed URL from glite-ce-glue2-endpoint-static
    • #95593 : CREAM cannot insert in the command queue if the lenght of the localUser field is > 14 chars
    • #96055 : Wrong DN format in logfiles for accounting

Installation and configuration:

  • See CREAM Sysadmin Guide.
  • Please note that yaim (re)configuration is required after installation/update

Known issues

List of RfCs:

Documentation:

  • All the documentation relevant for CREAM is available in the CREAM web site.

Updated artefacts

SL5
Binaries
dynsched-generic-2.4.1-1.sl5.noarch.rpm
glite-ce-cream-1.14.1-1.sl5.noarch.rpm
glite-ce-cream-core-1.14.1-1.sl5.noarch.rpm
glite-ce-cream-es-1.14.1-1.sl5.noarch.rpm
glite-ce-cream-api-java-1.14.1-2.sl5.noarch.rpm
glite-ce-cream-utils-1.2.1-0.sl5.x86_64.rpm
Binary tarballs
dynsched-generic-2.4.1-1.sl5.tar.gz
glite-ce-cream-1.14.1-1.sl5.tar.gz
glite-ce-cream-api-java-1.14.1-2.sl5.tar.gz
glite-ce-cream-utils-1.2.1-0.sl5.tar.gz
Sources
dynsched-generic-2.4.1-1.sl5.src.rpm
glite-ce-cream-1.14.1-1.sl5.src.rpm
glite-ce-cream-api-java-1.14.1-2.sl5.src.rpm
glite-ce-cream-utils-1.2.1-0.sl5.src.rpm
Source tarballs
dynsched-generic-2.4.1-1.src.tar.gz
glite-ce-cream-1.14.1-1.src.tar.gz
glite-ce-cream-api-java-1.14.1-2.src.tar.gz
glite-ce-cream-utils-1.2.1-0.src.tar.gz
SL6
Binaries
dynsched-generic-2.4.1-1.sl6.noarch.rpm
glite-ce-cream-1.14.1-1.sl6.noarch.rpm
glite-ce-cream-core-1.14.1-1.sl6.noarch.rpm
glite-ce-cream-es-1.14.1-1.sl6.noarch.rpm
glite-ce-cream-api-java-1.14.1-2.sl6.noarch.rpm
glite-ce-cream-utils-1.2.1-0.sl6.x86_64.rpm
Binary tarballs:
dynsched-generic-2.4.1-1.sl6.tar.gz
glite-ce-cream-1.14.1-1.sl6.tar.gz
glite-ce-cream-api-java-1.14.1-2.sl6.tar.gz
glite-ce-cream-utils-1.2.1-0.sl6.tar.gz
Sources:
dynsched-generic-2.4.1-1.sl6.src.rpm
glite-ce-cream-1.14.1-1.sl6.src.rpm
glite-ce-cream-api-java-1.14.1-2.sl6.src.rpm
glite-ce-cream-utils-1.2.1-0.sl6.src.rpm
Source tarballs:
dynsched-generic-2.4.1-1.src.tar.gz
glite-ce-cream-1.14.1-1.src.tar.gz
glite-ce-cream-api-java-1.14.1-2.src.tar.gz
glite-ce-cream-utils-1.2.1-0.src.tar.gz

dCache v. 2.2.4, task #31465

What's new:

  • dCache 2.2.4:
    • A potential problem, where chimera can leak a database connection has been fixed. Affected sites will see "list full in their log file. Several xrootd related race conditions and protocol violations in the pool have been fixed. Fixed an issue preventing upload through SRM to the root-directory of the name space. Support for running the srm service so that it directly uses a custom kpwd file (independent of the rest of dCache) has been removed. All SRM authentication and authorisation activity must now go through gPlazma. Note that it is possible to configure SRM to use a different gPlazma configuration from the rest of dCache by 'embedding' the gPlazma (see useGPlazmaAuthorizationModule and useGPlazmaAuthorizationCell options). These options, along with gPlazma's kpwd plugin, allow for an equivalent configuration. The srm service now listens on two ports. These are, by default, 8443 (as before) and 8445. Port 8443 continues to be for SRM clients that use GSI-based communication and the new port is for SRM clients that use SSL. While the SSL port is configurable, it is recommended to use the default as this an agreed port-number for SSL-based SRM traffic.
    • Resolved a conflict between the httpd service with billing plots enabled and the pin manager. Before those two service could not co-exist in the same dCache domain. Improved SQL standards compliance of replica manager. Fixed database related bugs that would prevent replica manager from operating within acceptable parameters. We now use the loopback interface when talking to rpcbind/portmap. Now, admins do not need to open portmapper port (111) in the firewalls. For nfs we switch to grizzly 2.2.9 with many improvements and bug fixes including internal IO buffers recycling. In the webadmin we can filter content of CellInfo, Pool Queue and Active Transfers tables. And we fixed 'page expired exception' which used to appear when page was left idle for more than 24 hours. For webdav we fixed a problem in the WebDAV door in which proxied reads would pause 5 to 10 seconds after the transfer. Also fixed an authorization problem in the WebDAV door relating to basic authentication. dCache erroneously replied with '405 method not allowed' when it should have replied '401 unauthorized'. Also resolved a compatibility issue between the dCache WebDAV door and Gnome. The problem prevented dCache WebDAV shares from being mounted in Gnome.
    • Gplazma2 supports gplazma1 as a plugin. The default configuration of dCache will work as the gplazma1 is configured. Any existing gplazma1 and gplazma2 configurations will work as before. NOTICE: we have no experience in combining gplazma1 plugin with other gplazma2 plugins.
    • Another useful addition are two new commands to the admin interface when looking at the! gPlazma cell. test login replaces the existing get mapping command. It shows the result of a login attempt but is more flexible when describing which principals have been identified for the user. The second is explain login. This command uses the same format as test login but provides detailed information on how the login was processed. The result of each processed plugin is explained in a tree structure.
    • For the poolmanager we suggest people regenerate poolmanager.conf after upgrade by running the save command in the pool manager. This will ensure compatibility with future releases.
    • Some of dCache properties accept only a few possible values (e.g., either true or false). The parsing of such properties is now more robust and incorrect values will be reported. Previously, incorrect values would take some default value. Now, if a property is configured with a value outside the set of acceptable values then an error is reported and dCache refuses to start. As part of this process, some equivalent property values are no longer considered the same; for example, some properties took true, True and TRUE as values that would result in the same behaviour but now only true is valid. After upgrading, we recommend you run the dcache check-config command to check your configuration.
    • dcache service is not enabled by default. Admins have to enable it by hand if required: /sbin/chkconfig --add dcache-server

Installation and configuration:

  • Please consider the following changes when upgrading from a version before dCache 2.2.0:
    • Doors and head nodes have to be updated at the same time.
    • NFSv4.1 door and pools are incompatible and have to be updated at the same time.
    • If NFS4.1 is not used, then 2.2 doors, head nodes and SRM can be mixed with pools of releases 1.9.12-11, 1.9.13-4 or newer. Doors and head nodes have to be updated at the same time.
    • If you are installing over a pre-existent billing database, you may, after upgrading and starting dCache, see some messages in the log for the domain where billing is running similar to the following:
    INFO 8/23/12 10:35 AM:liquibase: Successfully acquired change log lock
    INFO 8/23/12 10:35 AM:liquibase: Reading from databasechangelog
    INFO 8/23/12 10:35 AM:liquibase: Reading from databasechangelog
    INFO 8/23/12 10:35 AM:liquibase: Successfully released change log lock
    INFO 8/23/12 10:35 AM:liquibase: Successfully released change log lock
    INFO 8/23/12 10:35 AM:liquibase: Successfully acquired change log lock
    INFO 8/23/12 10:35 AM:liquibase: Reading from databasechangelog
    INFO 8/23/12 10:35 AM:liquibase: Reading from databasechangelog
    INFO 8/23/12 10:35 AM:liquibase: ChangeSet
    org/dcache/services/billing/db/sql/billing.changelog-1.9.13.xml::4.1.7::arossi
    ran successfully in 264ms
    INFO 8/23/12 10:35 AM:liquibase: Marking ChangeSet:
    org/dcache/services/billing/db/sql/billing.changelog-1.9.13.xml::4.1.8::arossi::(Checksum:
    3:faff07731c4ac867864824ca31e8ae81) ran despite precondition failure due
    to onFail='MARK_RAN':

    classpath:org/dcache/services/billing/db/sql/billing.changelog-master.xml :
    SQL Precondition failed. Expected '0' got '1'

    INFO 8/23/12 10:35 AM:liquibase: ChangeSet
    org/dcache/services/billing/db/sql/billing.changelog-1.9.13.xml::4.1.9::arossi
    ran successfully in 14ms
    INFO 8/23/12 10:35 AM:liquibase: Successfully released change log lock
    INFO 8/23/12 10:35 AM:liquibase: Successfully released change log lock

  • As long as the debug level for these messages is INFO or WARN and not ERROR, they are normal and can be ignored. The database change manager is simply indicating that certain preconditions are not met and that some of the potentially necessary updates are unnecessary and may be skipped.

Known issues

  • None

List of RfCs:

Documentation:

Updated artefacts

SL5
Binaries
dcache-server-2.2.4-1.noarch.rpm
Binary tarballs
dcache-server-2.2.4-1.noarch.tar.gz
Sources
dcache-server-2.2.4-1.src.rpm
SL6
Binaries
dcache-server-2.2.4-1.noarch.rpm
Binary tarballs:
dcache-server-2.2.4-1.noarch.tar.gz
Sources:
dcache-server-2.2.4-1.src.rpm

EMIR v. 1.2.0, task #33592

What's new:

List of RfCs:

Documentation:

Updated artefacts

SL5
Binaries
emi-emir-1.2.0-0.sl5.noarch.rpm
emir-serp-1.1.0-0.el5.noarch.rpm
Binary tarballs
emi-emir-1.2.0-0.sl5.noarch.tar.gz
emir-serp-1.1.0-0.el5.noarch.tar.gz
Sources
emi-emir-1.2.0-0.sl5.src.rpm
emir-serp-1.1.0-0.el5.src.rpm
Source tarballs
emi-emir-1.2.0-0.src.tar.gz
emir-serp-1.1.0-0.src.tar.gz
SL6
Binaries
emi-emir-1.2.0-0.sl6.noarch.rpm
emir-serp-1.1.0-0.el6.noarch.rpm
Binary tarballs:
emi-emir-1.2.0-0.sl6.noarch.tar.gz
emir-serp-1.1.0-0.el6.noarch.tar.gz
Sources:
emi-emir-1.2.0-0.sl6.src.rpm
emir-serp-1.1.0-0.el6.src.rpm
Source tarballs:
emi-emir-1.2.0-0.src.tar.gz
emir-serp-1.1.0-0.src.tar.gz
Deb6
emi-emir_1.2.0-0_all.deb

UNICORE/X6 v. 5.0.0-2, task #33230

What's new:

  • all probes were adapted to UCC 6.5.0
  • dependency upon registry address in some probes has been removed
  • check_workflow has been rewritten to the synchronous version
  • a new function was added to check_application: "number_of_lines_between"
  • a new probe, check_activemq, was added
  • bug in check_servorch due to api change has been fixed
  • invalid rss parsing in check_versions has been fixed
  • a missing dependency upon package poppler-info has been added
  • buffer overflow problem in large nagios output (known as "Return code of 127 is out of bounds" has been fixed
  • bug in configuration file creating in check_uvos has been fixed
  • bug in check_unicorex on non-tss environment has been fixed
  • trust delegation support has been added to check_workflow

List of RfCs:

Documentation:

  • General documentation, administrators guide and developers guide: PDF, HTML

Updated artefacts

SL5
Binaries
unicore-nagios-plugins-2.2.1-1.sl5.noarch.rpm
Binary tarballs
unicore-nagios-plugins-2.2.1-1.sl5.x86_64.tar.gz
Sources
unicore-nagios-plugins-2.2.1-1.sl5.src.rpm
Source tarballs
unicore-nagios-plugins-2.2.1-1.src.tar.gz
SL6
Binaries
unicore-nagios-plugins-2.2.1-1.sl6.noarch.rpm
Binary tarballs:
unicore-nagios-plugins-2.2.1-1.sl6.x86_64.tar.gz
Sources:
unicore-nagios-plugins-2.2.1-1.sl6.src.rpm
Source tarballs:
unicore-nagios-plugins-2.2.1-1.src.tar.gz

WNoDES v. 2.0.2, task #32920

What's new:

List of RfCs:

Documentation:

Updated artefacts

SL5
Binaries
wnodes_bait-2.0.6-1.sl5.noarch.rpm
wnodes_hypervisor-2.0.4-3.sl5.noarch.rpm
wnodes_manager-2.0.3-3.sl5.noarch.rpm
wnodes_nameserver-2.0.4-1.sl5.noarch.rpm
wnodes_site_specific-2.0.1-1.sl5.noarch.rpm
wnodes_utils-2.0.2-1.sl5.noarch.rpm
Binary tarballs
wnodes_bait-2.0.6-1.sl5.noarch.tar.gz
wnodes_hypervisor-2.0.4-3.sl5.noarch.tar.gz
wnodes_manager-2.0.3-3.sl5.noarch.tar.gz
wnodes_nameserver-2.0.4-1.sl5.noarch.tar.gz
wnodes_site_specific-2.0.1-1.sl5.noarch.tar.gz
wnodes_utils-2.0.2-1.sl5.noarch.tar.gz
Sources
wnodes_bait-2.0.6-1.sl5.src.rpm
wnodes_hypervisor-2.0.4-3.sl5.src.rpm
wnodes_manager-2.0.3-3.sl5.src.rpm
wnodes_nameserver-2.0.4-1.sl5.src.rpm
wnodes_site_specific-2.0.1-1.sl5.src.rpm
wnodes_utils-2.0.2-1.sl5.src.rpm
Source tarballs
wnodes_bait-2.0.5.src.tar.gz
wnodes_hypervisor-2.0.4.src.tar.gz
wnodes_manager-2.0.3.src.tar.gz
wnodes_nameserver-2.0.4.src.tar.gz
wnodes_site_specific-2.0.1.src.tar.gz
wnodes_utils-2.0.2.src.tar.gz
SL6
Binaries
wnodes_bait-2.0.6-1.sl6.noarch.rpm
wnodes_hypervisor-2.0.4-3.sl6.noarch.rpm
wnodes_manager-2.0.3-3.sl6.noarch.rpm
wnodes_nameserver-2.0.4-1.sl6.noarch.rpm
wnodes_site_specific-2.0.1-1.sl6.noarch.rpm
wnodes_utils-2.0.2-1.sl6.noarch.rpm
Binary tarballs:
wnodes_bait-2.0.6-1.sl6.noarch.tar.gz
wnodes_hypervisor-2.0.4-3.sl6.noarch.tar.gz
wnodes_manager-2.0.3-3.sl6.noarch.tar.gz
wnodes_nameserver-2.0.4-1.sl6.noarch.tar.gz
wnodes_site_specific-2.0.1-1.sl6.noarch.tar.gz
wnodes_utils-2.0.2-1.sl6.noarch.tar.gz
Sources:
wnodes_bait-2.0.6-1.sl6.src.rpm
wnodes_hypervisor-2.0.4-3.sl6.src.rpm
wnodes_manager-2.0.3-3.sl6.src.rpm
wnodes_nameserver-2.0.4-1.sl6.src.rpm
wnodes_site_specific-2.0.1-1.sl6.src.rpm
wnodes_utils-2.0.2-1.sl6.src.rpm
Source tarballs:
wnodes_bait-2.0.5.src.tar.gz
wnodes_hypervisor-2.0.4.src.tar.gz
wnodes_manager-2.0.3.src.tar.gz
wnodes_nameserver-2.0.4.src.tar.gz
wnodes_site_specific-2.0.1.src.tar.gz
wnodes_utils-2.0.2.src.tar.gz
-- DoinaCristinaAiftimiei - 24-Sep-2012
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2012-09-25 - DoinaCristinaAiftimiei
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 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