Hello,
Sorry if this is somewhat naive, but I'm a little confused as to what the criteria is for that which will get upgraded automatically by yum and what will not.
I see in our logwatch messages from time to time that yum upgraded a bunch of stuff, but I also notice that yum will not upgrade other packages at all (easy example is clamav, but there are others).
Can someone explain or point me to where I can read about the distinction between what is and is not subjected to automatic upgrade?
Thanks!
Sorry if this is somewhat naive, but I'm a little confused as to what the
criteria is for that which will get upgraded automatically by yum and what will
not.
I see in our logwatch messages from time to time that yum upgraded a bunch of
stuff, but I also notice that yum will not upgrade other packages at all (easy
example is clamav, but there are others).
Can someone explain or point me to where I can read about the distinction between what is and is not subjected to automatic upgrade?
More info: yum-updatesd is running and I do not have yum-cron. yum-updatesd does a fine job from what I can tell, but I still cannot understand what criteria it applies to know which packages get upgraded and which do not. (?)
The yum-updatesd configuration file is ultra-simple, so that doesn't seem to be where the update choice/distinction is being made.
There seem to be people posting in various places that they prefer to use yum-cron, but I have no problems with yum-updatesd and I suspect yum-cron wouldn't address/answer my question anyway.
Help?
On Tue, Apr 5, 2011 at 6:14 PM, email builder emailbuilder88@yahoo.com wrote:
Sorry if this is somewhat naive, but I'm a little confused as to what the criteria is for that which will get upgraded automatically by yum and what will not.
I see in our logwatch messages from time to time that yum upgraded a bunch of stuff, but I also notice that yum will not upgrade other packages at all (easy example is clamav, but there are others).
Can someone explain or point me to where I can read about the distinction between what is and is not subjected to automatic upgrade?
More info: yum-updatesd is running and I do not have yum-cron. yum-updatesd does a fine job from what I can tell, but I still cannot understand what criteria it applies to know which packages get upgraded and which do not. (?)
The yum-updatesd configuration file is ultra-simple, so that doesn't seem to be where the update choice/distinction is being made.
There seem to be people posting in various places that they prefer to use yum-cron, but I have no problems with yum-updatesd and I suspect yum-cron wouldn't address/answer my question anyway.
Help?
Yum-updatesd does not automatically install packages (unless you configure it to), it only notifies you of ones that need updating. If no one is manually doing it, and you don't have "do_update = yes" in /etc/yum/yum-updatesd.conf, then you have installed something else that is performing the updates automatically.
Are you sure the updates are actually getting installed, and it's not just noise in the log from yum-updatesd?
// Brian Mathis
P.S. The yum log doesn't have the year in the timestamp, and if it's not active it might not get rotated by logrotate. This can cause false messages sent from logwatch about packages that were installed last year.
Sorry if this is somewhat naive, but I'm a little confused as to what the
criteria is for that which will get upgraded automatically by yum and
what
will not.
I see in our logwatch messages from time to time that yum upgraded a bunch of stuff, but I also notice that yum will not upgrade other packages at all (easy example is clamav, but there are others).
Can someone explain or point me to where I can read about the
distinction
between what is and is not subjected to automatic upgrade?
More info: yum-updatesd is running and I do not have yum-cron.
yum-updatesd
does a fine job from what I can tell, but I still cannot understand what criteria it applies to know which packages get upgraded and which do not.
(?)
The yum-updatesd configuration file is ultra-simple, so that doesn't seem to
be
where the update choice/distinction is being made.
There seem to be people posting in various places that they prefer to use yum-cron, but I have no problems with yum-updatesd and I suspect yum-cron wouldn't address/answer my question anyway.
Help?
Yum-updatesd does not automatically install packages (unless you configure it to), it only notifies you of ones that need updating. If no one is manually doing it, and you don't have "do_update = yes" in /etc/yum/yum-updatesd.conf, then you have installed something else that is performing the updates automatically.
It does look like updates are happening, but it's not clear to me by whom. do_update is set to "no", but notification is by "dbus", so I assumed that "dbus" is notifying another process to do the actual updates. Is there a way I can track that down?
Are you sure the updates are actually getting installed, and it's not just noise in the log from yum-updatesd?
Well, if I can take it at its word, updates *are* happening. Here is a snippet I clipped out of a logwatch a few months ago:
--------------------- yum Begin ------------------------
Packages Updated: php-dba - 5.1.6-27.el5_5.3.i386 php - 5.1.6-27.el5_5.3.i386 php-devel - 5.1.6-27.el5_5.3.i386 php-cli - 5.1.6-27.el5_5.3.i386 php-common - 5.1.6-27.el5_5.3.i386 php-gd - 5.1.6-27.el5_5.3.i386 php-pdo - 5.1.6-27.el5_5.3.i386 php-mysql - 5.1.6-27.el5_5.3.i386
---------------------- yum End -------------------------
P.S. The yum log doesn't have the year in the timestamp, and if it's not active it might not get rotated by logrotate. This can cause false messages sent from logwatch about packages that were installed last year.
Hmm, is there a known fix for this?
On Tue, Apr 5, 2011 at 7:40 PM, email builder emailbuilder88@yahoo.com wrote:
Sorry if this is somewhat naive, but I'm a little confused as to what the criteria is for that which will get upgraded automatically by yum and
what
will not.
I see in our logwatch messages from time to time that yum upgraded a bunch of stuff, but I also notice that yum will not upgrade other packages at all (easy example is clamav, but there are others).
Can someone explain or point me to where I can read about the
distinction
between what is and is not subjected to automatic upgrade?
More info: yum-updatesd is running and I do not have yum-cron.
yum-updatesd
does a fine job from what I can tell, but I still cannot understand what criteria it applies to know which packages get upgraded and which do not.
(?)
The yum-updatesd configuration file is ultra-simple, so that doesn't seem to
be
where the update choice/distinction is being made.
There seem to be people posting in various places that they prefer to use yum-cron, but I have no problems with yum-updatesd and I suspect yum-cron wouldn't address/answer my question anyway.
Help?
Yum-updatesd does not automatically install packages (unless you configure it to), it only notifies you of ones that need updating. If no one is manually doing it, and you don't have "do_update = yes" in /etc/yum/yum-updatesd.conf, then you have installed something else that is performing the updates automatically.
It does look like updates are happening, but it's not clear to me by whom. do_update is set to "no", but notification is by "dbus", so I assumed that "dbus" is notifying another process to do the actual updates. Is there a way I can track that down?
Are you sure the updates are actually getting installed, and it's not just noise in the log from yum-updatesd?
Well, if I can take it at its word, updates *are* happening. Here is a snippet I clipped out of a logwatch a few months ago:
--------------------- yum Begin ------------------------
Packages Updated: php-dba - 5.1.6-27.el5_5.3.i386 php - 5.1.6-27.el5_5.3.i386 php-devel - 5.1.6-27.el5_5.3.i386 php-cli - 5.1.6-27.el5_5.3.i386 php-common - 5.1.6-27.el5_5.3.i386 php-gd - 5.1.6-27.el5_5.3.i386 php-pdo - 5.1.6-27.el5_5.3.i386 php-mysql - 5.1.6-27.el5_5.3.i386
---------------------- yum End -------------------------
P.S. The yum log doesn't have the year in the timestamp, and if it's not active it might not get rotated by logrotate. This can cause false messages sent from logwatch about packages that were installed last year.
Hmm, is there a known fix for this?
Rotate the log file yourself once a year. You can check if you are seeing this bug by looking at the /var/log/yum.log last modified time. If it was yesterday, then I suppose the packages were installed.
As far as your other questions, how does it determine what packages to update, I think you will find it's not actually doing any updating. I have not used yum-updatesd to auto-update packages myself, but I would think it would automatically install any updated package.
// Brian Mathis
Sorry if this is somewhat naive, but I'm a little confused as to what
the
criteria is for that which will get upgraded automatically by yum and
what
will not.
I see in our logwatch messages from time to time that yum upgraded a bunch of stuff, but I also notice that yum will not upgrade other packages at all (easy example is clamav, but there are others).
Can someone explain or point me to where I can read about the
distinction
between what is and is not subjected to automatic upgrade?
More info: yum-updatesd is running and I do not have yum-cron.
yum-updatesd
does a fine job from what I can tell, but I still cannot understand
what
criteria it applies to know which packages get upgraded and which do
not.
(?)
The yum-updatesd configuration file is ultra-simple, so that doesn't
seem to
be
where the update choice/distinction is being made.
There seem to be people posting in various places that they prefer to
use
yum-cron, but I have no problems with yum-updatesd and I suspect
yum-cron
wouldn't address/answer my question anyway.
Help?
Yum-updatesd does not automatically install packages (unless you configure it to), it only notifies you of ones that need updating. If no one is manually doing it, and you don't have "do_update = yes" in /etc/yum/yum-updatesd.conf, then you have installed something else that is performing the updates automatically.
It does look like updates are happening, but it's not clear to me by whom. do_update is set to "no", but notification is by "dbus", so I assumed that "dbus" is notifying another process to do the actual updates. Is there a
way I
can track that down?
Are you sure the updates are actually getting installed, and it's not just noise in the log from yum-updatesd?
Well, if I can take it at its word, updates *are* happening. Here is a
snippet
I clipped out of a logwatch a few months ago:
--------------------- yum Begin ------------------------
Packages Updated: php-dba - 5.1.6-27.el5_5.3.i386 php - 5.1.6-27.el5_5.3.i386 php-devel - 5.1.6-27.el5_5.3.i386 php-cli - 5.1.6-27.el5_5.3.i386 php-common - 5.1.6-27.el5_5.3.i386 php-gd - 5.1.6-27.el5_5.3.i386 php-pdo - 5.1.6-27.el5_5.3.i386 php-mysql - 5.1.6-27.el5_5.3.i386
---------------------- yum End -------------------------
P.S. The yum log doesn't have the year in the timestamp, and if it's not active it might not get rotated by logrotate. This can cause false messages sent from logwatch about packages that were installed last year.
Hmm, is there a known fix for this?
Rotate the log file yourself once a year. You can check if you are seeing this bug by looking at the /var/log/yum.log last modified time. If it was yesterday, then I suppose the packages were installed.
As far as your other questions, how does it determine what packages to update, I think you will find it's not actually doing any updating. I have not used yum-updatesd to auto-update packages myself, but I would think it would automatically install any updated package.
It's dated a couple days ago, so I'd say it's doing what it's supposed to. I'm not sure what the "dbus" notification does, but I presume it's telling someone to do the updating. It'd probably be more informative if I could understand who is picking up such notifications.
Do you know how to determine which repo a particular package is from? For example, when I do "yum info" against clamav (which isn't receiving automatic updates), it just says "Repo: installed". I don't know what repo it comes from.
Thanks much
Sorry if this is somewhat naive, but I'm a little confused as to
what
the
criteria is for that which will get upgraded automatically by yum
and
what
will not.
I see in our logwatch messages from time to time that yum upgraded a bunch of stuff, but I also notice that yum will not upgrade
other
packages at all (easy example is clamav, but there are others).
Can someone explain or point me to where I can read about the
distinction
between what is and is not subjected to automatic upgrade?
More info: yum-updatesd is running and I do not have yum-cron.
yum-updatesd
does a fine job from what I can tell, but I still cannot understand
what
criteria it applies to know which packages get upgraded and which do
not.
(?)
The yum-updatesd configuration file is ultra-simple, so that doesn't
seem to
be
where the update choice/distinction is being made.
There seem to be people posting in various places that they prefer to
use
yum-cron, but I have no problems with yum-updatesd and I suspect
yum-cron
wouldn't address/answer my question anyway.
Help?
Yum-updatesd does not automatically install packages (unless you configure it to), it only notifies you of ones that need updating.
If
no one is manually doing it, and you don't have "do_update = yes" in /etc/yum/yum-updatesd.conf, then you have installed something else that is performing the updates automatically.
It does look like updates are happening, but it's not clear to me by
whom.
do_update is set to "no", but notification is by "dbus", so I assumed
that
"dbus" is notifying another process to do the actual updates. Is there a
way I
can track that down?
Are you sure the updates are actually getting installed, and it's not just noise in the log from yum-updatesd?
Well, if I can take it at its word, updates *are* happening. Here is a
snippet
I clipped out of a logwatch a few months ago:
--------------------- yum Begin ------------------------
Packages Updated: php-dba - 5.1.6-27.el5_5.3.i386 php - 5.1.6-27.el5_5.3.i386 php-devel - 5.1.6-27.el5_5.3.i386 php-cli - 5.1.6-27.el5_5.3.i386 php-common - 5.1.6-27.el5_5.3.i386 php-gd - 5.1.6-27.el5_5.3.i386 php-pdo - 5.1.6-27.el5_5.3.i386 php-mysql - 5.1.6-27.el5_5.3.i386
---------------------- yum End -------------------------
P.S. The yum log doesn't have the year in the timestamp, and if it's not active it might not get rotated by logrotate. This can cause false messages sent from logwatch about packages that were installed last year.
Hmm, is there a known fix for this?
Rotate the log file yourself once a year. You can check if you are seeing this bug by looking at the /var/log/yum.log last modified time. If it was yesterday, then I suppose the packages were installed.
As far as your other questions, how does it determine what packages to update, I think you will find it's not actually doing any updating. I have not used yum-updatesd to auto-update packages myself, but I would think it would automatically install any updated package.
It's dated a couple days ago, so I'd say it's doing what it's supposed to. I'm
not sure what the "dbus" notification does, but I presume it's telling someone
to do the updating. It'd probably be more informative if I could understand who
is picking up such notifications.
/etc/dbus-1/system.d/yum-updatesd.conf
Doesn't really tell me anything. I'm guessing that someone is watching dbus for notifications, but I can't figure out how to see who that is.
Do you know how to determine which repo a particular package is from? For example, when I do "yum info" against clamav (which isn't receiving automatic
updates), it just says "Repo: installed". I don't know what repo it comes from.
email builder wrote:
Do you know how to determine which repo a particular package is from? For example, when I do "yum info" against clamav (which isn't receiving automatic updates), it just says "Repo: installed". I don't know what repo it comes from.
"yum list clamav --showduplicates" should show you all clamav packages available in all repos, and will show the installed version so you can compare.
Also, do you have some software that could do updates automaticaly? I think Virtualmin (like Webmin but for domain control, CPanel, etc.) can be set to do automatic updates.
Ljubomir
Do you know how to determine which repo a particular package is from? For example, when I do "yum info" against clamav (which isn't receiving
automatic
updates), it just says "Repo: installed". I don't know what repo it comes
from.
"yum list clamav --showduplicates" should show you all clamav packages available in all repos, and will show the installed version so you can compare.
Hmmm Command line error: no such option: --showduplicates
Also, do you have some software that could do updates automaticaly? I think Virtualmin (like Webmin but for domain control, CPanel, etc.) can be set to do automatic updates.
I'm not looking for an auto-update system, I'm just trying to understand the one that is currently running (yum-updatesd and whomever is listening on the other end of dbus).
It seems to work for the most part, but I want to understand why some packages don't get upgraded. A partial answer I got to that was that such packages would be from non-enabled repos, but when I do a "yum upgrade clamav" from the command line, it works fine -- doesn't that mean that the repo *IS* enabled?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of email builder Sent: Tuesday, April 05, 2011 19:41 To: CentOS mailing list Subject: Re: [CentOS] Understanding yum automatic upgrades
It does look like updates are happening, but it's not clear to me by whom. do_update is set to "no", but notification is by "dbus", so I assumed that "dbus" is notifying another process to do the actual updates. Is
there
a way I can track that down?
Are you sure the updates are actually getting installed, and it's
not
just noise in the log from yum-updatesd?
Well, if I can take it at its word, updates *are* happening. Here is
a
snippet I clipped out of a logwatch a few months ago:
--------------------- yum Begin ------------------------
Packages Updated: php-dba - 5.1.6-27.el5_5.3.i386 php - 5.1.6-27.el5_5.3.i386 php-devel - 5.1.6-27.el5_5.3.i386 php-cli - 5.1.6-27.el5_5.3.i386 php-common - 5.1.6-27.el5_5.3.i386 php-gd - 5.1.6-27.el5_5.3.i386 php-pdo - 5.1.6-27.el5_5.3.i386 php-mysql - 5.1.6-27.el5_5.3.i386
---------------------- yum End -------------------------
A much more reliable way to check is rpm -qa --last |less or simply run yum update and see what it thinks needs updated yet.
If things are reasonably up-to-date I would expect the --last list to have a tzdata-2011b package listed near the top. One other thing the --last list will revel is WHEN the updates were applied, if they consistently are at a particular time of the morning then it may be based on a cron job.
It does look like updates are happening, but it's not clear to me by
whom. do_update is set to "no", but notification is by "dbus", so I assumed that "dbus" is notifying another process to do the actual updates. Is
there
a way I can track that down?
Are you sure the updates are actually getting installed, and it's
not
just noise in the log from yum-updatesd?
Well, if I can take it at its word, updates *are* happening. Here is
a
snippet I clipped out of a logwatch a few months ago:
--------------------- yum Begin ------------------------
Packages Updated: php-dba - 5.1.6-27.el5_5.3.i386 php - 5.1.6-27.el5_5.3.i386 php-devel - 5.1.6-27.el5_5.3.i386 php-cli - 5.1.6-27.el5_5.3.i386 php-common - 5.1.6-27.el5_5.3.i386 php-gd - 5.1.6-27.el5_5.3.i386 php-pdo - 5.1.6-27.el5_5.3.i386 php-mysql - 5.1.6-27.el5_5.3.i386
---------------------- yum End -------------------------
A much more reliable way to check is rpm -qa --last |less
Thanks for that. I think this clears things up -- it looks like the updates are all manual ones, especially judging from how dates are grouped.
So I must apologize to you and the other responders on this thread. The notifications I have seen in logwatch must have been from manual updates that I was unaware of or did not remember.
or simply run yum update and see what it thinks needs updated yet.
If things are reasonably up-to-date I would expect the --last list to have a tzdata-2011b package listed near the top.
Indeed, it's not there yet I see an update available.
One other thing the --last list will revel is WHEN the updates were applied, if they consistently are at a particular time of the morning then it may be based on a cron job.
The date/times appear to indicate manual interaction from a human. In any case, my question seems to be answered. I will watch logwatch a little longer and make sure this is the case.
Thanks to everyone and sorry for the confusion.
Simple answer: yum update will update *all* packages in the repo's that are *enabled*.
Kai
email builder wrote:
Hello,
Sorry if this is somewhat naive, but I'm a little confused as to what the criteria is for that which will get upgraded automatically by yum and what will not.
I see in our logwatch messages from time to time that yum upgraded a bunch of stuff, but I also notice that yum will not upgrade other packages at all (easy example is clamav, but there are others).
Can someone explain or point me to where I can read about the distinction between what is and is not subjected to automatic upgrade?
Automatic upgrade (if "yum upgrade" is run), will upgrade all newer rpm packages that are in *enabled* repositories. If you installed from external repository that you keep disabled, those packages will not be automatically upgraded.
Ljubomir
Sorry if this is somewhat naive, but I'm a little confused as to what the
criteria is for that which will get upgraded automatically by yum and what
will
not.
I see in our logwatch messages from time to time that yum upgraded a bunch
of
stuff, but I also notice that yum will not upgrade other packages at all
(easy
example is clamav, but there are others).
Can someone explain or point me to where I can read about the distinction
between what is and is not subjected to automatic upgrade?
Automatic upgrade (if "yum upgrade" is run), will upgrade all newer rpm packages that are in *enabled* repositories. If you installed from external repository that you keep disabled, those packages will not be automatically upgraded.
Well, as I mentioned, yum-updatesd is running and doing the automatic updates. I'm specifically referring to the automatic updates and not manual command line updates by me.
But assuming that yum-updatesd does the same thing as "yum upgrade" (how do I confirm this?), then the outstanding question is how to figure out why certain packages are not being updated.
To take my easy example, clamav, when I need to update clamav, I have to go to the command line and do a "yum upgrade clamav" and it works as expected. Doesn't that mean its repo is enabled? If so, why isn't yum-updatesd updating it for me? If not, how do I find which repo it's coming from so I can enable it? (yum info just says "installed" for the "Repo" field).
TIA!
Email builder wrote on Tue, 5 Apr 2011 16:46:55 -0700 (PDT):
then the outstanding question is how to figure out why certain packages are not being updated.
Well, first action: did you actually check with the repo that there is a newer package? Just because a package isn't updated doesn't mean it's not working. Especially in the case of clamav I think you haven't done the obvious. Please read before continuing: http://wiki.centos.org/AdditionalResources http://wiki.centos.org/PackageManagement/Yum
Kai
then the outstanding question is how to figure out why certain
packages are not being updated.
Well, first action: did you actually check with the repo that there is a newer package?
Yes. I'm not sure why would you think otherwise...?
Just because a package isn't updated doesn't mean it's not working.
I *do* think the updater is working, judging from my logwatch emails. But it's quite clear that some packages, clamav being the example here, are definitely not being updated.
Especially in the case of clamav I think you haven't done the obvious.
Why do you say that? What is the obvious? Checking for an update?
Perhaps what would clear this up for you is to note that this is an ongoing issue, not anything *right now*. That is, I've watched clam tell me via logwatch that it is out of date for weeks at a time before I finally go log in and run "yum update clamav" on the command line, which updates things nicely as expected. So clearly in those cases there IS an update available (I also check via "yum info" before the update).
So while *some* packages get updated automatically by some mystery process that no one here seems to know about (??), some *do not*.
Please don't take me wrong; I'm grateful for the help, but while I'm not a highly skilled sysadmin, I'm not asking entirely bonehead questions I think. Correct me if I'm wrong though! :-)
-
Brian Mathis -
Denniston, Todd A CIV NAVSURFWARCENDIV Crane -
email builder -
Kai Schaetzl -
Ljubomir Ljubojevic