Discussion:
[Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are
Alan Pittman
2015-03-30 18:01:59 UTC
Permalink
Hi,
I'm having an issue with Spacewalk 2.0. I have two RHEL6 x86_64 servers that the Spacewalk GUI reports that there are available updates. However, if I run yum on these two machines, nothing is reported as being available for updating. I've done some Google searches and this has been an issue in the past for some individuals and occasionally the problem has been fixed by running yum clean all, followed by deleting the /var/cache/yum directory. Then a yum makecache. . I tried this and it didn't helped. I have also tried deleting the profile for the server and attempting a re-register. That didn't work either. If anyone has any ideas/suggestions, I would like to hear them.

Some other information that might be beneficial (I think):

- All updates have been performed using yum. No rpm --install or --upgrade has been performed.
- Since I had deleted and re-registered the client, I didn't think rhn-profile-sync would do any good, but I tried it anyhow. It didn't help.
- a complete shutdown of the Spacewalk server application and it's corresponding postgres database was also attempted, again to avail.
- attempting to update the client from the Spacewalk GUI does not work. The schedule task just goes into a pending state and never occurs.

Any suggestions would be appreciated.

Alan

Unix is user friendly. It’s just very selective about who its friends are.
p***@gmail.com
2015-03-31 04:21:29 UTC
Permalink
_______________________________________________
Spacewalk-list mailing list
Spacewalk-***@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Kobus Bensch
2015-03-31 08:42:04 UTC
Permalink
I had this issue. I fixed it by running a repo sync manually.
Try running rhn-profile-sync on the box in question then looking in
the GUI again. This can happen if some one does a manual update in yum
and does not run that command afterward.
Its well documented in the install procedure for every red hat errata‎
that you have to run that command after a yum update. You may also
want to consider adding cron.daily job to do this with anacron that
should execute it every day at a semi randomized time so you won't
over laod your spacewalk server and the added load to the host while
running it is negligible so it should not impact the performance of
the applications you are running unless the box is already severly
overloaded to begin with.
Sent from my BlackBerry 10 smartphone.
*From: *Alan Pittman
*Sent: *Monday, March 30, 2015 14:07
*Subject: *[Spacewalk-list] Yum client reports no update, But
Spacewalk GUI reports that there are
Hi,
I'm having an issue with Spacewalk 2.0. I have two RHEL6 x86_64
servers that the Spacewalk GUI reports that there are available
updates. However, if I run yum on these two machines, nothing is
reported as being available for updating. I've done some Google
searches and this has been an issue in the past for some individuals
and occasionally the problem has been fixed by running yum clean all,
followed by deleting the /var/cache/yum directory. Then a yum
makecache. . I tried this and it didn't helped. I have also tried
deleting the profile for the server and attempting a re-register. That
didn't work either. If anyone has any ideas/suggestions, I would like
to hear them.
- All updates have been performed using yum. No rpm --install or
--upgrade has been performed.
- Since I had deleted and re-registered the client, I didn't think
rhn-profile-sync would do any good, but I tried it anyhow. It didn't help.
- a complete shutdown of the Spacewalk server application and it's
corresponding postgres database was also attempted, again to avail.
- attempting to update the client from the Spacewalk GUI does not
work. The schedule task just goes into a pending state and never occurs.
Any suggestions would be appreciated.
Alan
*Unix **/is/**user friendly. It’s just very selective about who its
friends are.*
_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Kobus Bensch Trustpay Global LTD email signature Kobus Bensch
Senior Systems Administrator
Address: 22 & 24 | Frederick Sanger Road | Guildford | Surrey | GU2 7YD
DDI: 0207 871 3958
Tel: 0207 871 3890
Email: ***@trustpayglobal.com
<mailto:***@trustpayglobal.com>
--
Trustpay Global Limited is an authorised Electronic Money Institution
regulated by the Financial Conduct Authority registration number 900043.
Company No 07427913 Registered in England and Wales with registered address
130 Wood Street, London, EC2V 6DL, United Kingdom.

For further details please visit our website at www.trustpayglobal.com.

The information in this email and any attachments are confidential and
remain the property of Trustpay Global Ltd unless agreed by contract. It is
intended solely for the person to whom or the entity to which it is
addressed. If you are not the intended recipient you may not use, disclose,
copy, distribute, print or rely on the content of this email or its
attachments. If this email has been received by you in error please advise
the sender and delete the email from your system. Trustpay Global Ltd does
not accept any liability for any personal view expressed in this message.
Alan Pittman
2015-03-31 13:02:31 UTC
Permalink
Thanks for the replies, but neither suggestion helped. I got it to work with a wild shot in the dark. What I did was to delete the /var/cache/rhn/repodata/<channel> sub-directories on the spacewalk server and force the Spacewalk application to repopulate them. Exactly what forces the re-population, I don’t know, but if I run a yum makecache on the client, it initially fails because there isn’t anything in the /var/cache/rhn/repodata/<channel> directory. Something triggers Spacewalk to rebuild/reload the directory and then the makecache command works for that channel. I have to run the makecache multiple times to force all of the data for all of the channels to be re-populated.

How the data in the /var/cache/rhn/repodata/<channel> directory got “stale”, I don’t know, but at least it’s working now.

Hopefully this makes some sense and is helpful for someone else.

Alan

From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Kobus Bensch
Sent: Tuesday, March 31, 2015 4:42 AM
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are

I had this issue. I fixed it by running a repo sync manually.
On 31/03/2015 05:21, ***@gmail.com<mailto:***@gmail.com> wrote:
Try running rhn-profile-sync on the box in question then looking in the GUI again. This can happen if some one does a manual update in yum and does not run that command afterward.
Its well documented in the install procedure for every red hat errata‎ that you have to run that command after a yum update. You may also want to consider adding cron.daily job to do this with anacron that should execute it every day at a semi randomized time so you won't over laod your spacewalk server and the added load to the host while running it is negligible so it should not impact the performance of the applications you are running unless the box is already severly overloaded to begin with.


Sent from my BlackBerry 10 smartphone.
From: Alan Pittman
Sent: Monday, March 30, 2015 14:07
To: spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>
Reply To: spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>
Subject: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are


Hi,
I'm having an issue with Spacewalk 2.0. I have two RHEL6 x86_64 servers that the Spacewalk GUI reports that there are available updates. However, if I run yum on these two machines, nothing is reported as being available for updating. I've done some Google searches and this has been an issue in the past for some individuals and occasionally the problem has been fixed by running yum clean all, followed by deleting the /var/cache/yum directory. Then a yum makecache. . I tried this and it didn't helped. I have also tried deleting the profile for the server and attempting a re-register. That didn't work either. If anyone has any ideas/suggestions, I would like to hear them.

Some other information that might be beneficial (I think):

- All updates have been performed using yum. No rpm --install or --upgrade has been performed.
- Since I had deleted and re-registered the client, I didn't think rhn-profile-sync would do any good, but I tried it anyhow. It didn't help.
- a complete shutdown of the Spacewalk server application and it's corresponding postgres database was also attempted, again to avail.
- attempting to update the client from the Spacewalk GUI does not work. The schedule task just goes into a pending state and never occurs.

Any suggestions would be appreciated.

Alan

Unix is user friendly. It’s just very selective about who its friends are.











_______________________________________________

Spacewalk-list mailing list

Spacewalk-***@redhat.com<mailto:Spacewalk-***@redhat.com>

https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Kobus Bensch
Senior Systems Administrator
Address: 22 & 24 | Frederick Sanger Road | Guildford | Surrey | GU2 7YD
DDI: 0207 871 3958
Tel: 0207 871 3890
Email: ***@trustpayglobal.com<mailto:***@trustpayglobal.com>
[cid:***@01D06B91.48573890]


Trustpay Global Limited is an authorised Electronic Money Institution regulated by the Financial Conduct Authority registration number 900043. Company No 07427913 Registered in England and Wales with registered address 130 Wood Street, London, EC2V 6DL, United Kingdom.

For further details please visit our website at www.trustpayglobal.com<http://www.trustpayglobal.com>.

The information in this email and any attachments are confidential and remain the property of Trustpay Global Ltd unless agreed by contract. It is intended solely for the person to whom or the entity to which it is addressed. If you are not the intended recipient you may not use, disclose, copy, distribute, print or rely on the content of this email or its attachments. If this email has been received by you in error please advise the sender and delete the email from your system. Trustpay Global Ltd does not accept any liability for any personal view expressed in this message.
Boyd, Robert
2015-04-01 16:29:02 UTC
Permalink
I’m having this same problem – a number of clients show in the GUI to need quite a number of updates. However at the client end yum check-update shows 1 2 or 3 packages needing update. And when I attempt to run the update I get dependency errors. Some of the clients are showing an update for bind-libs.i686 when they only have the x86_64 package installed. The appropriate update package for the correct architecture is on the spacewalk server and I can see in the GUI that it is listed as an update for the client, but the client can’t see it. I’ve done all of the suggestions (and then some) for clearing this problem from the client end. This suggestion about the cache looks like the first hopeful suggestion I’ve seen.

And for the record, we’re running on Spacewalk 2.0 currently.

Robert Boyd
Sr. Systems Engineer
PeopleFluent
p. 919-645-2972 | c. 919-306-4681
e. ***@PeopleFluent.com<mailto:***@peoplefluent.com>

[Loading Image...]<http://www.peoplefluent.com/>
Click here<http://www.peoplefluent.com/> to experience the power of the new PeopleFluent Mirror Suite ™
Visit: www.peoplefluent.com<http://www.peoplefluent.com/> | Read: PeopleFluent Blog<http://peoplefluent.com/resources/peoplefluent-blog> | Follow: @PeopleFluent<http://twitter.com/peoplefluent>

From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Alan Pittman
Sent: Tuesday, March 31, 2015 9:03 AM
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are

Thanks for the replies, but neither suggestion helped. I got it to work with a wild shot in the dark. What I did was to delete the /var/cache/rhn/repodata/<channel> sub-directories on the spacewalk server and force the Spacewalk application to repopulate them. Exactly what forces the re-population, I don’t know, but if I run a yum makecache on the client, it initially fails because there isn’t anything in the /var/cache/rhn/repodata/<channel> directory. Something triggers Spacewalk to rebuild/reload the directory and then the makecache command works for that channel. I have to run the makecache multiple times to force all of the data for all of the channels to be re-populated.

How the data in the /var/cache/rhn/repodata/<channel> directory got “stale”, I don’t know, but at least it’s working now.

Hopefully this makes some sense and is helpful for someone else.

Alan

From: spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com> [mailto:spacewalk-list-***@redhat.com] On Behalf Of Kobus Bensch
Sent: Tuesday, March 31, 2015 4:42 AM
To: spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>
Subject: Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are

I had this issue. I fixed it by running a repo sync manually.
On 31/03/2015 05:21, ***@gmail.com<mailto:***@gmail.com> wrote:
Try running rhn-profile-sync on the box in question then looking in the GUI again. This can happen if some one does a manual update in yum and does not run that command afterward.
Its well documented in the install procedure for every red hat errata‎ that you have to run that command after a yum update. You may also want to consider adding cron.daily job to do this with anacron that should execute it every day at a semi randomized time so you won't over laod your spacewalk server and the added load to the host while running it is negligible so it should not impact the performance of the applications you are running unless the box is already severly overloaded to begin with.


Sent from my BlackBerry 10 smartphone.
From: Alan Pittman
Sent: Monday, March 30, 2015 14:07
To: spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>
Reply To: spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>
Subject: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are


Hi,
I'm having an issue with Spacewalk 2.0. I have two RHEL6 x86_64 servers that the Spacewalk GUI reports that there are available updates. However, if I run yum on these two machines, nothing is reported as being available for updating. I've done some Google searches and this has been an issue in the past for some individuals and occasionally the problem has been fixed by running yum clean all, followed by deleting the /var/cache/yum directory. Then a yum makecache. . I tried this and it didn't helped. I have also tried deleting the profile for the server and attempting a re-register. That didn't work either. If anyone has any ideas/suggestions, I would like to hear them.

Some other information that might be beneficial (I think):

- All updates have been performed using yum. No rpm --install or --upgrade has been performed.
- Since I had deleted and re-registered the client, I didn't think rhn-profile-sync would do any good, but I tried it anyhow. It didn't help.
- a complete shutdown of the Spacewalk server application and it's corresponding postgres database was also attempted, again to avail.
- attempting to update the client from the Spacewalk GUI does not work. The schedule task just goes into a pending state and never occurs.

Any suggestions would be appreciated.

Alan

Unix is user friendly. It’s just very selective about who its friends are.









_______________________________________________

Spacewalk-list mailing list

Spacewalk-***@redhat.com<mailto:Spacewalk-***@redhat.com>

https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Kobus Bensch
Senior Systems Administrator
Address: 22 & 24 | Frederick Sanger Road | Guildford | Surrey | GU2 7YD
DDI: 0207 871 3958
Tel: 0207 871 3890
Email: ***@trustpayglobal.com<mailto:***@trustpayglobal.com>
[cid:***@01D06C77.8A4F1150]


Trustpay Global Limited is an authorised Electronic Money Institution regulated by the Financial Conduct Authority registration number 900043. Company No 07427913 Registered in England and Wales with registered address 130 Wood Street, London, EC2V 6DL, United Kingdom.

For further details please visit our website at www.trustpayglobal.com<http://www.trustpayglobal.com>.

The information in this email and any attachments are confidential and remain the property of Trustpay Global Ltd unless agreed by contract. It is intended solely for the person to whom or the entity to which it is addressed. If you are not the intended recipient you may not use, disclose, copy, distribute, print or rely on the content of this email or its attachments. If this email has been received by you in error please advise the sender and delete the email from your system. Trustpay Global Ltd does not accept any liability for any personal view expressed in this message.
Paul Robert Marino
2015-04-01 16:59:48 UTC
Permalink
check if a repomd sync job is stuck
this can occasionally happen on larger repos if Java isn't properly tuned.
the quick way to fix it is to restart taskomatic then resync the repo
Failing that you need to delete the directory containing the repomd file
and resync the repo again to fully regenerate it.
Post by Boyd, Robert
I’m having this same problem – a number of clients show in the GUI to
need quite a number of updates. However at the client end yum
check-update shows 1 2 or 3 packages needing update. And when I attempt to
run the update I get dependency errors. Some of the clients are showing
an update for bind-libs.i686 when they only have the x86_64 package
installed. The appropriate update package for the correct architecture is
on the spacewalk server and I can see in the GUI that it is listed as an
update for the client, but the client can’t see it. I’ve done all of the
suggestions (and then some) for clearing this problem from the client end.
This suggestion about the cache looks like the first hopeful suggestion
I’ve seen.
And for the record, we’re running on Spacewalk 2.0 currently.
*Robert Boyd*
*Sr. Systems Engineer *
*PeopleFluent*
p. 919-645-2972 | c. 919-306-4681
http://mktg.peoplefluent.com/rs/peopleclick/images/140410_PF4colorLOGOx150.png]
<http://www.peoplefluent.com/>
*Click here* <http://www.peoplefluent.com/> *to experience the power of
the new PeopleFluent Mirror Suite ™*
Visit: www.peoplefluent.com | Read: PeopleFluent Blog
@PeopleFluent <http://twitter.com/peoplefluent>
*Sent:* Tuesday, March 31, 2015 9:03 AM
*Subject:* Re: [Spacewalk-list] Yum client reports no update, But
Spacewalk GUI reports that there are
Thanks for the replies, but neither suggestion helped. I got it to work
with a wild shot in the dark. What I did was to delete the
/var/cache/rhn/repodata/<channel> sub-directories on the spacewalk server
and force the Spacewalk application to repopulate them. Exactly what forces
the re-population, I don’t know, but if I run a yum makecache on the
client, it initially fails because there isn’t anything in the
/var/cache/rhn/repodata/<channel> directory. Something triggers Spacewalk
to rebuild/reload the directory and then the makecache command works for
that channel. I have to run the makecache multiple times to force all of
the data for all of the channels to be re-populated.
How the data in the /var/cache/rhn/repodata/<channel> directory got
“stale”, I don’t know, but at least it’s working now.
Hopefully this makes some sense and is helpful for someone else.
Alan
*Sent:* Tuesday, March 31, 2015 4:42 AM
*Subject:* Re: [Spacewalk-list] Yum client reports no update, But
Spacewalk GUI reports that there are
I had this issue. I fixed it by running a repo sync manually.
Try running rhn-profile-sync on the box in question then looking in the
GUI again. This can happen if some one does a manual update in yum and does
not run that command afterward.
Its well documented in the install procedure for every red hat errata‎
that you have to run that command after a yum update. You may also want to
consider adding cron.daily job to do this with anacron that should execute
it every day at a semi randomized time so you won't over laod your
spacewalk server and the added load to the host while running it is
negligible so it should not impact the performance of the applications you
are running unless the box is already severly overloaded to begin with.
Sent from my BlackBerry 10 smartphone.
*From: *Alan Pittman
*Sent: *Monday, March 30, 2015 14:07
*Subject: *[Spacewalk-list] Yum client reports no update, But Spacewalk
GUI reports that there are
Hi,
I'm having an issue with Spacewalk 2.0. I have two RHEL6 x86_64 servers
that the Spacewalk GUI reports that there are available updates. However,
if I run yum on these two machines, nothing is reported as being available
for updating. I've done some Google searches and this has been an issue in
the past for some individuals and occasionally the problem has been fixed
by running yum clean all, followed by deleting the /var/cache/yum
directory. Then a yum makecache. . I tried this and it didn't helped. I
have also tried deleting the profile for the server and attempting a
re-register. That didn't work either. If anyone has any ideas/suggestions,
I would like to hear them.
- All updates have been performed using yum. No rpm --install or
--upgrade has been performed.
- Since I had deleted and re-registered the client, I didn't think
rhn-profile-sync would do any good, but I tried it anyhow. It didn't help.
- a complete shutdown of the Spacewalk server application and it's
corresponding postgres database was also attempted, again to avail.
- attempting to update the client from the Spacewalk GUI does not work.
The schedule task just goes into a pending state and never occurs.
Any suggestions would be appreciated.
Alan
*Unix is user friendly. It’s just very selective about who its friends
are.*
_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Kobus Bensch
Senior Systems Administrator
Address: 22 & 24 | Frederick Sanger Road | Guildford | Surrey | GU2 7YD
DDI: 0207 871 3958
Tel: 0207 871 3890
Trustpay Global Limited is an authorised Electronic Money Institution
regulated by the Financial Conduct Authority registration number 900043.
Company No 07427913 Registered in England and Wales with registered address
130 Wood Street, London, EC2V 6DL, United Kingdom.
For further details please visit our website at www.trustpayglobal.com.
The information in this email and any attachments are confidential and
remain the property of Trustpay Global Ltd unless agreed by contract. It is
intended solely for the person to whom or the entity to which it is
addressed. If you are not the intended recipient you may not use, disclose,
copy, distribute, print or rely on the content of this email or its
attachments. If this email has been received by you in error please advise
the sender and delete the email from your system. Trustpay Global Ltd does
not accept any liability for any personal view expressed in this message.
_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list
Boyd, Robert
2015-04-02 19:34:17 UTC
Permalink
I tried running the spacewalk fsck utility.

I tried your suggestions as well. Unfortunately so far nothing has changed. I tried deleting one of the systems from spacewalk and re-registering it. After registering, it still shows the same discrepancy. A good number of updates listed in the GUI as being applicable, with only 2 showing on the client side with yum check-update.

I tried clearing out the yum cache on the client side, to no net effect.

I have another client that needed quite a number of updates. I applied the updates with yum update. After the update was complete, I now see the same discrepancy between the yum client list and the package updates showing available and applicable from the GUI. All of the servers involved have been rebooted, so everything has been restarted. At least once.

Any suggestions about why yum queries are getting different results than I see in the spacewalk GUI? And how to get things back in synch?

Robert Boyd
Sr. Systems Engineer
PeopleFluent
p. 919-645-2972 | c. 919-306-4681
e. ***@PeopleFluent.com<mailto:***@peoplefluent.com>

[http://mktg.peoplefluent.com/rs/peopleclick/images/140410_PF4colorLOGOx150.png]<http://www.peoplefluent.com/>
Click here<http://www.peoplefluent.com/> to experience the power of the new PeopleFluent Mirror Suite ™
Visit: www.peoplefluent.com<http://www.peoplefluent.com/> | Read: PeopleFluent Blog<http://peoplefluent.com/resources/peoplefluent-blog> | Follow: @PeopleFluent<http://twitter.com/peoplefluent>

From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Paul Robert Marino
Sent: Wednesday, April 01, 2015 1:00 PM
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are

check if a repomd sync job is stuck
this can occasionally happen on larger repos if Java isn't properly tuned.
the quick way to fix it is to restart taskomatic then resync the repo
Failing that you need to delete the directory containing the repomd file and resync the repo again to fully regenerate it.



On Wed, Apr 1, 2015 at 12:29 PM, Boyd, Robert <***@peoplefluent.com<mailto:***@peoplefluent.com>> wrote:
I’m having this same problem – a number of clients show in the GUI to need quite a number of updates. However at the client end yum check-update shows 1 2 or 3 packages needing update. And when I attempt to run the update I get dependency errors. Some of the clients are showing an update for bind-libs.i686 when they only have the x86_64 package installed. The appropriate update package for the correct architecture is on the spacewalk server and I can see in the GUI that it is listed as an update for the client, but the client can’t see it. I’ve done all of the suggestions (and then some) for clearing this problem from the client end. This suggestion about the cache looks like the first hopeful suggestion I’ve seen.

And for the record, we’re running on Spacewalk 2.0 currently.
Boyd, Robert
2015-04-17 17:03:07 UTC
Permalink
This problem continues. The master clearly sees that a number of packages need updating. For some reason on the client these packages are not being seen. I attempted scheduling updates from Spacewalk GUI. Then ran rhn_check on the client. Then I see this result on the master:

Summary:

Package Install scheduled by <username>

Details:

This action will be executed after 04/17/15 12:58:53 PM EDT.

This action's status is: Failed.
The client picked up this action on 04/17/15 12:59:09 PM EDT.
The client completed this action on 04/17/15 12:59:15 PM EDT.
Client execution returned "Error while executing packages action: empty transaction [[6]]" (code -1)
Packages Scheduled:
· xorg-x11-server-common-1.15.0-26.el6_6
· libipa_hbac-python-1.11.6-30.el6_6.4
· cyrus-sasl-2.1.23-15.el6_6.2
· scl-utils-20120927-27.el6_6
· kernel-2.6.32-504.12.2.el6
· sssd-1.11.6-30.el6_6.4
· dhcp-common-4.1.1-43.P1.el6_6.1:12
· busybox-1.15.1-21.el6_6:1
· nss-softokn-freebl-3.14.3-22.el6_6
· tzdata-2015b-1.el6
· kpartx-0.4.9-80.el6_6.3
· openssl-1.0.1e-30.el6_6.8
· samba-winbind-3.6.23-14.el6_6:0
· samba-winbind-clients-3.6.23-14.el6_6:0
· ntp-4.2.6p5-3.el6_6
· krb5-libs-1.10.3-37.el6_6
· sssd-krb5-common-1.11.6-30.el6_6.4
· perf-2.6.32-504.12.2.el6
· flac-1.2.1-7.el6_6
· krb5-workstation-1.10.3-37.el6_6
· freetype-2.3.11-15.el6_6.1
· cyrus-sasl-lib-2.1.23-15.el6_6.2
· unzip-6.0-2.el6_6
· dhclient-4.1.1-43.P1.el6_6.1:12
· augeas-libs-1.0.0-7.el6_6.1
· samba4-libs-4.0.0-66.el6_6.rc4:0
· samba-common-3.6.23-14.el6_6:0
· tzdata-java-2015b-1.el6
· sssd-client-1.11.6-30.el6_6.4
· dracut-004-356.el6_6.1
· curl-7.19.7-40.el6_6.4
· cyrus-sasl-plain-2.1.23-15.el6_6.2
· libsss_idmap-1.11.6-30.el6_6.4
· libcurl-7.19.7-40.el6_6.4
· sssd-proxy-1.11.6-30.el6_6.4
· libipa_hbac-1.11.6-30.el6_6.4
· openssl-devel-1.0.1e-30.el6_6.8
· krb5-devel-1.10.3-37.el6_6
· libssh2-1.4.2-1.el6_6.1
· nss-softokn-3.14.3-22.el6_6
· sssd-common-1.11.6-30.el6_6.4
· python-sssdconfig-1.11.6-30.el6_6.4
· shadow-utils-4.1.4.2-19.el6_6.1:2
· sssd-ipa-1.11.6-30.el6_6.4
· xorg-x11-server-Xorg-1.15.0-26.el6_6
· alsa-utils-1.0.22-9.el6_6
· sssd-krb5-1.11.6-30.el6_6.4
· kexec-tools-2.0.0-280.el6_6.2
· ruby-1.8.7.374-4.el6_6
· kernel-headers-2.6.32-504.12.2.el6
· sssd-ad-1.11.6-30.el6_6.4
· kernel-firmware-2.6.32-504.12.2.el6
· gdbm-1.8.0-38.el6
· openjpeg-libs-1.3-11.el6
· gdbm-devel-1.8.0-38.el6
· tcsh-6.17-25.el6_6
· sssd-ldap-1.11.6-30.el6_6.4
· dracut-kernel-004-356.el6_6.1
· nss-softokn-freebl-3.14.3-22.el6_6
· ruby-libs-1.8.7.374-4.el6_6
· cyrus-sasl-gssapi-2.1.23-15.el6_6.2
· sssd-common-pac-1.11.6-30.el6_6.4

Time:

04/17/15 12:58:53 PM EDT

________________________________
Reschedule:

This history event was caused by a failed scheduled action.
If you have corrected the problem, you may reschedule the action b



Robert Boyd
Sr. Systems Engineer
PeopleFluent
p. 919-645-2972 | c. 919-306-4681
e. ***@PeopleFluent.com<mailto:***@peoplefluent.com>

[http://mktg.peoplefluent.com/rs/peopleclick/images/140410_PF4colorLOGOx150.png]<http://www.peoplefluent.com/>
Click here<http://www.peoplefluent.com/> to experience the power of the new PeopleFluent Mirror Suite ™
Visit: www.peoplefluent.com<http://www.peoplefluent.com/> | Read: PeopleFluent Blog<http://peoplefluent.com/resources/peoplefluent-blog> | Follow: @PeopleFluent<http://twitter.com/peoplefluent>
Andy Ingham
2015-04-17 20:10:06 UTC
Permalink
Due to these sorts of nagging issues (especially when they proliferate across SCORES of servers), I finally set up a standard daily cron task (pushed out via the SW configuration management!) that does these actions daily on all clients:

/usr/bin/yum clean all
/usr/bin/yum makecache
/usr/sbin/rhn-profile-sync
/sbin/service osad restart

I find it handy to run that script "by hand" at times also. A sledgehammer approach, perhaps, but one with very little downside AFAIK.

I'd say that that has eliminated 90% of the nagging one-off problems with connectivity (osad) and failed updates.

FWIW.

If you have root privileges to the spacewalk SERVER (which you presumably do), you may find that recreating the repodata for the affected channel may help.

cd /var/cache/rhn/repodata/
remove the affected channel's directory tree
then run (in spacecmd) the "softwarechannel_regenerateyumcache" command against that channel
new repodata should then shortly re-appear
(At which point, I've found that I may need to run the cron script (above) by hand on the client.)

Andy

Andy Ingham, MS, CISSP
IT Infrastructure
Fuqua School of Business
Duke University


From: <Boyd>, Robert <***@peoplefluent.com<mailto:***@peoplefluent.com>>
Reply-To: "spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>" <spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>>
Date: Friday, April 17, 2015 at 1:03 PM
To: "spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>" <spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>>
Subject: Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are

This problem continues. The master clearly sees that a number of packages need updating. For some reason on the client these packages are not being seen. I attempted scheduling updates from Spacewalk GUI. Then ran rhn_check on the client. Then I see this result on the master:

Summary:

Package Install scheduled by <username>

Details:

This action will be executed after 04/17/15 12:58:53 PM EDT.

This action's status is: Failed.
The client picked up this action on 04/17/15 12:59:09 PM EDT.
The client completed this action on 04/17/15 12:59:15 PM EDT.
Client execution returned "Error while executing packages action: empty transaction [[6]]" (code -1)
Packages Scheduled:
· xorg-x11-server-common-1.15.0-26.el6_6
· libipa_hbac-python-1.11.6-30.el6_6.4
· cyrus-sasl-2.1.23-15.el6_6.2
· scl-utils-20120927-27.el6_6
· kernel-2.6.32-504.12.2.el6
· sssd-1.11.6-30.el6_6.4
· dhcp-common-4.1.1-43.P1.el6_6.1:12
· busybox-1.15.1-21.el6_6:1
· nss-softokn-freebl-3.14.3-22.el6_6
· tzdata-2015b-1.el6
· kpartx-0.4.9-80.el6_6.3
· openssl-1.0.1e-30.el6_6.8
· samba-winbind-3.6.23-14.el6_6:0
· samba-winbind-clients-3.6.23-14.el6_6:0
· ntp-4.2.6p5-3.el6_6
· krb5-libs-1.10.3-37.el6_6
· sssd-krb5-common-1.11.6-30.el6_6.4
· perf-2.6.32-504.12.2.el6
· flac-1.2.1-7.el6_6
· krb5-workstation-1.10.3-37.el6_6
· freetype-2.3.11-15.el6_6.1
· cyrus-sasl-lib-2.1.23-15.el6_6.2
· unzip-6.0-2.el6_6
· dhclient-4.1.1-43.P1.el6_6.1:12
· augeas-libs-1.0.0-7.el6_6.1
· samba4-libs-4.0.0-66.el6_6.rc4:0
· samba-common-3.6.23-14.el6_6:0
· tzdata-java-2015b-1.el6
· sssd-client-1.11.6-30.el6_6.4
· dracut-004-356.el6_6.1
· curl-7.19.7-40.el6_6.4
· cyrus-sasl-plain-2.1.23-15.el6_6.2
· libsss_idmap-1.11.6-30.el6_6.4
· libcurl-7.19.7-40.el6_6.4
· sssd-proxy-1.11.6-30.el6_6.4
· libipa_hbac-1.11.6-30.el6_6.4
· openssl-devel-1.0.1e-30.el6_6.8
· krb5-devel-1.10.3-37.el6_6
· libssh2-1.4.2-1.el6_6.1
· nss-softokn-3.14.3-22.el6_6
· sssd-common-1.11.6-30.el6_6.4
· python-sssdconfig-1.11.6-30.el6_6.4
· shadow-utils-4.1.4.2-19.el6_6.1:2
· sssd-ipa-1.11.6-30.el6_6.4
· xorg-x11-server-Xorg-1.15.0-26.el6_6
· alsa-utils-1.0.22-9.el6_6
· sssd-krb5-1.11.6-30.el6_6.4
· kexec-tools-2.0.0-280.el6_6.2
· ruby-1.8.7.374-4.el6_6
· kernel-headers-2.6.32-504.12.2.el6
· sssd-ad-1.11.6-30.el6_6.4
· kernel-firmware-2.6.32-504.12.2.el6
· gdbm-1.8.0-38.el6
· openjpeg-libs-1.3-11.el6
· gdbm-devel-1.8.0-38.el6
· tcsh-6.17-25.el6_6
· sssd-ldap-1.11.6-30.el6_6.4
· dracut-kernel-004-356.el6_6.1
· nss-softokn-freebl-3.14.3-22.el6_6
· ruby-libs-1.8.7.374-4.el6_6
· cyrus-sasl-gssapi-2.1.23-15.el6_6.2
· sssd-common-pac-1.11.6-30.el6_6.4

Time:

04/17/15 12:58:53 PM EDT

________________________________
Reschedule:

This history event was caused by a failed scheduled action.
If you have corrected the problem, you may reschedule the action b



Robert Boyd
Sr. Systems Engineer
PeopleFluent
p. 919-645-2972 | c. 919-306-4681
e. ***@PeopleFluent.com<mailto:***@peoplefluent.com>

[http://mktg.peoplefluent.com/rs/peopleclick/images/140410_PF4colorLOGOx150.png]<http://www.peoplefluent.com/>
Click here<http://www.peoplefluent.com/> to experience the power of the new PeopleFluent Mirror Suite (tm)
Visit: www.peoplefluent.com<http://www.peoplefluent.com/> | Read: PeopleFluent Blog<http://peoplefluent.com/resources/peoplefluent-blog> | Follow: @PeopleFluent<http://twitter.com/peoplefluent>
Boyd, Robert
2015-04-17 21:08:10 UTC
Permalink
I finally found the source of this problem. I had a java heap max of 1GB(Default?) configured for the taskomatic daemon. I modified /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf to bump up the heap:

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=512

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=3072

After restarting spacewalk the RHN cache rebuilt cleanly and now things look matched.

Wouldn’t it be nice if somehow taskomatic could flag that it’s in trouble in some way that it emails the administrator or raises an alarm that would show up in the GUI to tell you it’s failing? Does it already do this somewhere and I just don’t know about it? I don’t see any emails to root about this problem.

Robert Boyd
Sr. Systems Engineer
PeopleFluent
p. 919-645-2972 | c. 919-306-4681
e. ***@PeopleFluent.com<mailto:***@peoplefluent.com>

[http://mktg.peoplefluent.com/rs/peopleclick/images/140410_PF4colorLOGOx150.png]<http://www.peoplefluent.com/>
Click here<http://www.peoplefluent.com/> to experience the power of the new PeopleFluent Mirror Suite ™
Visit: www.peoplefluent.com<http://www.peoplefluent.com/> | Read: PeopleFluent Blog<http://peoplefluent.com/resources/peoplefluent-blog> | Follow: @PeopleFluent<http://twitter.com/peoplefluent>

From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Boyd, Robert
Sent: Friday, April 17, 2015 1:03 PM
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are

This problem continues. The master clearly sees that a number of packages need updating. For some reason on the client these packages are not being seen. I attempted scheduling updates from Spacewalk GUI. Then ran rhn_check on the client. Then I see this result on the master:
Loading...