It means that all the previous updates have to been applied before the last one:
Please check the instructions you find at the following link:
As good practice is suggested to disable the yum-autoupdate service. Any other settings is decided at site-manager own risk!
To disable the service it is available the following script ” disable_yum.sh” (thanks Giuseppe Platania) that can be used to REALLY disable yum-autoupdate.
Find your nodetype and carefully follow the corresponding actions.
|Profiles|| Metapackages |
| Nodetypes |
| Service |
| Partial |
| Total |
|ARGUS|| || ||-||-||-|| 1_Metapackage_update |
|BDII|| || ||-||-||-||1_Metapackage_update||-|
|GLEXEC_wn|| || ||-||-||-|| 1_Metapackage_update |
|LB|| || ||-||-||-||1_Profile_first_installation||First release!|
Important note on how to update ig_UI and ig_WN
Due to a problem of the versioning scheme used by VDT, upgrading an already existing gLite 3.2 WN or UI fails. Using the update command “yum groupupdate ig_WN” or “yum groupupdate ig_UI” 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 ig_WN” or “yum groupupdate ig_UI”.
Each of the following sections reports the actions that may be follow in order to upgrade your profiles. Please execute ONLY the actions listed on the table above in the column “Actions” and in the row correspondig to your profile!
Please see YUM Tips for additional information about YUM.
yum clean all yum install <node-type>
Please remember that on case of WN you should use the “groupinstall”:
yum groupinstall ig_WN_torque
defaultsdirectories (see ”updates” for information about those locations). Please carefully check your
<site-info.def>and files under
nodes/directories comparing to the new ones distributed with latest released
yaimmodules. For example you can use
vimdifflike here below:
vimdiff /opt/glite/yaim/examples/siteinfo/ig-site-info.def <site-info.def>
You can see the main differences between the previous release of ig-site-info.def (ig-yaim-4.0.11-4) and the present one (ig-yaim-4.0.12-1) at the following link ig-site-info.def differences
In order to help the comparison the ”Differences between INFNGRID Updates” page has been prepared. WIP
You may find more detailed information on configuration files structure here:
and on configuration variables here:
IMPORTANT: <siteconfig>/services directory
Please ensure that you have all the NEEDED configuration files under your
<siteconfig>/services directory (for example:
For any details please refer to the ”INFNGRID YAIM configuration files” reference.
Known Issues: /etc/init.d/tomcat5
Latest version of tomcat5 has a bug on its init script that arises the following error when the service is stopped/started:
/etc/rc.d/init.d/tomcat5: line 196: log_success_msg: command not found
You may fix it simply modifying the first line of
/etc/init.d/tomcat5 file as follows:
/opt/glite/yaim/bin/ig_yaim -c -s <site-info.def> -n <nodetype>
<nodetype> is one of the nodetypes listed in the “Nodetypes” column of the table above.
NOTE: Please remember to add ”
-n ig_BDII_site” if you want to reconfiguring a site BDII on top of your CE.
Look at your
chkconfig services list and restart all middleware-related service:
chkconfig --list | grep 3:on | sort
Then restart with:
service <middleware-service> restart
After the update please edit the following wiki page with the current situation of your site (when update is done set “
3.2 Update 09”):