Finally I was able to pass the following command and register my client: rhnreg_ks --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --serverUrl=https://client.x.y/XMLRPC --activationkey=1-CentOS --force
But afterwards unfortunately the problem occurs with the osad comnnection. I see in log that the server is not FQDN: jid='rhn-dispatcher-sat@server' and not jid='rhn-dispatcher-sat@server.x.y' - Is that the issue? - Where should I configure that? All config’s file seems ok… 2018-07-17 15:32:47 jabber_lib._expire_callbacks_hash: 1531834367.88 2018-07-17 15:32:47 jabber_lib._expire_callbacks_list: [[<bound method Client._presence_callback of <osad.osad_client.Client object at 0x7f29ce933f10>>, None, None]] 1531834367.88 2018-07-17 15:32:47 jabber_lib._get_callbacks: <iq to='osad-1d0d6896a4@server.x.y/osad' type='set' id='todaq7lsfog3mqm7ggxbyko0jqwljt1dien9m921'><query xmlns = 'jabber:iq:roster' ><item ask='subscribe' jid='rhn-dispatcher-sat@server' subscription='none' /></query></iq> 2018-07-17 15:32:47 jabber_lib.dispatch: Calling callback <bound method Client._roster_callback of <osad.osad_client.Client object at 0x7f29ce933f10>> <iq to='osad-1d0d6896a4@server.x.y/osad' type='set' id='todaq7lsfog3mqm7ggxbyko0jqwljt1dien9m921'><query xmlns = 'jabber:iq:roster' ><item ask='subscribe' jid='rhn-dispatcher-sat@server' subscription='none' /></query></iq> 2018-07-17 15:32:47 jabber_lib._roster_callback: Updating the roster <iq to='osad-1d0d6896a4@ server.x.y /osad' type='set' id='todaq7lsfog3mqm7ggxbyko0jqwljt1dien9m921'><query xmlns = 'jabber:iq:roster' ><item ask='subscribe' jid='rhn-dispatcher-sat@server' subscription='none' /></query></iq> 2018-07-17 15:32:54 jabber_lib.process: 180 2018-07-17 15:32:54 jabber_lib.process: before select(); timeout 179.999999046 2018-07-17 15:34:53 jabber_lib.process: select() returned 2018-07-17 15:34:53 jabber_lib.process: Reading 1024 bytes from ssl socket 2018-07-17 15:34:53 jabber_lib.process: Read 210 bytes 2018-07-17 15:34:53 jabber_lib._orig_dispatch: <error><host-gone xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' /><text xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >connection timed out</text></error> 2018-07-17 15:34:53 jabber_lib.dispatch: <error><host-gone xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' /><text xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >connection timed out</text></error> 2018-07-17 15:34:53 jabber_lib.cleanup_expired_callbacks: Thanks, J. Von: Jérôme Meyer<mailto:jerome.me...@lcsystems.ch> Gesendet: Dienstag, 17. Juli 2018 12:51 An: 'spacewalk-list@redhat.com'<mailto:spacewalk-list@redhat.com> Betreff: [Spacewalk-list] rhn_register issue with spacewalk 2.4 on CentOS 7 Hi All, I always needed to use rhn_check to enable the command on the client. For this reason, I’ve 1) re-created the CA Key pair and Web SSL for my server 2) configure server and client with new Key pair 3) delete client host on spacewalk. When I want to register my client the following error appears (the registration should be only done with spacewalk server but not with the RHN Network). ******************* # rhn_register rhn-plugin: Error communicating with server. The message was: Error Class Code: 70 Error Class Info: All available subscriptions for the requested channel have been exhausted. Please contact a Red Hat Satellite Sales associate. Explanation: An error has occurred while processing your request. If this problem persists please enter a bug report at bugzilla.redhat.com. If you choose to submit the bug report, please be sure to include details of what you were trying to do when this error occurred and details on how to reproduce this problem. ******************* Is another way to register the client to the spacewalk server? Anyone has an idea? Thanks, Jérôme
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
