Date |
24.03.2010 |
Priority |
Normal |
Description
glite-SE_dpm_mysql, glite-WN, glite-UI, glite-VOBOX, glite-LFC_mysql
New version of LFC and DPM
This is version 1.7.3 for both the LFC and DPM. It contains bug
fixes for both services with respect to version 1.7.2; in
particular
- Bug 53568, which could cause the DPM's SRM 2.2 server to
crash
- Bug 50686, which meant a malformed request could crash the
LFC or the DPNS
Other issues which may be noticed by users or
administrators:
- DPM will now only publish information regarding static spaces
to the information system, rather than information about all
spaces.
- dpm-listspaces reports space in units of powers of 1024 for
normal user use, to be consistent with other DPM tools. When
providing data for the information system quantities are reported
in SI units, as required by the glue schema.
The xrootd plugin for ALICE for the DPM has been upgraded to
version 2.1.0. As previously, in order to enable xrootd access the
xroot daemons must be obtained separately - they are not included
in the glite release. Plugin 2.1.0 is intended for use with
xrootd-20090729.0855, see:
https://twiki.cern.ch/twiki/bin/view/LCG/DpmXrootAccess21
The updated xrootd base is expected to bring increased stability
to the service. The DPM plugin is also has updated defaults for
some settings, extra authentication settings and uses the most
recent ALICE security plugin.
See the CHANGES and RELEASE files in the CVS repository for a
complete list of changes.
DPM Known issues:
For those upgrading from DPM 1.6.x please check the following
for known issues and considerations relating to the database schema
change:
https://twiki.cern.ch/twiki/bin/view/LCG/DpmVersion170SchemaChange
In case the DPM gridftp fails to startup with the error
message:
Starting dpm-gsiftp: /etc/sysconfig/dpm-gsiftp says NO:
[FAILED]
please check that your /etc/sysconfig/dpm-gsiftp contains the
line:
RUN_DPMFTP="yes"
(for configuration files built from the 1.6 template this
setting is missing)
glite-LFC_mysql, glite-SE_dpm_mysql, glite-UI, glite-WN, glite-VOBOX
Vulnerability fix for bug #54623
Important note for the UI and WN:
Due to a problem of the versioning scheme used by VDT, upgrading
an already existing gLite 3.2 UI and WN fails. Using the commands
"yum groupupdate glite-UI" resp. "yum
groupupdate glite-WN" fails with an error message
"package
vdt_globus_essentials-VDT1.10.1x86_64_rhap_5-3.x86_64 (which is
newer than vdt_globus_essentials-VDT1.10.1x86_rhap_5-4.i386) is
already installed". The workaround is to uninstall the
vdt_globus_essentials rpms manually:
rpm -e --nodeps vdt_globus_essentials-VDT1.10.1x86_rhap_5-3
vdt_globus_essentials-VDT1.10.1x86_64_rhap_5-3
Then do "yum groupupdate glite-UI" resp.
"yum groupupdate glite-WN"
glite-UI, glite-VOBOX, glite-WN
Vulnerability fix for bug #54623
Update to patch #3040 to fix vulnerability issue bug #54623 This update fixes various bugs. For the full list of bugs, please see list below.
Fixed bugs
Number | Description |
#35879 |
python module for LFC and DPM should be improved |
#39280 |
DPM 1.6.10: dpm_getspacetokens() returns an error message when no token exists |
#50686 |
There is a vulnerability concerning LFC |
#50818 |
operation with entries with wrong/unexisten uid crashed lfcdaemon |
#50962 |
dpm-listspaces should use consistent units |
#51493 |
DPM/https: fix Yaim configuration on disk only servers |
#51530 |
DPM should only publish static spaces |
#52075 |
DPM 1.7.2-4: /etc/sysconfig files overwritten by RPM |
#53568 |
DPM: srm daemon can attempt to use DB connection before it is opened |
#54542 |
LFC license issue |
#54792 |
[yaim lfc] reflect LFC sysconfig changes in YAIM configuration |
#54848 |
DPM/SRM: srmLs should return proper checksum algorithms |
#55699 |
LFC/Yaim: should handle remote DB |
#55777 |
DPM: httpd-cgi sets expire time too short on PUT/POST requests |
#55980 |
DPM: gridftp behavior for CKSM length argument |
#55982 |
LFC/DPM: Addition of liblcgdm library |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Not needed.
Service restart after update
Not needed.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|