Hi,
I am trying to run a software which requires a specific version of glib(GLIBC_2.7). Current version of GLIB on my system is 2.5 and error which I am getting is - ------------------------------ [hp@mysys example]$ /share/apps/CAP3/cap3: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by /share/apps/CAP3/cap3) ------------------------------ [root@mysys scratch]# ldd --version ldd (GNU libc) 2.5 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Roland McGrath and Ulrich Drepper. ---------------------------------------------
I have tried to upgrade the package with both yum and rpm but it failed. Here is what I got when I tried yum upgrade. Can anyone help in fixing this? Btw, I am running CentOS 5.4
---------------------------------------------- [root@mysys scratch]# yum update glib* http://xx.xx.xx.xx/install/rocks-dist/x86_64/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (113, 'No route to host')> Trying other mirror. Setting up Update Process Examining glibc-2.7-12.2mnb1.x86_64.rpm: 6:glibc-2.7-12.2mnb1.x86_64 Marking glibc-2.7-12.2mnb1.x86_64.rpm as an update to glibc-2.5-118.el5_10.2.x86_64 Marking glibc-2.7-12.2mnb1.x86_64.rpm as an update to glibc-2.5-118.el5_10.2.i686 Resolving Dependencies --> Running transaction check --> Processing Dependency: glibc = 2.5-118.el5_10.2 for package: glibc-devel --> Processing Dependency: glibc = 2.5-118.el5_10.2 for package: nscd --> Processing Dependency: glibc = 2.5-118.el5_10.2 for package: glibc-devel --> Processing Dependency: glibc = 2.5-118.el5_10.2 for package: glibc-headers --> Processing Dependency: glibc = 2.5-118.el5_10.2 for package: glibc-devel --> Processing Dependency: glibc = 2.5-118.el5_10.2 for package: nscd --> Processing Dependency: glibc = 2.5-118.el5_10.2 for package: glibc-devel --> Processing Dependency: glibc = 2.5-118.el5_10.2 for package: glibc-headers ---> Package glibc.x86_64 6:2.7-12.2mnb1 set to be updated --> Processing Dependency: dash-static for package: glibc --> Processing Dependency: dash-static for package: glibc --> Processing Dependency: /bin/dash.static for package: glibc --> Processing Dependency: /bin/dash.static for package: glibc --> Processing Conflict: glibc-common conflicts glibc > 2.5 --> Finished Dependency Resolution glibc-devel-2.5-118.el5_10.2.i386 from installed has depsolving problems --> Missing Dependency: glibc = 2.5-118.el5_10.2 is needed by package glibc-devel-2.5-118.el5_10.2.i386 (installed) glibc-devel-2.5-118.el5_10.2.x86_64 from installed has depsolving problems --> Missing Dependency: glibc = 2.5-118.el5_10.2 is needed by package glibc-devel-2.5-118.el5_10.2.x86_64 (installed) glibc-headers-2.5-118.el5_10.2.x86_64 from installed has depsolving problems --> Missing Dependency: glibc = 2.5-118.el5_10.2 is needed by package glibc-headers-2.5-118.el5_10.2.x86_64 (installed) 6:glibc-2.7-12.2mnb1.x86_64 from /glibc-2.7-12.2mnb1.x86_64 has depsolving problems --> Missing Dependency: /bin/dash.static is needed by package 6:glibc-2.7-12.2mnb1.x86_64 (/glibc-2.7-12.2mnb1.x86_64) nscd-2.5-118.el5_10.2.x86_64 from installed has depsolving problems --> Missing Dependency: glibc = 2.5-118.el5_10.2 is needed by package nscd-2.5-118.el5_10.2.x86_64 (installed) 6:glibc-2.7-12.2mnb1.x86_64 from /glibc-2.7-12.2mnb1.x86_64 has depsolving problems --> Missing Dependency: dash-static is needed by package 6:glibc-2.7-12.2mnb1.x86_64 (/glibc-2.7-12.2mnb1.x86_64) glibc-common-2.5-118.el5_10.2.x86_64 from installed has depsolving problems --> glibc-common conflicts with glibc Error: Missing Dependency: dash-static is needed by package 6:glibc-2.7-12.2mnb1.x86_64 (/glibc-2.7-12.2mnb1.x86_64) Error: Missing Dependency: glibc = 2.5-118.el5_10.2 is needed by package nscd-2.5-118.el5_10.2.x86_64 (installed) Error: glibc-common conflicts with glibc Error: Missing Dependency: glibc = 2.5-118.el5_10.2 is needed by package glibc-devel-2.5-118.el5_10.2.x86_64 (installed) Error: Missing Dependency: glibc = 2.5-118.el5_10.2 is needed by package glibc-headers-2.5-118.el5_10.2.x86_64 (installed) Error: Missing Dependency: glibc = 2.5-118.el5_10.2 is needed by package glibc-devel-2.5-118.el5_10.2.i386 (installed) Error: Missing Dependency: /bin/dash.static is needed by package 6:glibc-2.7-12.2mnb1.x86_64 (/glibc-2.7-12.2mnb1.x86_64) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. --------------------------------
Regards Hersh
On Wed, 26 Mar 2014 21:37:07 -0700 (PDT) Hersh Parikh wrote:
Examining glibc-2.7-12.2mnb1.x86_64.rpm: 6:glibc-2.7-12.2mnb1.x86_64
I think "mnb" means that you have a Mandriva rpm there; nothing to do with Centos.
The current version of glibc on Centos 5 is glibc-2.5-118.el5_10.2
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Regards Hersh
On Thursday, 27 March 2014 10:27 AM, Frank Cox theatre@melvilletheatre.com wrote:
On Wed, 26 Mar 2014 21:37:07 -0700 (PDT) Hersh Parikh wrote:
Examining glibc-2.7-12.2mnb1.x86_64.rpm: 6:glibc-2.7-12.2mnb1.x86_64
I think "mnb" means that you have a Mandriva rpm there; nothing to do with Centos.
The current version of glibc on Centos 5 is glibc-2.5-118.el5_10.2
Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
Hi Alexnder,
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system. Backing all of this not very continent.
Regards Hersh
On Thursday, 27 March 2014 1:30 PM, Alexander Dalloz ad+lists@uni-x.org wrote:
Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 03/27/2014 04:52 AM, Hersh Parikh wrote:
Hi Alexnder,
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system. Backing all of this not very continent.
Regards Hersh
Then let's hope that none of you machines touch the internet in any way.
Staying on any version of CentOS except the latest in a branch is not safe. CentOS-5.10 is CentOS-5.4 with just bugfix and security updates. CentOS-5 is safe, CentOS-5.10 is safe. CentOS-5.4 is unsafe. For the record, there are more than 300 security updates released, dozens of them rated as Critical after 5.4 in the CentOS-5 tree (currently 5.10).
Critical means remotely exploitable.
Updates within a branch (that is, updates that stay on the CentOS-5 family in this case) SHOULD work and not break things. Obviously bugs happen and sometimes things do not work ... that should be the exception, not the rule.
It is imperative that people install security updates, otherwise it is not a question of if, but when their machines will be exploited.
On Thursday, 27 March 2014 1:30 PM, Alexander Dalloz ad+lists@uni-x.org wrote:
Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
Hi Johnny,
Thanks for the explanation. yes I do understand that critical patches needs to be applied for any OS. But in this case it is not a stand alone machine, it is a cluster suite and OS was not installed separately. I would have definitely upgraded the system if this was stand alone box. If I remember correctly, long back I was suggested not to upgrade cluster suite due to various reasons. Though I will check on this and see if its upgradable. If it is, I will try it out.
On Thursday, 27 March 2014 5:10 PM, Johnny Hughes johnny@centos.org wrote:
On 03/27/2014 04:52 AM, Hersh Parikh wrote:
Hi Alexnder,
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system. Backing all of this not very continent.
Regards Hersh
Then let's hope that none of you machines touch the internet in any way.
Staying on any version of CentOS except the latest in a branch is not safe. CentOS-5.10 is CentOS-5.4 with just bugfix and security updates. CentOS-5 is safe, CentOS-5.10 is safe. CentOS-5.4 is unsafe. For the record, there are more than 300 security updates released, dozens of them rated as Critical after 5.4 in the CentOS-5 tree (currently 5.10).
Critical means remotely exploitable.
Updates within a branch (that is, updates that stay on the CentOS-5 family in this case) SHOULD work and not break things. Obviously bugs happen and sometimes things do not work ... that should be the exception, not the rule.
It is imperative that people install security updates, otherwise it is not a question of if, but when their machines will be exploited.
On Thursday, 27 March 2014 1:30 PM, Alexander Dalloz ad+lists@uni-x.org wrote: Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
You wrote:
Thanks for the explanation. yes I do understand that critical patches needs to be applied for any OS. But in this case it is not a stand alone machine, it is a cluster suite and OS was not installed separately. I would have definitely upgraded the system if this was stand alone box. If I remember correctly, long back I was suggested not to upgrade cluster suite due to various reasons. Though I will check on this and see if its upgradable. If it is, I will try it out.
Let me put it this way: is there *anything* other than an air gap between this system and the Internet? If not, you *NEED* to file a report with your manager(s), and get at *least* a return receipt - a *signed* by them piece of paper would be a lot better - stating that the failure to update to 5.10 is, in your professional opinion a very serious security risk, and not doing so opens the gateway wide to a major security breach, and that you have explained this to them, and they understand the risks.
Then point them to somewhere like, say, http://krebsonsecurity.com/ and have them read about the Sally Beauty breach, and, scrolling down the Target breach, and all the other breaches, and the costs to the companies involved of those breaches.
You really do need to pound this into their heads.
mark
At Thu, 27 Mar 2014 02:52:51 -0700 (PDT) CentOS mailing list centos@centos.org wrote:
Hi Alexnder,
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system. Backing all of this not very continent.
First of all, you can update to 5.10 using yum (a 'yum update' will automagically update to 5.10). I don't know how this would affect the clustering, though.
Regards Hersh
On Thursday, 27 March 2014 1:30 PM, Alexander Dalloz ad+lists@uni-x.org wrote:
Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 03/27/2014 08:26 AM, Robert Heller wrote:
At Thu, 27 Mar 2014 02:52:51 -0700 (PDT) CentOS mailing list centos@centos.org wrote:
Hi Alexnder,
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Â Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system. Backing all of this not very continent.Â
First of all, you can update to 5.10 using yum (a 'yum update' will automagically update to 5.10). I don't know how this would affect the clustering, though.
Regards Hersh
On Thursday, 27 March 2014 1:30 PM, Alexander Dalloz ad+lists@uni-x.org wrote:
Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
As I just pointed out in a previous email to the list - I did a yum upgrade from 6.4 to 6.5 and is broke our OSPF network. I had to revert back to the last 6.4 kernel to get it working again.
On 03/27/2014 07:37 AM, Steve Clark wrote:
On 03/27/2014 08:26 AM, Robert Heller wrote:
At Thu, 27 Mar 2014 02:52:51 -0700 (PDT) CentOS mailing list centos@centos.org wrote:
Hi Alexnder,
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Â Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system. Backing all of this not very continent.Â
First of all, you can update to 5.10 using yum (a 'yum update' will automagically update to 5.10). I don't know how this would affect the clustering, though.
Regards Hersh
On Thursday, 27 March 2014 1:30 PM, Alexander Dalloz ad+lists@uni-x.org wrote:
Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
As I just pointed out in a previous email to the list - I did a yum upgrade from 6.4 to 6.5 and is broke our OSPF network. I had to revert back to the last 6.4 kernel to get it working again.
That certainly does happen and individual packages can be excluded (and the bugs reported) ... but upgrades still need to happen whenever possible.
We have released 4 different kernels since 6.5 (so 5 kernels including the one on the 6.5 iso ... so keep checking if it works).
Again, these updates happen because there are issues that need to be fixed, and it is very important that they get applied.
On 03/27/2014 08:51 AM, Johnny Hughes wrote:
On 03/27/2014 07:37 AM, Steve Clark wrote:
On 03/27/2014 08:26 AM, Robert Heller wrote:
At Thu, 27 Mar 2014 02:52:51 -0700 (PDT) CentOS mailing list centos@centos.org wrote:
Hi Alexnder,
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Â Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system. Backing all of this not very continent.Â
First of all, you can update to 5.10 using yum (a 'yum update' will automagically update to 5.10). I don't know how this would affect the clustering, though.
Regards Hersh
On Thursday, 27 March 2014 1:30 PM, Alexander Dalloz ad+lists@uni-x.org wrote:
Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
As I just pointed out in a previous email to the list - I did a yum upgrade from 6.4 to 6.5 and is broke our OSPF network. I had to revert back to the last 6.4 kernel to get it working again.
That certainly does happen and individual packages can be excluded (and the bugs reported) ... but upgrades still need to happen whenever possible.
We have released 4 different kernels since 6.5 (so 5 kernels including the one on the 6.5 iso ... so keep checking if it works).
Again, these updates happen because there are issues that need to be fixed, and it is very important that they get applied.
Hi Johnny,
First let me thank you and the CentOS team for the great work that you do!
Secondly I don't disagree about the need to keep our systems current, but Hersh indicated that this was a clustered production system and I was merely pointing out that there could be breakage by doing an upgrade.
Regards,
Am 27.03.2014 um 14:10 schrieb Steve Clark sclark@netwolves.com:
On 03/27/2014 08:51 AM, Johnny Hughes wrote:
that certainly does happen and individual packages can be excluded (and the bugs reported) ... but upgrades still need to happen whenever possible.
We have released 4 different kernels since 6.5 (so 5 kernels including the one on the 6.5 iso ... so keep checking if it works).
Again, these updates happen because there are issues that need to be fixed, and it is very important that they get applied.
Hi Johnny,
First let me thank you and the CentOS team for the great work that you do!
Secondly I don't disagree about the need to keep our systems current, but Hersh indicated that this was a clustered production system and I was merely pointing out that there could be breakage by doing an upgrade.
what is confusing me is the usage of upgrade and update as synonym. The suggested activity is an update (you stay with the same OS, libs etc.) and this will not break any compatibility with an already running 3rd party software. I mean if someone is scared about the "production" system, will it change a broken harddisk if it is faulty? 5.4 is faulty - it is an inherent attribute of software that mistakes are found and corrected.
So my suggestion is; reboot your system to check to functionality of all services after this. then update your system with yum update rpm* glibc yum*; yum update
to your original question: you can not use a more recent glibc version. it is not just an optional piece of software that can be altered, it is the main/core part of an OS ...
-- LF
Hi Guys,
Thanks for your valuable suggestion. I will keep them in mind. I have checked whether there is a way to update to Centos to 5.10 without damaging the cluster suite and I was suggested the best way is to reinstall the entire cluster suite. There are few suggestions around this but they are not tested. So I would not like to take a risk with untested solution. So now I will start looking for feasibility of upgrading the entire suite. This may take sometime but I guess at some stage it needs to be done.
On Friday, 28 March 2014 12:11 AM, Steve Clark sclark@netwolves.com wrote:
On 03/27/2014 08:51 AM, Johnny Hughes wrote:
On 03/27/2014 07:37 AM, Steve Clark wrote:
On 03/27/2014 08:26 AM, Robert Heller wrote:
At Thu, 27 Mar 2014 02:52:51 -0700 (PDT) CentOS mailing list centos@centos.org wrote:
Hi Alexnder,
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Â Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system. Backing all of this not very continent.Â
First of all, you can update to 5.10 using yum (a 'yum update' will automagically update to 5.10). I don't know how this would affect the clustering, though.
Regards Hersh
On Thursday, 27 March 2014 1:30 PM, Alexander Dalloz ad+lists@uni-x.org wrote: Am 27.03.2014 06:22, schrieb Hersh Parikh:
Hi Frank,
Thanks for quick response. Does it mean that I cant have glib 2.7 on centos 5.4?
Right, you can't. If you install a different glibc than the one provided by CentOS 5, then your system will be completely broken. The glibc is a very important and central library set for the system.
Regards Hersh
Btw. CentOS 5.4 is outdated, vulnerable and the current release is 5.10. Please update.
Alexander
As I just pointed out in a previous email to the list - I did a yum upgrade from 6.4 to 6.5 and is broke our OSPF network. I had to revert back to the last 6.4 kernel to get it working again.
That certainly does happen and individual packages can be excluded (and the bugs reported) ... but upgrades still need to happen whenever possible.
We have released 4 different kernels since 6.5 (so 5 kernels including the one on the 6.5 iso ... so keep checking if it works).
Again, these updates happen because there are issues that need to be fixed, and it is very important that they get applied.
Hi Johnny,
First let me thank you and the CentOS team for the great work that you do!
Secondly I don't disagree about the need to keep our systems current, but Hersh indicated that this was a clustered production system and I was merely pointing out that there could be breakage by doing an upgrade.
Regards,
On Fri, Mar 28, 2014 at 02:33:05AM -0700, Hersh Parikh wrote:
Hi Guys,
Thanks for your valuable suggestion. I will keep them in mind. I have checked whether there is a way to update to Centos to 5.10 without damaging the cluster suite and I was suggested the best way is to reinstall the entire cluster suite. There are few suggestions around
... Next time, just say that your are using Rocks which is managing your CentOS distribution and not a plain CentOS-5 setup ;)
Cheers,
Tru
Sure. Will do so.
Thanks!! :)
On Friday, 28 March 2014 4:18 PM, Tru Huynh tru@centos.org wrote:
On Fri, Mar 28, 2014 at 02:33:05AM -0700, Hersh Parikh wrote:
Hi Guys,
Thanks for your valuable suggestion. I will keep them in mind. I have checked whether there is a way to update to Centos to 5.10 without damaging the cluster suite and I was suggested the best way is to reinstall the entire cluster suite. There are few suggestions around
... Next time, just say that your are using Rocks which is managing your CentOS distribution and not a plain CentOS-5 setup ;)
Cheers,
Tru
-----Original Message----- From: Hersh Parikh [mailto:hershparikh12@yahoo.com] Sent: Friday, March 28, 2014 7:05 AM To: CentOS mailing list Subject: Re: [CentOS] GLIBC_2.7 not found
Sure. Will do so.
Thanks!! :)
On Friday, 28 March 2014 4:18 PM, Tru Huynh tru@centos.org wrote:
On Fri, Mar 28, 2014 at 02:33:05AM -0700, Hersh Parikh wrote:
Hi Guys,
Thanks for your valuable suggestion. I will keep them in mind. I have checked whether there is a way to update to Centos to 5.10 without damaging the cluster suite and I was suggested the best way is to reinstall the entire cluster suite. There are few suggestions around
... Next time, just say that your are using Rocks which is managing your CentOS distribution and not a plain CentOS-5 setup ;)
Cheers,
Tru
if you MUST have the cluster accessible by the internet, or even much of the institution's intranet, definitely consider options for keeping it up to date. Or at least it's accessible nodes. I noticed when I looked at rocks[1] a while back, that there are folks in that community which have been _looking_ at how to safely do some updates: https://wiki.rocksclusters.org/wiki/index.php/Software_Update_%28SUWG%29 Note that it looks like they have not updated the page in a while, so I would use on a test cluster and do a small compute job that is in line with what your institution often does first. And of course see if that group could be reinvigorated. :)
Oh, and no I don't run a rocks myself, but had looked into one around the time of the formation of the above group.
[1] http://www.rocksclusters.org/wordpress/
Even when this disclaimer is not here: I am not a contracting officer. I do not have authority to make or modify the terms of any contract.
Robert Heller wrote:
At Thu, 27 Mar 2014 02:52:51 -0700 (PDT) CentOS mailing list centos@centos.org wrote:
Thanks for the info. I know its quite old but I cant update as its running with cluster suite and its a production unit. Â Moreover its not feasible to upgrade as I have hundreds for apps and data lying on the system.Backing all of this not very continent.Â
First of all, you can update to 5.10 using yum (a 'yum update' will automagically update to 5.10). I don't know how this would affect the clustering, though.
Oh, and btw, we have both H/A clusters and heavy-duty scientific computing clusters. The h/a's have not been any problem upgrading. We're very cautious on the scientific compute clusters, only because when we went, I think it was, from 5.x to 6.x, or there were mathematical inconsistencies that *may* have been from glibc. Those seem to have been resolved, but they push back until they can verify the results via regression test.
You *do* have a test system or cluster for them to regression test on, right...?
mark
-
Alexander Dalloz -
Denniston, Todd A CIV NAVSURFWARCENDIV Crane -
Frank Cox -
Hersh Parikh -
Johnny Hughes -
Leon Fauster -
m.roth＠5-cent.us -
Robert Heller -
Steve Clark -
Tru Huynh