[Spacewalk-list] No module named hardware_hal
lravelo at us.hellmann.net
lravelo at us.hellmann.net
Mon Jun 5 13:47:48 UTC 2017
That's the thing: python-gobject2 already exists and the path
/usr/lib64/python2.7/site-packages/glib exists so not sure.
Regards,
Lazaro Ravelo
ISS Systems Engineer II
Hellmann Worldwide Logistics Inc.
10450 Doral Blvd
Doral, FL 33178
Phone: +1 305 406 4500
Fax: +1 305 418 4992
Direct: +1 305 406 4574
Mobile: +1 305 927 1386
Email: Lazaro.Ravelo at us.hellmann.net
Web: www.hellmann.com
THINKING AHEAD - MOVING FORWARD
From: spacewalk-list-request at redhat.com
To: spacewalk-list at redhat.com
Date: 06/02/2017 04:50 AM
Subject: Spacewalk-list Digest, Vol 109, Issue 7
Sent by: spacewalk-list-bounces at redhat.com
Send Spacewalk-list mailing list submissions to
spacewalk-list at redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/spacewalk-list
or, via email, send a message with subject or body 'help' to
spacewalk-list-request at redhat.com
You can reach the person managing the list at
spacewalk-list-owner at redhat.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Spacewalk-list digest..."
Today's Topics:
1. Re: Can't start OSAD in Spacewalk client? (Fouts, Christopher)
2. Re: No module named hardware_hal (Lichtinger, Bernhard)
3. Re: How to "unregister" a Spacewalk client from the server
(Michael Mraka)
----------------------------------------------------------------------
Message: 1
Date: Thu, 1 Jun 2017 20:52:56 +0000
From: "Fouts, Christopher" <Christopher.Fouts at Teradata.com>
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] Can't start OSAD in Spacewalk client?
Message-ID: <8C603327-08EE-44B6-82D9-DD0199255AE1 at teradata.com>
Content-Type: text/plain; charset="utf-8"
BTW, after I upgraded rhnlib, I can?t see my Spacewalk repos anymore, that
is, when I do a yum repolist, I see 0 mirrors.
Chris
From: <spacewalk-list-bounces at redhat.com> on behalf of "Fouts,
Christopher" <Christopher.Fouts at Teradata.com>
Reply-To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Date: Thursday, June 1, 2017 at 4:31 PM
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: [Spacewalk-list] Can't start OSAD in Spacewalk client?
I have Spacewalk v2.6 running on my server.
I was able to register a client to the server, and have osa-dispatcher
running as well. Now am trying to run osad on the client. I installed the
osad package and tried to start it and got?
Jun 1 20:12:04 ip-172-31-18-165 systemd: Starting OSAD daemon...
Jun 1 20:12:04 ip-172-31-18-165 osad: Unable to load module osad
Jun 1 20:12:04 ip-172-31-18-165 osad: No module named i18n
So I updated the rhnlib package (per google search), and now I get this?
Jun 1 20:27:51 ip-172-31-18-165 systemd: Starting OSAD daemon...
Jun 1 20:27:51 ip-172-31-18-165 osad: Unable to load module osad
Jun 1 20:27:51 ip-172-31-18-165 osad: cannot import name
idn_ascii_to_pune
I can?t find anything in the forum about it.
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://www.redhat.com/archives/spacewalk-list/attachments/20170601/a035c8c9/attachment.html
>
------------------------------
Message: 2
Date: Fri, 2 Jun 2017 08:25:35 +0000
From: "Lichtinger, Bernhard" <Bernhard.Lichtinger at lrz.de>
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] No module named hardware_hal
Message-ID: <248C3EAE-E2D6-47F4-A94E-B8FC886643F8 at lrz.de>
Content-Type: text/plain; charset="us-ascii"
Hi,
> and here's my output:
>
> Traceback (most recent call last):
> File "/usr/sbin/rhnreg_ks", line 37, in <module>
> from up2date_client import rhnreg
> File "/usr/share/rhn/up2date_client/rhnreg.py", line 20, in <module>
> from up2date_client import hardware
> File "/usr/share/rhn/up2date_client/hardware.py", line 64, in <module>
> from up2date_client.hardware_hal import check_hal_dbus_status,
get_hal_computer, read_hal
> ImportError: No module named hardware_hal
>
> I've tried it with the --nohardware flag but I get the same output. Any
ideas?
Perhaps you need to install the package "python-gobject2".
I can vaguely remember having the same error. It is a bit tricky, because
the "real error" happens in the try block at line 60 in
"/usr/share/rhn/up2date_client/hardware.py":
try: # F13 and EL6
from up2date_client.hardware_gudev import get_devices,
get_computer_info
using_gudev = 1
except ImportError:
from up2date_client.hardware_hal import check_hal_dbus_status,
get_hal_computer, read_hal
using_gudev = 0
The try block fails, because
"/usr/share/rhn/up2date_client/hardware_gudev.py" has:
if dist()[0] == 'SuSE':
# import gi.repository.GUdev fail and
# make the import gudev after it fail too
# so we have to import gudev only
import gudev
import glib
gi_gudev = False
And this fails because "import glib" fails.
The package "python-gobject2" will install
"/usr/lib64/python2.7/site-packages/glib"
And if the python module glib is missing, the except block is tried and
this block fails also, which gives you your error message.
I have to admit that I was too lazy to file a bug report that
"python-gobject2" should be a dependency for "rhn-client-tools" on SLES.
Regards,
Bernhard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5128 bytes
Desc: not available
URL: <
https://www.redhat.com/archives/spacewalk-list/attachments/20170602/b07469fe/attachment.bin
>
------------------------------
Message: 3
Date: Fri, 2 Jun 2017 10:48:46 +0200
From: Michael Mraka <michael.mraka at redhat.com>
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] How to "unregister" a Spacewalk client
from the server
Message-ID: <20170602084846.GA3616 at magni.brq.redhat.com>
Content-Type: text/plain; charset=utf-8
Fouts, Christopher:
> What is the correct procedure from unregistering a currently registered
Spacewalk client from the Spacewalk server? I know deleting the instance
from the Spacewalk server GUI is once step, but what about on the client
side?
You can either remove all client packages
yum remove rhn* osad spacewalk* yum-rhn-plugin
or just disable spacewalk services
systemctl disable rhnsd
systemctl disable rhnmd
sed -i 's/enabled *= *1/enabled=0/' /etc/yum/pluginconf.d/rhnplugin.conf
> Chris
Regards,
--
Michael Mr?ka
System Management Engineering, Red Hat
------------------------------
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
End of Spacewalk-list Digest, Vol 109, Issue 7
**********************************************
06/02/2017----04:48:52 AM
>Disclaimer: Please note that Internet communications are not secure and
therefore HELLMANN WORLDWIDE LOGISTICS does not accept legal
responsibility for the contents of this message. This e-mail is intended
only for the use of the individual or entity named above and may contain
information that is confidential and privileged. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this e-mail is strictly prohibited. Opinions,
conclusions and other information in this message that do not relate to
the official business of HELLMANN WORLDWIDE LOGISTICS shall be understood
as neither given nor endorsed by it. Viruses: HELLMANN WORLDWIDE LOGISTICS
takes all possible steps to ensure that emails are virus free, but does
not accept any liability or responsibility whatsoever for any claims,
losses or damages arising as a result of any party accessing this email or
files attached to it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20170605/7269c73f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 18000 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20170605/7269c73f/attachment.jpe>
More information about the Spacewalk-list
mailing list