[Spacewalk-list] Updating a machine after registering.

[Gerhardus.Geldenhuis at gta-travel.com]

Hi
Here is the output:
 
D: login(forceUpdate=True) invoked
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
logging into up2date server
D: writeCachedLogin() invoked
D: Wrote pickled loginInfo at  1224681100.04  with expiration of
1224684700.04  seconds.
successfully retrieved authentication token from up2date server
D: logininfo: {'X-RHN-Server-Id': 1000010003, 'X-RHN-Auth-Server-Time':
'1224681100.03', 'X-RHN-Auth': 'DHANoitGU5CwrMW7XHVlDA==',
'X-RHN-Auth-Channels': [['centos-5-x86_64', '20081021125218', '1',
'1']], 'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset': '3600.0'}
Updating package profile...
Updating package profile
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))




________________________________

	From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of puck at i29.net
	Sent: 22 October 2008 14:06
	To: spacewalk-list at redhat.com
	Subject: Re: [Spacewalk-list] Updating a machine after
registering.
	
	
	Could you try running rhn-profile-sync -vvv to get more output
and post that back to the list?
	
	Jem
	
	
	Gerhardus.Geldenhuis at gta-travel.com wrote: 

		Hi
		I am using the following versions on the client machine:
		rhn-profile-sync (Red Hat Network Client Tools)
0.4.17-8.el5
		
		rhn packages
		~~~~~~~~~~~~
		rhnlib-2.2.5-1.el5
		yum-rhn-plugin-0.5.3-6.6
		rhn-check-0.4.17-8.el5
		rhnsd-4.6.1-1.el5
		rhn-setup-0.4.17-8.el5
		rhn-client-tools-0.4.17-8.el5
		
		which are running on Centos5 2.6.18-92.el5xen #1 SMP Tue
Jun 10 19:20:18
		EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
		
		The dates are synced properly. Running rhn-profile-sync
gives the
		following error:
		Updating package profile...
		Updating hardware profile...
		Error reading hardware information:
dbus_bindings.DBusException
		Error reading dmi info : dbus_bindings.DBusException
		
		So it appears to be working for package profile but not
for the hardware
		profile. It does not however update the package profile
on the spacewalk
		server. 
		
		How do I check if there is an incompatibility between
the base channel
		of the activation key used for registration and the
system I am trying
		to update?
		
		Regards 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________