Am 13. März 2018 15:57:22 MEZ schrieb Soham Chakraborty <dec.so...@gmail.com>: >Hi all, > >I am trying to figure out whether anyone has seen this problem. After I >posted this thread, I had some discussion with Jan Hutar and although I >tried all the steps he suggested (which are below), I am still stuck >with >this problem. > >1) So far, I have tried to increase the memory >in /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf file from >1024 >to 3072 for the parameter wrapper.java.maxmemory. Restarted taskomatic. >Same problem. > >2) I deleted /var/cache/repodata/rhn/<label-of-the-channel> and >regenerated >metadata again. Same problem. > >3) yum-rhn-plugin is updated in both server and client. > >4) Ran 'yum clean all' and tried to schedule update from the server. >Same >problem. > >>From the /var/log/up2date file of the client, I see this: > >up2date successfully retrieved authentication token from up2date server >up2date E: Package samba4-libs-0:4.2.10-12.el6_9.x86_64 is not >available >for installation >up2date updateLoginInfo() login info >up2date logging into up2date server >up2date successfully retrieved authentication token from up2date server >up2date E: Package samba4-libs-0:4.2.10-12.el6_9.x86_64 is not >available >for installation > >But the packages are present on the spacewalk server. > ># ll >/spacewalk/redhat/1/fdb/samba4-libs/0:4.2.10-12.el6_9/x86_64/fdbbc812af803aa8a715ae23398ac177b64de178a56d1d6750f41a6730de787c/samba4-libs-4.2.10-12.el6_9.x86_64.rpm >-rw-r--r-- 1 root root 4567480 Nov 29 02:20 >/spacewalk/redhat/1/fdb/samba4-libs/0:4.2.10-12.el6_9/x86_64/fdbbc812af803aa8a715ae23398ac177b64de178a56d1d6750f41a6730de787c/samba4-libs-4.2.10-12.el6_9.x86_64.rpm > >The sha256sum matches as well. > >The spacewalk-schema is spacewalk-schema-2.6.17-1.el7.noarch. Do I need >to >update the schema as advised in >https://access.redhat.com/solutions/1263213? > >What could be wrong? Any help would be much appreciated. > >@Michael, do you reckon this could be any way related to >https://bugzilla.redhat.com/show_bug.cgi?id=1421674? Not as an end >result >but rather as a symptom? > >Thanks, > >On Tue, Aug 15, 2017 at 6:30 PM, Soham Chakraborty ><dec.so...@gmail.com> >wrote: > >> Hi all, >> >> I faced an odd problem today while trying to update my clients. I had >> several security patches and I got most of them installed but few of >the >> updates refused to get installed and I could not install them >manually as >> well. >> >> The error message from event logs of spacewalk say this: >> >> Client execution returned "Failed: Packages failed to install >properly: >> Package bind-utils-32:9.8.2-0.62.rc1.el6_9.4.x86_64 is not available >for >> installation Package bind-libs-32:9.8.2-0.62.rc1.el6_9.4.x86_64 is >not >> available for installation" (code 32) >> >> Interwebz tells different methods to fix this. But I do not see any >> smoking guns from those articles. >> >> Does anyone know why this is happening? I see this happening only for >few >> particular packages and few particular clients. Any thoughts? >> >> Thanks, >>
And your client is definitely subscribing to a channel, that has this package? What does yum search samba4-libs and yum info samba4-libs tell on the client? Robert -- sent from my mobile device _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
