gLite 3.0
glite-MON - Update to version 3.0.18-0
This update fixes various bugs. For the full list of bugs, please see list below.
This release contains a new version of YAIM. YAIM 3.1.1 will configure gLite 3.0 and gLite 3.1 services and clients. The main feature of the new YAIM is its modularity. There will be a yaim core module, a yaim client module and different yaim modules for each gLite service. In the first release not all the services have been splitted in a new module and therefore they are part of yaim core. The idea for upcoming releases is to have a full modular version.
If you have not already performed a manual action in order to fix bug #27539, then you to do need a re-configuration and restart of the node.
The first YAIM 3.1.1 release is a merge of yaim 3.0.1-22 and yaim 3.1.0 (for UI and WN). The new yaim will allow to configure all gLite 3.0 and gLite 3.1 services and clients.
Multiple improvements and bug fixes (see individual service updates for the list of fixed bugs):
glite-MON - Update to version 3.0.18-0
| Date | 20.08.07 |
|---|---|
| Priority | Normal |
Description
This update fixes various bugs. For the full list of bugs, please see list below.
YAIM
This release contains a new version of YAIM. YAIM 3.1.1 will configure gLite 3.0 and gLite 3.1 services and clients. The main feature of the new YAIM is its modularity. There will be a yaim core module, a yaim client module and different yaim modules for each gLite service. In the first release not all the services have been splitted in a new module and therefore they are part of yaim core. The idea for upcoming releases is to have a full modular version.
If you have not already performed a manual action in order to fix bug #27539, then you to do need a re-configuration and restart of the node.
The first YAIM 3.1.1 release is a merge of yaim 3.0.1-22 and yaim 3.1.0 (for UI and WN). The new yaim will allow to configure all gLite 3.0 and gLite 3.1 services and clients.
Information system (MON-Box)
Multiple improvements and bug fixes (see individual service updates for the list of fixed bugs):
- Update to prevent unnecessary load on the schema (co-hosted with the registry) when the R-GMA command line tool starts up.
- Optimizations to the R-GMA registry.
Fixed bugs
| Number | Description |
|---|---|
| #25946 | Possible memory leak in disk cache |
| #26345 | Avoid cleaning up resources on every call |
| #26812 | Slow message queues are not cleaned up when consumer is destroyed |
| #27504 | CLI submits a call to getAllTables when initialised |
| #27510 | R-GMA Registry is not coping with a large number of requests |
| #27841 | strange node type problem with at least WN_torque |
Updated rpms
| Name | Version | Full RPM name | Description |
|---|---|---|---|
| glite-MON | 3.0.18-0 | glite-MON-3.0.18-0.noarch.rpm | gLite MON node |
| glite-rgma-command-line | 5.0.5-1 | glite-rgma-command-line-5.0.5-1.noarch.rpm | R-GMA command line |
| glite-rgma-server-servlet | 5.0.43-1 | glite-rgma-server-servlet-5.0.43-1.noarch.rpm | Servlet-based R-GMA server implementation |
| glite-yaim-core | 3.1.1-8 | glite-yaim-core-3.1.1-8.noarch.rpm | org.glite.yaim.core |
The RPMs can be updated using apt via
- via apt: apt-get dist-upgrade
- or via a download from:
http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/rhel30/RPMS.updates/
Service reconfiguration after update
If you have not already performed a manual action in order to fix bug #27539, then you to do need a re-configuration of the nodes.
Service restart after update
If you have not already performed a manual action in order to fix bug #27539, then you to do need a restart of the node.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)