Hi I at least now get an error with rhn_register but I think it is because it is trying to use the wrong channel... I think.
Error Class Code: 70
All available subscriptions for the requested channel have been
exhausted
Regards
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gerhardus
Geldenhuis
Sent: 22 October 2008 22:16
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: [Spacewalk-list] Updating a machine after
registering.
Hi Thanks,
I will try rhn_register tomorrow, I am really hopefull that it
will have improved behaviour.
The dmi errors was because I am running xen, and you need to add
an exception to the code when checking for dmi info...
Regards
On Wed, Oct 22, 2008 at 7:11 PM, <[EMAIL PROTECTED]> wrote:
I thought it might've been the DMI error that was
causing you problems but I found some threads on the rhn-satellite lists
that confirm others have had similar issues but it didn't affect them
any. So hopefully that wouldn't be stopping your systems from
registering - it's just an error message that can be safely ignored.
Have you tried registering your system with rhn_register
to see if that changes the behavior? I've had better luck with
rhn_register than rhnreg_ks, personally. It might be worth a try.
Jem
[EMAIL PROTECTED] wrote:
Hi
I have rebuild my server and added the output of
-vvv for rhnreg_ks and
rhn-profile-sync
rhnreg_ks --serverUrl=http://longrhn01a/XMLRPC
--activationkey=1-test02
-vvv
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
Error reading hardware information:
dbus_bindings.DBusException
Error reading DMI information:
dbus_bindings.DBusException
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))
and
updateLoginInfo() login info
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 1224695184.25
with expiration of
1224698784.25 seconds.
successfully retrieved authentication token from
up2date server
D: logininfo: {'X-RHN-Server-Id': 1000010008,
'X-RHN-Auth-Server-Time':
'1224695184.24', 'X-RHN-Auth':
'LTSOP7CR1OUVAqvZn1a6TQ==',
'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
Updating hardware profile...
Error reading hardware information:
dbus_bindings.DBusException
Error reading DMI information:
dbus_bindings.DBusException
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))
Regards
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 22 October 2008 16:15
To: [EMAIL PROTECTED];
[email protected]
Subject: RE: [Spacewalk-list] Updating a
machine after registering.
That is definetely all of it. I noticed
that too, I need to
rebuild the
machine and try again to see if there is
a difference. Even though it
does not fail at the hardware profile
now it still does not
mark any of
the packages as out of date on the
spacewalk server.
Regards
-----Original Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 22 October 2008 16:01
To: [email protected]
Subject: Re: [Spacewalk-list]
Updating a machine after registering.
Are you sure that was all of the
output from the command?
It doesn't
look like it tried to update the
hardware profile this
time, which is
where the errors appeared in
your original post.
Jem
[EMAIL PROTECTED] wrote:
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:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 22 October 2008
14:06
To:
[email protected]
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
[EMAIL PROTECTED] 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
______________________________________________________________________
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
______________________________________________________________________
This email has been scanned by the
MessageLabs Email Security System.
For more information please visit
http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
______________________________________________________________________
This email has been scanned by the MessageLabs
Email Security System.
For more information please visit
http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Gerhardus Geldenhuis
Registered Linux User #193352
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
