Hi folks,
I have a production server that's currently running 5.0 with all updates. What's the easiest, or perhaps best way to upgrade it to 5.1, with minimal down time? The downtime is critical, so I need to have it be a short as possible. I can live with an hour or two, but larger is going to be a pain.
Suggestions?
On Wed, Mar 5, 2008 at 11:58 AM, Ashley M. Kirchner ashley@pcraft.com wrote:
I have a production server that's currently running 5.0 with allupdates. What's the easiest, or perhaps best way to upgrade it to 5.1, with minimal down time? The downtime is critical, so I need to have it be a short as possible. I can live with an hour or two, but larger is going to be a pain.
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
If you're unsure if you actually are running centos 5.1, run 'rpm -q centos-release' and you should see 5.1.0- in the release string.
Jim Perrin wrote:
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
Nope, I don't run yum. I do manual updates. So I've rsynced the updates to a local drives, and then ran rpm against them. There's something about running un-attended updates on a life system. I've had too many cases where I come into the office in the morning and the system is dead because of some update overnight.
Ashley M. Kirchner wrote:
Jim Perrin wrote:
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
Nope, I don't run yum. I do manual updates. So I've rsynced the updates to a local drives, and then ran rpm against them. There's something about running un-attended updates on a life system. I've had too many cases where I come into the office in the morning and the system is dead because of some update overnight.
What is it about yum that make you think it needs to be unattended?
On Wed, Mar 5, 2008 at 9:17 AM, Ashley M. Kirchner ashley@pcraft.com wrote:
Jim Perrin wrote:
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
Nope, I don't run yum. I do manual updates. So I've rsynced the updates to a local drives, and then ran rpm against them. There's something about running un-attended updates on a life system. I've had too many cases where I come into the office in the morning and the system is dead because of some update overnight.
Fascinating - I've always had to run yum manually, and I've never seen an overnight update on my system.
Are you sure you don't have rogue administrators sneaking in at night and 'yup'ing?
(Okay, that wasn't a serious suggestion, but your issue seems kind of strange...)
Just my $0.02.
mhr
MHR wrote:
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
Nope, I don't run yum. I do manual updates. So I've rsynced the updates to a local drives, and then ran rpm against them. There's something about running un-attended updates on a life system. I've had too many cases where I come into the office in the morning and the system is dead because of some update overnight.
Fascinating - I've always had to run yum manually, and I've never seen an overnight update on my system.
Are you sure you don't have rogue administrators sneaking in at night and 'yup'ing?
(Okay, that wasn't a serious suggestion, but your issue seems kind of strange...)
Just my $0.02.
Yes, aside from being able to run yum manually while still letting it do all the work, when has anyone seen a Centos system die from an update? I know it's theoretically possible and I baby-sit the critical systems too (at least the first on each hardware type), but this stuff is pretty well tested before being pushed out.
on 3-5-2008 11:20 AM Les Mikesell spake the following:
MHR wrote:
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
Nope, I don't run yum. I do manual updates. So I've rsynced the updates to a local drives, and then ran rpm against them. There's something about running un-attended updates on a life system. I've had too many cases where I come into the office in the morning and the system is dead because of some update overnight.
Fascinating - I've always had to run yum manually, and I've never seen an overnight update on my system.
Are you sure you don't have rogue administrators sneaking in at night and 'yup'ing?
(Okay, that wasn't a serious suggestion, but your issue seems kind of strange...)
Just my $0.02.
Yes, aside from being able to run yum manually while still letting it do all the work, when has anyone seen a Centos system die from an update? I know it's theoretically possible and I baby-sit the critical systems too (at least the first on each hardware type), but this stuff is pretty well tested before being pushed out.
While I haven't seen an entire system go down from an update, I have seen software stop working due to a perl module update. But to be fair, that also involved a third-party repo.
Les Mikesell wrote:
when has anyone seen a Centos system die from an update?
Just a few months ago, one of the Samba updates caused it to drop all our Windows systems' mapped drives every 10 minutes or so. You'd be in the middle of a big copy, and boom, there goes your share, and you have to start again. I don't remember what eventually fixed it. If I hadn't been here to do fire fighting, it could have gotten ugly.
on 3-5-2008 9:17 AM Ashley M. Kirchner spake the following:
Jim Perrin wrote:
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
Nope, I don't run yum. I do manual updates. So I've rsynced the updates to a local drives, and then ran rpm against them. There's something about running un-attended updates on a life system. I've had too many cases where I come into the office in the morning and the system is dead because of some update overnight.
Yum update "is" a manual process unless you specifically enable it to run nightly.
Ashley M. Kirchner escribió:
Jim Perrin wrote:
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
Nope, I don't run yum. I do manual updates. So I've rsynced the updates to a local drives, and then ran rpm against them. There's something about running un-attended updates on a life system. I've had too many cases where I come into the office in the morning and the system is dead because of some update overnight.
Never automate the updates. Do them manually, using yum, and selecting the packages you are interested in.
Martin Marques wrote:
If you've been running yum update, you're already at 5.1. You may just need to reboot to load the new kernel.
Nope, I don't run yum. I do manual updates. So I've rsynced the updates to a local drives, and then ran rpm against them. There's something about running un-attended updates on a life system. I've had too many cases where I come into the office in the morning and the system is dead because of some update overnight.
Never automate the updates. Do them manually, using yum, and selecting the packages you are interested in.
For updates you probably want all the packages. If someone has gone to the trouble to backport fixes into these versions and roll out the updates there are probably very good reasons to apply them. But, if machine is really critical it might be a good idea to have a similar setup for testing first. Updates normally preserve your running kernel, so you can boot back to that easily, but the others would be hard to back out. Or, just watch this list for a short time after major updates are available before you apply them yourself. If anything breaks, you'll likely see a discussion of the problem here.
On Wed, Mar 05, 2008 at 09:58:27AM -0700, Ashley M. Kirchner enlightened us:
Hi folks,
I have a production server that's currently running 5.0 with all updates. What's the easiest, or perhaps best way to upgrade it to 5.1, with minimal down time? The downtime is critical, so I need to have it be a short as possible. I can live with an hour or two, but larger is going to be a pain.
Suggestions?
5.0 with all updates is equal to 5.1 with all updates. So probably all you have to do is reboot to the latest kernel.
Unless you've changed the default yum repo files to stay at 5.0 for some reason, you should already be at 5.1.
Matt
Yum upgrade....
john
Ashley M. Kirchner wrote:
Hi folks,
I have a production server that's currently running 5.0 with all updates. What's the easiest, or perhaps best way to upgrade it to 5.1, with minimal down time? The downtime is critical, so I need to have it be a short as possible. I can live with an hour or two, but larger is going to be a pain.
Suggestions?
Ashley M. Kirchner wrote:
Hi folks,
I have a production server that's currently running 5.0 with all updates. What's the easiest, or perhaps best way to upgrade it to 5.1, with minimal down time? The downtime is critical, so I need to have it be a short as possible. I can live with an hour or two, but larger is going to be a pain.
Suggestions?
As others have mentioned, you are probably already there, but I'd do: yum install yum-downloadonly yum -y --downloadonly update to pull in anything new but not install it. You can repeat the 2nd command if it doesn't complete or if some time passes before you get around to doing the yum install which will go quickly with all the packages already downloaded. You really only have downtime if you need to reboot and you only need to reboot if you pick up a new kernel in the update.
-
Ashley M. Kirchner -
Jim Perrin -
John Plemons -
Les Mikesell -
Martin Marques -
Matt Hyclak -
MHR -
Niki Kovacs -
Scott Silva -
Warren Young