[Spacewalk-list] Unable to register clients

Mike Anderson Mike.Anderson at payspan.com
Thu Jan 29 00:11:23 UTC 2015


Well, I was able to register the client without the bootstrap file, but it’s stopped talking to the spacewalk server. “System not checking in with Spacewalk”. up2date log says  up2date A socket error occurred: [Errno -2] Name or service not known, attempt #1, and does that on a daily basis. Can anyone advise as to what’s going on here? Thanks


From: Alexander Innes <senni at necurity.co.uk<mailto:senni at necurity.co.uk>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Thursday, January 22, 2015 at 2:35 PM
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] Unable to register clients

by bootstap do you mean kickstart :)?

If so we got it working by adding a pre script to add our internal CA cert before it does the registration. Other beter way would be pushing the RPM to a channel, then specifing that rpm to be installed during build. As long as all the packages needed for clients to talk to the server are installed then it "should"^tm work

Took me ages to figure that out! Ive been meaning to write it all down sometime ha!

On 22 January 2015 at 19:06, Mike Anderson <Mike.Anderson at payspan.com<mailto:Mike.Anderson at payspan.com>> wrote:
I take it back, it did add the needed repositories. I just didn’t refresh the services. Still wondering why my bootstrap failed.
Mike Anderson | Systems Engineer | PaySpan®, Inc.
Two Ravinia Drive, Suite 1710, Atlanta, GA  30346 | (404) 665-3020<tel:%28404%29%20665-3020>
Mike.Anderson at PaySpan.com<mailto:mike.anderson at payspan.com>

From: Mike Anderson <mike.anderson at payspan.com<mailto:mike.anderson at payspan.com>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Thursday, January 22, 2015 at 1:32 PM

To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] Unable to register clients

So running the listed commands allowed the server to register, though it didn’t pick up any of the repositories. It looks like something happened with my bootstrap script, as doing this manually seems to work. I used to be able to run my bootstrap.sh which would install the ssl cert, register the system and assign the system to the specific channel.
If I recreate the bootstrap, will I need to re-register all the clients I’ve already registered w/ it?

Thanks for your help!
Mike Anderson | Systems Engineer | PaySpan®, Inc.
Two Ravinia Drive, Suite 1710, Atlanta, GA  30346 | (404) 665-3020<tel:%28404%29%20665-3020>
Mike.Anderson at PaySpan.com<mailto:mike.anderson at payspan.com>

From: Alexander Innes <senni at necurity.co.uk<mailto:senni at necurity.co.uk>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Thursday, January 22, 2015 at 10:11 AM
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] Unable to register clients

You need to distribute the SSL cert to your clients along the lines of

# Install the SSL certificate from the server
yum install http://spacewalk.lan/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm# Register clients
rhnreg_ks --serverUrl=https://spacewalk.lan/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-key --username $spacewalkusername


On 22 January 2015 at 14:04, Reneau, Wes W [HDS] <Wes.Reneau at hdsupply.com<mailto:Wes.Reneau at hdsupply.com>> wrote:
Check out this pdf:
http://linux.oracle.com/documentation/spacewalk/Red_Hat_Network_Satellite-5.5-Client_Configuration_Guide-en-US.pdf

Specifically this section, I think you need to import the cert from your swalk svr.
2.2.1. Registering Clients to Red Hat Network RHN Satellite Server

Then try to register clients.

Wes


From:spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com> [mailto:spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com>] On Behalf Of Mike Anderson
Sent: Wednesday, January 21, 2015 3:24 PM
To: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>

Subject: Re: [Spacewalk-list] Unable to register clients

Red herring. After I installed the necessary client software, received the same error as in original post.
I’m able to curl the https page of the spacewalk box from the client, telling me to go to the login page, so the port is open.
Expanded log from /var/log/up2date:

[Wed Jan 21 15:06:47 2015] up2date ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

[Wed Jan 21 15:07:29 2015] up2date Updating package profile

[Wed Jan 21 15:07:29 2015] up2date ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

[Wed Jan 21 15:08:14 2015] up2date Updating package profile

[Wed Jan 21 15:08:14 2015] up2date ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

[Wed Jan 21 15:08:40 2015] up2date Updating package profile

[Wed Jan 21 15:08:40 2015] up2date ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

[Wed Jan 21 15:08:57 2015] up2date Updating package profile

[Wed Jan 21 15:08:57 2015] up2date ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

[Wed Jan 21 15:09:24 2015] up2date Updating package profile

[Wed Jan 21 15:09:24 2015] up2date ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

[Wed Jan 21 15:09:34 2015] up2date Updating package profile

[Wed Jan 21 15:09:34 2015] up2date ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

[Wed Jan 21 15:10:00 2015] up2date A socket error occurred: [Errno -2] Name or service not known, attempt #1

[Wed Jan 21 15:10:00 2015] up2date

Traceback (most recent call last):

  File "/usr/sbin/rhnreg_ks", line 218, in <module>

    cli.run()

  File "/usr/share/rhn/up2date_client/rhncli.py", line 96, in run

    sys.exit(self.main() or 0)

  File "/usr/sbin/rhnreg_ks", line 90, in main

    rhnreg.getCaps()

  File "/usr/share/rhn/up2date_client/rhnreg.py", line 248, in getCaps

    s.capabilities.validate()

  File "/usr/share/rhn/up2date_client/rhnserver.py", line 178, in __get_capabilities

    self.registration.welcome_message()

  File "/usr/share/rhn/up2date_client/rhnserver.py", line 63, in __call__

    return rpcServer.doCall(method, *args, **kwargs)

  File "/usr/share/rhn/up2date_client/rpcServer.py", line 203, in doCall

    ret = method(*args, **kwargs)

  File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__

    return self.__send(self.__name, args)

  File "/usr/share/rhn/up2date_client/rpcServer.py", line 37, in _request1

    ret = self._request(methodname, params)

  File "/usr/lib64/python2.6/site-packages/rhn/rpclib.py", line 384, in _request

    self._handler, request, verbose=self._verbose)

  File "/usr/lib64/python2.6/site-packages/rhn/transports.py", line 170, in request

    headers, fd = req.send_http(host, handler)

  File "/usr/lib64/python2.6/site-packages/rhn/transports.py", line 720, in send_http

    self._connection.connect()

  File "/usr/lib64/python2.6/site-packages/rhn/connections.py", line 165, in connect

    socket.AF_UNSPEC, socket.SOCK_STREAM)

<class 'up2date_client.up2dateErrors.CommunicationError'>:

Thanks for any help you can provide.

From: Mike Anderson <mike.anderson at payspan.com<mailto:mike.anderson at payspan.com>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Wednesday, January 21, 2015 at 2:47 PM
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] Unable to register clients

It looks like the only traffic occurring during a registration is http/https, at least according to my firewall.
I tried to register another box, and prior to the process telling me that I didn’t have the rhnreg package installed, it complained about the up2date config file…

UPDATING RHN_REGISTER/UP2DATE CONFIGURATION FILES

-------------------------------------------------

* downloading necessary files

  client_config_update.py...

  client-config-overrides.txt...

* running the update scripts

  . up2date config file

Traceback (most recent call last):

  File "client_config_update.py", line 219, in <module>

    sys.exit(main() or 0)

  File "client_config_update.py", line 212, in main

    configFilename, newMappings = parseCommandline()

  File "client_config_update.py", line 198, in parseCommandline

    raise IOError(msg)

IOError: ERROR: filename to alter (1st argument), does not exist:

       /etc/sysconfig/rhn/up2date
I’ll install the required software on the box and report back if anything comes of that.

Mike Anderson | Systems Engineer | PaySpan®, Inc.
Two Ravinia Drive, Suite 1710, Atlanta, GA  30346 | (404) 665-3020<tel:%28404%29%20665-3020>
Mike.Anderson at PaySpan.com<mailto:mike.anderson at payspan.com>

From: <Reneau>, "Wes W [HDS]" <Wes.Reneau at hdsupply.com<mailto:Wes.Reneau at hdsupply.com>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Wednesday, January 21, 2015 at 2:15 PM
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] Unable to register clients

Have you confirmed your ports are up and listening?

The following table shows the required network ports depending on the configuration of the Spacewalk server.
Port and Protocol

Purpose

69/udp

tftp for PXE provisioning support

80/tcp

Spacewalk web access

443/tcp

Spacewalk web access

5222/tcp

Spacewalk client push support

5269/tcp

Spacewalk proxy push support





From:spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com> [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Mike Anderson
Sent: Wednesday, January 21, 2015 2:00 PM
To: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>
Subject: [Spacewalk-list] Unable to register clients

I tried registering the server to itself, and don’t recall why right now, but it didn’t work. Prior to attempting to register itself, I had no problems w/ registering machines. I had to register a new server soon afterwards, and when I went to do so, was unable to. Its giving me:

REGISTRATION

------------

* registering

An error has occurred:

Error communicating with server. The message was:

Name or service not known

See /var/log/up2date for more information



*** Error: Registering the system failed.
Applicable info in up2date:

[Mon Jan 19 17:06:41 2015] up2date Updating package profile

[Tue Jan 20 09:30:05 2015] up2date logging into up2date server

[Tue Jan 20 09:30:05 2015] up2date successfully retrieved authentication token from up2date server

[Wed Jan 21 09:30:05 2015] up2date logging into up2date server

[Wed Jan 21 09:30:05 2015] up2date successfully retrieved authentication token from up2date server

[Wed Jan 21 13:42:54 2015] up2date A socket error occurred: [Errno -2] Name or service not known, attempt #1

[Wed Jan 21 13:42:54 2015] up2date

Traceback (most recent call last):

  File "/usr/sbin/rhnreg_ks", line 218, in <module>

    cli.run()

  File "/usr/share/rhn/up2date_client/rhncli.py", line 96, in run

    sys.exit(self.main() or 0)

  File "/usr/sbin/rhnreg_ks", line 90, in main

    rhnreg.getCaps()

  File "/usr/share/rhn/up2date_client/rhnreg.py", line 248, in getCaps

    s.capabilities.validate()

  File "/usr/share/rhn/up2date_client/rhnserver.py", line 178, in __get_capabilities

    self.registration.welcome_message()

  File "/usr/share/rhn/up2date_client/rhnserver.py", line 63, in __call__

    return rpcServer.doCall(method, *args, **kwargs)

  File "/usr/share/rhn/up2date_client/rpcServer.py", line 203, in doCall

    ret = method(*args, **kwargs)

  File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__

    return self.__send(self.__name, args)

  File "/usr/share/rhn/up2date_client/rpcServer.py", line 37, in _request1

    ret = self._request(methodname, params)

  File "/usr/lib64/python2.6/site-packages/rhn/rpclib.py", line 384, in _request

    self._handler, request, verbose=self._verbose)

  File "/usr/lib64/python2.6/site-packages/rhn/transports.py", line 170, in request

    headers, fd = req.send_http(host, handler)

  File "/usr/lib64/python2.6/site-packages/rhn/transports.py", line 720, in send_http

    self._connection.connect()

  File "/usr/lib64/python2.6/site-packages/rhn/connections.py", line 165, in connect

    socket.AF_UNSPEC, socket.SOCK_STREAM)

<class 'up2date_client.up2dateErrors.CommunicationError'>:



Anyone run into this?
Mike Anderson | Systems Engineer | PaySpan®, Inc.
Two Ravinia Drive, Suite 1710, Atlanta, GA  30346 | (404) 665-3020<tel:%28404%29%20665-3020>
Mike.Anderson at PaySpan.com<mailto:mike.anderson at payspan.com>

The PaySpan e-mail gateway <mailgw01> made the following annotations.

------------------------------------------------------------------------------

Confidentiality statement

***********************************************************************

Notice: This e-mail message, including any attachments, is for the sole

use of the intended recipient(s) and may contain confidential and

privileged information.  Any unauthorized review, copy, use, disclosure,

or distribution is prohibited.  If you are not the intended recipient,

or not an agent of the intended recipient responsible for delivering this

message, please contact the sender by reply e-mail and destroy all copies

of the original message.[TW] 01/21/15, 14:00:00



The PaySpan e-mail gateway <mailgw01> made the following annotations.

------------------------------------------------------------------------------

Confidentiality statement

***********************************************************************

Notice: This e-mail message, including any attachments, is for the sole

use of the intended recipient(s) and may contain confidential and

privileged information.  Any unauthorized review, copy, use, disclosure,

or distribution is prohibited.  If you are not the intended recipient,

or not an agent of the intended recipient responsible for delivering this

message, please contact the sender by reply e-mail and destroy all copies

of the original message.[TW] 01/21/15, 14:48:01



The PaySpan e-mail gateway <mailgw01> made the following annotations.

------------------------------------------------------------------------------

Confidentiality statement

***********************************************************************

Notice: This e-mail message, including any attachments, is for the sole

use of the intended recipient(s) and may contain confidential and

privileged information.  Any unauthorized review, copy, use, disclosure,

or distribution is prohibited.  If you are not the intended recipient,

or not an agent of the intended recipient responsible for delivering this

message, please contact the sender by reply e-mail and destroy all copies

of the original message.[TW] 01/21/15, 15:00:12



The PaySpan e-mail gateway <mailgw01> made the following annotations.

------------------------------------------------------------------------------

Confidentiality statement

***********************************************************************

Notice: This e-mail message, including any attachments, is for the sole

use of the intended recipient(s) and may contain confidential and

privileged information.  Any unauthorized review, copy, use, disclosure,

or distribution is prohibited.  If you are not the intended recipient,

or not an agent of the intended recipient responsible for delivering this

message, please contact the sender by reply e-mail and destroy all copies

of the original message.[TW] 01/21/15, 15:24:26



_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com<mailto:Spacewalk-list at redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list


The PaySpan e-mail gateway <mailgw01> made the following annotations.
------------------------------------------------------------------------------
Confidentiality statement
***********************************************************************
Notice: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and
privileged information.  Any unauthorized review, copy, use, disclosure,
or distribution is prohibited.  If you are not the intended recipient,
or not an agent of the intended recipient responsible for delivering this
message, please contact the sender by reply e-mail and destroy all copies
of the original message.[TW] 01/22/15, 13:32:04



The PaySpan e-mail gateway <mailgw01> made the following annotations.
------------------------------------------------------------------------------
Confidentiality statement
************************************************************
***********
Notice: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and
privileged information.  Any unauthorized review, copy, use, disclosure,
or distribution is prohibited.  If you are not the intended recipient,
or not an agent of the intended recipient responsible for delivering this
message, please contact the sender by reply e-mail and destroy all copies
of the original message.[TW] 01/22/15, 13:45:44



The PaySpan e-mail gateway <mailgw01> made the following annotations.
------------------------------------------------------------------------------
Confidentiality statement
***********************************************************************
Notice: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and
privileged information.  Any unauthorized review, copy, use, disclosure,
or distribution is prohibited.  If you are not the intended recipient,
or not an agent of the intended recipient responsible for delivering this
message, please contact the sender by reply e-mail and destroy all copies
of the original message.[TW] 01/22/15, 14:06:50



_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com<mailto:Spacewalk-list at redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list


The PaySpan e-mail gateway <mailgw01> made the following annotations.
------------------------------------------------------------------------------
Confidentiality statement
***********************************************************************
Notice: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and 
privileged information.  Any unauthorized review, copy, use, disclosure, 
or distribution is prohibited.  If you are not the intended recipient,
or not an agent of the intended recipient responsible for delivering this 
message, please contact the sender by reply e-mail and destroy all copies 
of the original message.[TW] 01/28/15, 19:11:32

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20150129/e0ad1c3b/attachment.htm>


More information about the Spacewalk-list mailing list