gLite 3.1
glite-CREAM - Update to version 3.1.11-0
|
| Date |
08.04.2009 |
| Priority |
Normal |
Description
glite-CREAM
Update of CREAM. The main changes are:
Configuration
===========
- A problem in BLAH configuration fixed in order to reduce the probability of jobs aborted for "killed by signal 15"
- Publications of VO software tags in a CREAM CE is now supported
Bug fixes and new functionality
=======================
- Fixed a "too many open files" problem triggered by the purge operation
- Fixed a memory leak in the BLAH Blparser for LSF
- Fixed some problems in the BLAH BLparser which caused its crash or its inability to send notifications to CREAM
- BLAH is started via a "master" process, which monitors and in case restarts the parser
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 |
|
#44873 |
blah_child_poll_timeout should be configured in blah.config |
|
#45844 |
yaim-cream-ce doesn't call config_gip_vo_tag |
|
#45437 |
Sometimes the jobPurger throws the exception "Too many open files" |
|
#45718 |
Some check on log lines should be added on BLParser code |
|
#45736 |
Problems in case of resubmissions in the same CREAM CE: a new CREAM job is not created ! |
|
#45913 |
Proxy renewal not done for CREAM jobs not yet in IDLE status |
|
#45983 |
BLAH can leave children processes behind. |
|
#46024 |
Sometimes the AbstractJobExecutor throws the exception "Too many open files" |
|
#46283 |
Possible memory leak in strtoken function for BLParser |
|
#46684 |
CREAM should call glexec directly (not via a wrapper script) |
|
#46916 |
blparser startup daemon |
|
#47209 |
[CREAM CE] BL parser startup script assumes ${GLITE_LOCATION_VAR} exists |
|
#47375 |
BLParser could fail in sending notification to cream |
|
#47655 |
Failure updating the main authN proxy |
|
#47700 |
glexec failures in CREAM because /tmp is used as working directory |
Updated rpms
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
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|
