Doubt these are the only situation but under SW 1.4. 1)RHEL4 which
required deleting and registering the system again. 2)Channels/Repos
were still in a process of sync'ing their repo cache. You can see this
from the Channels details page.
I just had a similar issue but in my case I was seeing updates available
SW side but not client. I did all the typical yum clean all, profile
syncs, rhn_check checks, channel repo cache sync etc and so forth. I
even restarted the SW services. Nothing worked.
I then noticed that reposyncs were still running (ie: ps auxwww | grep
repo). Somehow they appear to have been causing problems with this even
though the repos were unrelated to the clients I saw issues on. Within
minutes of the reposync's finishing all updates showed up.
On 09/13/2011 01:57 AM, Pierre Casenove wrote:
Hello,
After a day, the clients still don't see the updates.
I've checked /var/log/up2date file on the client, but couldn't find
anything interesting.
From the spacewalk gui, when I select the latest kernel package and
then click on "Target Systems" tabs, my clients are listed, though
spacewalk says they doesn't need any update (I've attached a screenshot
to be clear).
Thanks in advance for your help,
Pierre
2011/9/12 Pierre Casenove <[email protected] <mailto:[email protected]>>
Hello,
I have a spacewalk 1.5 installation on PGSQL backend.
I have a base channel containing RHEL 5 x64 rpms.
My test clients have RHEL 5.6 installed.
I've rhnpushed the rpm of RHEL 5.7 in the base channel.
The problem is that in the web ui, no packages are marcked for updates.
When I connect on a client, and launched yum update command, here is
the (filtered) output:
Transaction Summary
Install 1 Package(s)
Upgrade 178 Package(s)
Total download size: 287 M
Is this ok [y/N]: N
Here is the log when running rhn_check -vvvv :
hostname ~ # rhn_check -vvvv
D: opening db environment /var/lib/rpm/Packages joinenv
D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
D: locked db index /var/lib/rpm/Packages
D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
D: do_call packages.checkNeedUpdate ('rhnsd=1',) {}
Loaded plugins: rhnplugin
D: opening db environment /var/lib/rpm/Packages joinenv
D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
D: closed db index /var/lib/rpm/Providename
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm/Packages
D: May free Score board((nil))
Config time: 0.069
Setting up Package Sacks
D: login(forceUpdate=False) invoked
D: readCachedLogin invoked
D: Checking pickled loginInfo, currentTime= 1315834359.91 ,
createTime= 1315834345.24 , expire-offset= 3600.0
D: readCachedLogin(): using pickled loginInfo set to expire at
1315837945.24
D: rpcServer: Calling XMLRPC up2date.listChannels
pkgsack time: 0.076
rpmdb time: 0.000
repo time: 0.003
D: local action status: (0, 'rpm database not modified since last
update (or package list recently updated)', {})
D: rpcServer: Calling XMLRPC registration.welcome_message
D: closed db index /var/lib/rpm/Providename
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm/Packages
D: May free Score board((nil))
I've ran rhn_check 6 hours after rhnpushing the updates. Is there a
problem in my setup? Where could I find useful information?
Thanks in advance for you help,
Pierre
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
