Dear All,
I am curently running a CENTOS server with the following setup
CentOS release 5 (Final) Kernel 2.6.18-8.1.8.el5xen on an i686 bind-9.3.3-10.el5 sendmail-8.13.8-2.el5 apache httpd-2.2.3-11.el5_1.centos.3 MailScanner ver 4.66.5 ClamAV 0.92 SpamAssassin version 3.2.4 SquirrelMail ver 1.4.13
Now all this have been workin perfectly fine for a long time.
now if i do a yum upgrade i see the following
Install 29 Package(s) Update 415 Package(s) Remove 0 Package(s)
and the total download size is abt 579 M
i jus wanted to know if i could SAFELY apply the updates since its a live server running our companys primary DNS and mail server
has any body done this b4
i know the Centos will be upgraded to 5.2
but has anybody applied these updates and its been workin fine after reboot and also about the various software currently running on the server apprecite your help and asvise
regards
Fabian
fabian dacunha wrote:
i jus wanted to know if i could SAFELY apply the updates since its a live server running our companys primary DNS and mail server
noone has your exact configuration, so the only way to know if it will for sure work for you would be to test it on a staging server configured identically to your production server, or at least, make full backups of your system so you can restore it if something goes wrong.
generally, updates are safe if your system is clean and doesn't have its system components polluted by non-distribution code.
On Thu, 2008-06-26 at 11:35 -0700, John R Pierce wrote:
fabian dacunha wrote:
i jus wanted to know if i could SAFELY apply the updates since its a live server running our companys primary DNS and mail server
In case you missed it, there was a recommended "two step" and parameter recommendation.
1. yum update yum rpm 2. yum upgrade # not update
<snip>
As Jim alluded to, and others have stated explicitly in the past, an update of a live server without adequate testing and/or fallback plan is akin to unassisted suicide. It won't be your foot you shot yourself in if something goes drastically wrong.
William L. Maltby wrote on Thu, 26 Jun 2008 14:48:48 -0400:
- yum upgrade # not update
that's supposed to be the same.
Kai
On Thu, 2008-06-26 at 21:31 +0200, Kai Schaetzl wrote:
William L. Maltby wrote on Thu, 26 Jun 2008 14:48:48 -0400:
- yum upgrade # not update
that's supposed to be the same.
IIRC, that's true if default config file wasn't modified with certain parameters. Do I mis-remember? IIRC, upgrade works correctly even if they changed that config parameter. So, better safe than sorry.
If I mis-remember, please forgive an old fart with half-heimer's. :-))
Kai
I just updated from an i386 CentOS 5 system today, using the reccommendeds steps on my server, and it went fine.
So it *should* also go fine for you, but, as has been said before, Your Mileage May Vary.
2008/6/26 William L. Maltby CentOS4Bill@triad.rr.com:
On Thu, 2008-06-26 at 21:31 +0200, Kai Schaetzl wrote:
William L. Maltby wrote on Thu, 26 Jun 2008 14:48:48 -0400:
- yum upgrade # not update
that's supposed to be the same.
IIRC, that's true if default config file wasn't modified with certain parameters. Do I mis-remember? IIRC, upgrade works correctly even if they changed that config parameter. So, better safe than sorry.
If I mis-remember, please forgive an old fart with half-heimer's. :-))
Kai
-- Bill
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
on 6-26-2008 3:09 PM Michael Holmes spake the following:
I just updated from an i386 CentOS 5 system today, using the reccommendeds steps on my server, and it went fine.
So it *should* also go fine for you, but, as has been said before, Your Mileage May Vary.
Even though there have been several posts with problems, there have probably been hundreds of upgrades if not thousands that went fine.
Thanks guys for the various suggestions
really do apprecite but as u guys say i shd follow ..
have a perfect backup system and then do the upgrade
really apprecite
regards
fabian
simon
I just updated from an i386 CentOS 5 system today, using the reccommendeds steps on my server, and it went fine.
So it *should* also go fine for you, but, as has been said before, Your Mileage May Vary.
2008/6/26 William L. Maltby CentOS4Bill@triad.rr.com:
On Thu, 2008-06-26 at 21:31 +0200, Kai Schaetzl wrote:
William L. Maltby wrote on Thu, 26 Jun 2008 14:48:48 -0400:
- yum upgrade # not update
that's supposed to be the same.
IIRC, that's true if default config file wasn't modified with certain parameters. Do I mis-remember? IIRC, upgrade works correctly even if they changed that config parameter. So, better safe than sorry.
If I mis-remember, please forgive an old fart with half-heimer's. :-))
Kai
-- Bill
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
You are right, there is a difference:
upgrade Is the same as the update command with the --obsoletes flag set. See update for more details.
Kai
Kai Schaetzl wrote:
You are right, there is a difference:
upgrade Is the same as the update command with the --obsoletes flag set. See update for more details.
If the /etc/yum.conf file contains:
obsoletes=1
yum update will be the same as yum upgrade.
The yum.conf file will have this line unless manually removed or you've upgraded from a previous CentOS release that didn't have it. I guess it has to be very old then, the line is present in CentOS 4 and 5...
Mogens
Mogens Kjaer wrote:
Kai Schaetzl wrote:
You are right, there is a difference:
upgrade Is the same as the update command with the --obsoletes flag set. See update for more details.
If the /etc/yum.conf file contains:
obsoletes=1
yum update will be the same as yum upgrade.
The yum.conf file will have this line unless manually removed or you've upgraded from a previous CentOS release that didn't have it. I guess it has to be very old then, the line is present in CentOS 4 and 5...
Mogens
Which is why yum upgrade is recommended, yum update may or may not work for everyone, depending on this flag
Rudi Ahlers wrote: ...
Which is why yum upgrade is recommended, yum update may or may not work for everyone, depending on this flag
Many have expressed concern because they've used "yum update" instead of "yum upgrade".
My point is that it might not be a problem.
Mogens
Mogens Kjaer kirjoitti viestissään (lähetysaika perjantai, 27. kesäkuuta 2008):
Rudi Ahlers wrote: ...
Which is why yum upgrade is recommended, yum update may or may not work for everyone, depending on this flag
Many have expressed concern because they've used "yum update" instead of "yum upgrade".
My point is that it might not be a problem.
Mogens
Both methods worked here, yup upgrade into desktop and yum update into my wifes laptop. No problems occured after.
Jarmo
Mogens Kjaer wrote on Fri, 27 Jun 2008 12:55:58 +0200:
The yum.conf file will have this line unless manually removed
And you are right, too :-) William mentioned the config file, btw, he just didn't mention the flag.
Kai
William L. Maltby <> scribbled on Thursday, June 26, 2008 8:49 PM:
an update of a live server without adequate testing and/or fallback plan is akin to unassisted suicide. It won't be your foot you shot yourself in if something goes drastically wrong.
LOL! Clear and to the point. Good one!
Why don't you clone your machine, or use Vmware or something, and do an test before you do it with your production-machine? Asking this sort of question is, well, rather meaningless IMO. Your setup is unique considering what tweaks you might've done to it. YMMV as they say. What works for me, doesn't necessarily work for you, or vice versa.
Testing before use in sharp situations is always a good idea, although I've been pampered and spoiled by CentOS's stability on inplace-upgrades, like this last one. 8-}
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of fabian dacunha Sent: Thursday, June 26, 2008 8:46 PM To: centos@centos.org Subject: [CentOS] is centos update safe
Dear All,
I am curently running a CENTOS server with the following setup
CentOS release 5 (Final) Kernel 2.6.18-8.1.8.el5xen on an i686 bind-9.3.3-10.el5 sendmail-8.13.8-2.el5 apache httpd-2.2.3-11.el5_1.centos.3 MailScanner ver 4.66.5 ClamAV 0.92 SpamAssassin version 3.2.4 SquirrelMail ver 1.4.13
Now all this have been workin perfectly fine for a long time.
now if i do a yum upgrade i see the following
Install 29 Package(s) Update 415 Package(s) Remove 0 Package(s)
and the total download size is abt 579 M
i jus wanted to know if i could SAFELY apply the updates since its a live server running our companys primary DNS and mail server
has any body done this b4
i know the Centos will be upgraded to 5.2
but has anybody applied these updates and its been workin fine after reboot and also about the various software currently running on the server apprecite your help and asvise
regards
Fabian
On Thu, 2008-06-26 at 21:46 +0300, fabian dacunha wrote:
Dear All,
I am curently running a CENTOS server with the following setup
CentOS release 5 (Final) Kernel 2.6.18-8.1.8.el5xen on an i686
Stating the obvious, you are WAY behind on updates, including many security patches.
bind-9.3.3-10.el5 sendmail-8.13.8-2.el5 apache httpd-2.2.3-11.el5_1.centos.3 MailScanner ver 4.66.5 ClamAV 0.92 SpamAssassin version 3.2.4 SquirrelMail ver 1.4.13
Now all this have been workin perfectly fine for a long time.
now if i do a yum upgrade i see the following
Install 29 Package(s) Update 415 Package(s) Remove 0 Package(s)
and the total download size is abt 579 M
i jus wanted to know if i could SAFELY apply the updates since its a live server running our companys primary DNS and mail server
I'd have a bootable backup ready before trying this. See the section on "cloning" in http://wiki.centos.org/HowTos/MigrationGuide.
has any body done this b4
Lots of people have updated by now.
i know the Centos will be upgraded to 5.2
but has anybody applied these updates and its been workin fine after reboot and also about the various software currently running on the server apprecite your help and asvise
Have had two mysterious crashes of my main server since upgrading yesterday, one on kernel-2.6.18-92.1.1.el5.x86_64 and the second on kernel-2.6.18-92.1.6.el5.x86_64. Just quietly dies with nothing in the logs. Several other upgraded systems (all i386) seem to be fine. Still searching for any other reports of problems.
Phil
-
fabian dacunha -
jarmo -
John R Pierce -
Kai Schaetzl -
Michael Holmes -
Mogens Kjaer -
Phil Schaffner -
Rudi Ahlers -
Scott Silva -
Sorin Srbu -
Sorin＠Gmail
-
William L. Maltby