Follow-up Comment #9, bug #94002 (project xrootd):
Hi Andrew,
In the end the downgrade went much smoother than I expected. Let me just post
a howto, maybe it will make things easier for others.
So, in order to downgrade the service on all our worker nodes, I did these
things on all of them:
1. Stopped all the services with:
service frm_xfrd stop && service frm_purged stop && service cmsd stop &&
service xrootd stop
2. Installed a little extension to YUM that makes downgrading packages
easier:
yum install yum-allowdowngrade
3. Downgraded the packages with:
yum downgrade xrootd-client-3.1.1-1.slc5.xu
xrootd-client-devel-3.1.1-1.slc5.xu xrootd-debuginfo-3.1.1-1.slc5.xu
xrootd-fuse-3.1.1-1.slc5.xu xrootd-libs-3.1.1-1.slc5.xu
xrootd-libs-devel-3.1.1-1.slc5.xu xrootd-server-3.1.1-1.slc5.xu
xrootd-server-devel-3.1.1-1.slc5.xu
4. Edited the /etc/sysconfig/xrootd file to correspond to the 3.1.1 setup.
The FRM daemons got two separate configurations in 3.2 (which I very much
support), while they use the same configuration in 3.1. (Since I just updated
these configuration files yesterday, rolling them back to the previous setting
was easy enough.)
5. Restarted the services with:
service xrootd start && service cmsd start && service frm_purged start &&
service frm_xfrd start
This seems to have gone well. The tests I've ran so far were all successful,
the staging is working once again as expected.
Cheers,
Attila
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?94002>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
