Running "yum update", yum appears to perform fine and appears to finish but continues to reside in memory:
... Updating : lftp 2/4 Cleanup : lftp 3/4 Cleanup : freetype 4/4
Updated: freetype.i386 0:2.2.1-25.el5_5 lftp.i386 0:3.7.11-4.el5_5.3
Complete! # ps -ef|grep yum root 1384 1336 0 06:21 pts/0 00:00:00 grep yum root 2229 1 0 Jul06 ? 00:00:11 /usr/bin/python -tt /usr/sbin/yum-updatesd ....
Running the above "ps -ef|grep yum" again after composing this email, process 2229 is still running (several minutes later). And this machine isn't particularly busy:
# vmstat procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------ r b swpd free buff cache si so bi bo in cs us sy id wa st 0 0 64 42268 73752 139556 0 0 0 2 8 4 1 0 99 0 0
From: ken gebser@mousecar.com
Running "yum update", yum appears to perform fine and appears to finish but continues to reside in memory: Complete! # ps -ef|grep yum root 1384 1336 0 06:21 pts/0 00:00:00 grep yum root 2229 1 0 Jul06 ? 00:00:11 /usr/bin/python -tt /usr/sbin/yum-updatesd ....
yum-updatesd is not yum. man yum-updatesd
JD
On 08/03/2010 06:52 AM John Doe wrote:
From: ken gebser@mousecar.com
....
yum-updatesd is not yum. man yum-updateeresd
JD
Thanks, JD. Sorry, I copy-and-pasted from the wrong machine.
Trying again: it's happened to me a few times now that when I run "yum update", it fails like this:
The other application is: yum-updatesd-he Memory : 31 M RSS ( 74 MB VSZ) Started: Tue Aug 3 04:40:05 2010 - 1:25:42 ago State : Running, pid: 32006 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum-updatesd-he Memory : 31 M RSS ( 74 MB VSZ) Started: Tue Aug 3 04:40:05 2010 - 1:25:44 ago State : Running, pid: 32006 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum-updatesd-he Memory : 31 M RSS ( 74 MB VSZ) Started: Tue Aug 3 04:40:05 2010 - 1:25:46 ago State : Running, pid: 32006 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum-updatesd-he Memory : 31 M RSS ( 74 MB VSZ) Started: Tue Aug 3 04:40:05 2010 - 1:25:48 ago State : Running, pid: 32006
Exiting on user cancel.
# ps -ef|grep yum root 864 3195 0 06:06 pts/1 00:00:00 grep yum root 2632 1 0 Jul27 ? 00:05:13 /usr/bin/python -tt /usr/sbin/yum-updatesd root 32006 2632 1 04:40 ? 00:00:54 /usr/bin/python -tt /usr/libexec/yum-updatesd-helper --check --dbus
After killing 32006, then 2632, "yum update" ran fine. (Perhaps I didn't need to kill the second one... 2632. Dunno.)
ken wrote:
On 08/03/2010 06:52 AM John Doe wrote:
From: ken gebser@mousecar.com
....
<snip>
Trying again: it's happened to me a few times now that when I run "yum update", it fails like this:
The other application is: yum-updatesd-he Memory : 31 M RSS ( 74 MB VSZ) Started: Tue Aug 3 04:40:05 2010 - 1:25:42 ago State : Running, pid: 32006 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum-updatesd-he Memory : 31 M RSS ( 74 MB VSZ) Started: Tue Aug 3 04:40:05 2010 - 1:25:44 ago State : Running, pid: 32006
<snip>
# ps -ef|grep yum root 864 3195 0 06:06 pts/1 00:00:00 grep yum root 2632 1 0 Jul27 ? 00:05:13 /usr/bin/python -tt /usr/sbin/yum-updatesd root 32006 2632 1 04:40 ? 00:00:54 /usr/bin/python -tt /usr/libexec/yum-updatesd-helper --check --dbus
After killing 32006, then 2632, "yum update" ran fine. (Perhaps I didn't need to kill the second one... 2632. Dunno.)
Yep - if any version of yum is running, no other will. At work, I do *not* have yum-updatesd turned up - I want to control when and what. Certainly, I don't want to update, say, firefox while folks are using it on their desktops. And some managers are rather picky as to what servers get updated, and when, esp. their production boxes. So, it's tedious, but I have control - yum runs when I run it, and not otherwise.
mark
On Tue, 2010-08-03 at 09:51 -0400, m.roth@5-cent.us wrote:
ken wrote:
On 08/03/2010 06:52 AM John Doe wrote:
From: ken gebser@mousecar.com
....
<snip> > Trying again: it's happened to me a few times now that when I run "yum > update", it fails like this: > > The other application is: yum-updatesd-he > Memory : 31 M RSS ( 74 MB VSZ) > Started: Tue Aug 3 04:40:05 2010 - 1:25:42 ago > State : Running, pid: 32006 > Another app is currently holding the yum lock; waiting for it to exit... > The other application is: yum-updatesd-he > Memory : 31 M RSS ( 74 MB VSZ) > Started: Tue Aug 3 04:40:05 2010 - 1:25:44 ago > State : Running, pid: 32006 <snip> > # ps -ef|grep yum > root 864 3195 0 06:06 pts/1 00:00:00 grep yum > root 2632 1 0 Jul27 ? 00:05:13 /usr/bin/python -tt > /usr/sbin/yum-updatesd > root 32006 2632 1 04:40 ? 00:00:54 /usr/bin/python -tt > /usr/libexec/yum-updatesd-helper --check --dbus > > After killing 32006, then 2632, "yum update" ran fine. (Perhaps I > didn't need to kill the second one... 2632. Dunno.)
Yep - if any version of yum is running, no other will. At work, I do *not* have yum-updatesd turned up - I want to control when and what. Certainly, I don't want to update, say, firefox while folks are using it on their desktops. And some managers are rather picky as to what servers get updated, and when, esp. their production boxes. So, it's tedious, but I have control - yum runs when I run it, and not otherwise.
--- Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
John
On 08/03/2010 10:19 AM JohnS wrote:
On Tue, 2010-08-03 at 09:51 -0400, m.roth@5-cent.us wrote:
ken wrote:
On 08/03/2010 06:52 AM John Doe wrote:
....
Yep - if any version of yum is running, no other will. At work, I do *not* have yum-updatesd turned up - I want to control when and what. Certainly, I don't want to update, say, firefox while folks are using it on their desktops. And some managers are rather picky as to what servers get updated, and when, esp. their production boxes. So, it's tedious, but I have control - yum runs when I run it, and not otherwise.
Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
So is there a way to configure yum and/or yum-updatesd so that I get a GUI notice that updates are available, but then run the actual update when I want from the CLI?
On 8/3/2010 11:27 AM, ken wrote:
On 08/03/2010 10:19 AM JohnS wrote:
On Tue, 2010-08-03 at 09:51 -0400, m.roth@5-cent.us wrote:
ken wrote:
On 08/03/2010 06:52 AM John Doe wrote:
....
Yep - if any version of yum is running, no other will. At work, I do *not* have yum-updatesd turned up - I want to control when and what. Certainly, I don't want to update, say, firefox while folks are using it on their desktops. And some managers are rather picky as to what servers get updated, and when, esp. their production boxes. So, it's tedious, but I have control - yum runs when I run it, and not otherwise.
Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
So is there a way to configure yum and/or yum-updatesd so that I get a GUI notice that updates are available, but then run the actual update when I want from the CLI?
Run 'yum check-update' as a cron job.
On Tue, 2010-08-03 at 11:30 -0400, Bowie Bailey wrote:
On 8/3/2010 11:27 AM, ken wrote:
On 08/03/2010 10:19 AM JohnS wrote:
On Tue, 2010-08-03 at 09:51 -0400, m.roth@5-cent.us wrote:
ken wrote:
On 08/03/2010 06:52 AM John Doe wrote:
....
Yep - if any version of yum is running, no other will. At work, I do *not* have yum-updatesd turned up - I want to control when and what. Certainly, I don't want to update, say, firefox while folks are using it on their desktops. And some managers are rather picky as to what servers get updated, and when, esp. their production boxes. So, it's tedious, but I have control - yum runs when I run it, and not otherwise.
Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
So is there a way to configure yum and/or yum-updatesd so that I get a GUI notice that updates are available, but then run the actual update when I want from the CLI?
Run 'yum check-update' as a cron job.
--- And then | tee it >> out to /var/log/yum/check_update.log
John
JohnS wrote:
On Tue, 2010-08-03 at 11:30 -0400, Bowie Bailey wrote:
On 8/3/2010 11:27 AM, ken wrote:
On 08/03/2010 10:19 AM JohnS wrote:
On Tue, 2010-08-03 at 09:51 -0400, m.roth@5-cent.us wrote:
ken wrote:
On 08/03/2010 06:52 AM John Doe wrote: > ....
Yep - if any version of yum is running, no other will. At work, I do
<snip>
desktops. And some managers are rather picky as to what servers get updated, and when, esp. their production boxes. So, it's tedious, but I have control - yum runs when I run it, and not otherwise.
<snip>
So is there a way to configure yum and/or yum-updatesd so that I get a GUI notice that updates are available, but then run the actual update when I want from the CLI?
Run 'yum check-update' as a cron job.
And then | tee it >> out to /var/log/yum/check_update.log
or | mail -s "Yum updates available" <youremail>
mark
On 8/3/2010 12:12 PM, m.roth@5-cent.us wrote:
JohnS wrote:
On Tue, 2010-08-03 at 11:30 -0400, Bowie Bailey wrote:
On 8/3/2010 11:27 AM, ken wrote:
So is there a way to configure yum and/or yum-updatesd so that I get a GUI notice that updates are available, but then run the actual update when I want from the CLI?
Run 'yum check-update' as a cron job.
And then | tee it >> out to /var/log/yum/check_update.log
or | mail -s "Yum updates available" <youremail>
By default, cron will already email the output. You can set MAILTO at the top of the crontab to control who the emails go to.
On 08/03/2010 11:30 AM Bowie Bailey wrote:
On 8/3/2010 11:27 AM, ken wrote:
On 08/03/2010 10:19 AM JohnS wrote:
On Tue, 2010-08-03 at 09:51 -0400, m.roth@5-cent.us wrote:
ken wrote:
On 08/03/2010 06:52 AM John Doe wrote:
....
Yep - if any version of yum is running, no other will. At work, I do *not* have yum-updatesd turned up - I want to control when and what. Certainly, I don't want to update, say, firefox while folks are using it on their desktops. And some managers are rather picky as to what servers get updated, and when, esp. their production boxes. So, it's tedious, but I have control - yum runs when I run it, and not otherwise.
Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
So is there a way to configure yum and/or yum-updatesd so that I get a GUI notice that updates are available, but then run the actual update when I want from the CLI?
Run 'yum check-update' as a cron job.
yum-updatesd lights up a GUI notification. Can 'yum check-update' do this?
On Tue, 2010-08-03 at 12:18 -0400, ken wrote:
On 08/03/2010 11:30 AM Bowie Bailey wrote:
On 8/3/2010 11:27 AM, ken wrote:
On 08/03/2010 10:19 AM JohnS wrote:
On Tue, 2010-08-03 at 09:51 -0400, m.roth@5-cent.us wrote:
ken wrote:
On 08/03/2010 06:52 AM John Doe wrote: > ....
Yep - if any version of yum is running, no other will. At work, I do *not* have yum-updatesd turned up - I want to control when and what. Certainly, I don't want to update, say, firefox while folks are using it on their desktops. And some managers are rather picky as to what servers get updated, and when, esp. their production boxes. So, it's tedious, but I have control - yum runs when I run it, and not otherwise.
Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
So is there a way to configure yum and/or yum-updatesd so that I get a GUI notice that updates are available, but then run the actual update when I want from the CLI?
Run 'yum check-update' as a cron job.
yum-updatesd lights up a GUI notification. Can 'yum check-update' do this?
--- No, your out of luck there. I'm sure that would not be a hard hack though.
John
On Tue, Aug 3, 2010 at 7:19 AM, JohnS jses27@gmail.com wrote:
Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
Oh? I run yum-updatesd as a service (by dafult, not by any specific intent), but as far as I can tell, it has never interfered with me running a yum update.
Mark
Mark wrote:
On Tue, Aug 3, 2010 at 7:19 AM, JohnS jses27@gmail.com wrote:
Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
Oh? I run yum-updatesd as a service (by dafult, not by any specific intent), but as far as I can tell, it has never interfered with me running a yum update.
Presumably because it's doing it overnight, and is done. You cannot run yum while it's running - they both want the same locks, and both are updating the same database. Bad, and so they prevent you from doing so.
mark
On Tue, 2010-08-03 at 14:33 -0400, m.roth@5-cent.us wrote:
Mark wrote:
On Tue, Aug 3, 2010 at 7:19 AM, JohnS jses27@gmail.com wrote:
Ahh as long as yum-updated is running as a service regular yum update will not run! IE, you killed the yum-updatesd service and that is why yum update ran.
Oh? I run yum-updatesd as a service (by dafult, not by any specific intent), but as far as I can tell, it has never interfered with me running a yum update.
Presumably because it's doing it overnight, and is done. You cannot run yum while it's running - they both want the same locks, and both are updating the same database. Bad, and so they prevent you from doing so.
mark
Right also you can and will some day in time hit the same problem but using rpm to do various queries will throw up the same error when using yum because of the db lock. I do not for see regular users encountering this problem but heavy rpm -q, qa ,qi ,qiR, qf | grep foo will indeed. I encounter it a lot of times especially when using multiple terminal windows. So I have to kill pid{rpm}.
John
-
Bowie Bailey -
John Doe -
JohnS -
ken -
m.roth＠5-cent.us -
Mark