[Spacewalk-list] OSAD can't connect to host and port

Wed Feb 15 19:08:32 UTC 2017

Konstantin,

Yes, I can telnet to port 5222.

Robert,

Here is the verbose output.  I only did three v's, because four is just to much information to post.

[root at corp-rhel-sndbx ~]# /usr/sbin/osad -N -v -v -v

2017-02-15 12:58:52 osad._setup_config: Updating configuration

2017-02-15 12:58:52 jabber_lib.setup_connection: Connecting to <FQDN SW Server>

2017-02-15 12:58:52 jabber_lib._get_jabber_client:

2017-02-15 12:58:52 jabber_lib._get_jabber_client: Connecting to <FQDN SW Server>

2017-02-15 12:58:52 jabber_lib.__init__:

2017-02-15 12:58:52 jabber_lib.__init__:

2017-02-15 12:58:52 jabber_lib.connect:

2017-02-15 12:58:52 jabber_lib.process: 300

2017-02-15 12:58:52 jabber_lib.process: None

2017-02-15 12:58:53 jabber_lib.process: None

2017-02-15 12:58:53 jabber_lib.process: None

2017-02-15 12:58:53 jabber_lib.setup_connection: Connected to jabber server <FQDN SW Server>

2017-02-15 12:58:53 osad_client.start: osad-5aecf197b4 f6962f84b418c0bdd420 osad

2017-02-15 12:58:53 jabber_lib.auth: osad-5aecf197b4 f6962f84b418c0bdd420 osad 1

2017-02-15 12:58:53 jabber_lib.process: 59.9999690056

2017-02-15 12:58:53 jabber_lib.process: 299.999938011

2017-02-15 12:58:53 jabber_lib.register_callback: <bound method Client._roster_callback of <osad.osad_client.Client object at 0x20c6a90>> iq None None None None

2017-02-15 12:58:53 jabber_lib.process: None

2017-02-15 12:58:53 jabber_lib._roster_callback: Updating the roster <iq type='result' id='iq-request-6ee481-2'><query xmlns = 'jabber:iq:roster' ><item ask='subscribe' jid='rhn-dispatcher-sat@<FQDN SW Server>' subscription='none' /></query></iq>

2017-02-15 12:58:53 jabber_lib.register_callback: <bound method Client._presence_callback of <osad.osad_client.Client object at 0x20c6a90>> presence None None None None

2017-02-15 12:58:53 jabber_lib.register_callback: <bound method Client._message_callback of <osad.osad_client.Client object at 0x20c6a90>> message None None None None

2017-02-15 12:58:53 jabber_lib.register_callback: <bound method Runner._error_callback of <osad.osad.Runner instance at 0x7fa5ed8ece18>> error None None None None

2017-02-15 12:58:53 osad.fix_connection: Time drift 0

2017-02-15 12:58:53 osad.fix_connection: Client name 475c306861c30ddf

2017-02-15 12:58:53 osad.fix_connection: Shared key c6074436a1185a81e717c5e1fa0d976b3275cc91

2017-02-15 12:58:53 jabber_lib.send_presence: None None

2017-02-15 12:58:53 jabber_lib.process_forever:

2017-02-15 12:58:53 jabber_lib.process: 180

And here it the established connection:
# netstat -an|grep 5222|grep "<IP Address>"
tcp        0      0 ::ffff:<FQDN SW Server>:5222      ::ffff:<IP Address>:60441  ESTABLISHED

Thank you.

Daryl

________________________________
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> on behalf of Robert Paschedag <robert.paschedag at web.de>
Sent: Wednesday, February 15, 2017 11:18 AM
To: spacewalk-list at redhat.com; Konstantin Raskoshnyi
Subject: Re: [Spacewalk-list] OSAD can't connect to host and port

Am 15. Februar 2017 17:49:22 MEZ schrieb Konstantin Raskoshnyi <konrasko at gmail.com>:
>Can you do a telnet to port 5222 from client to spacewalk?
>On Wed, Feb 15, 2017 at 8:07 AM Daryl Rose <darylrose at outlook.com>
>wrote:
>
>> I just did a fresh install of RHEL 6.6.  I installed Spacewalk client
>2.6
>> onto the server.  All is good with the exception of OSAD.  Whenever I
>try
>> to start it using services, I get the following error:
>>
>>
>> *# service osad start*
>>
>> *Starting osad: 2017-02-15 09:41:40 rhn_log.log_error: Error
>connecting to
>> jabber server: Unable to connect to the host and port specified. See
>> https://access.redhat.com/solutions/327903
Log in to Your Red Hat Account - Red Hat Customer Portal<https://access.redhat.com/solutions/327903>
access.redhat.com
Log In. Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

>> <https://access.redhat.com/solutions/327903> for more information. *
Log in to Your Red Hat Account - Red Hat Customer Portal<https://access.redhat.com/solutions/327903>
access.redhat.com
Log In. Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

>>
>> *Error connecting to jabber server: Unable to connect to the host and
>port
>> specified. See https://access.redhat.com/solutions/327903
Log in to Your Red Hat Account - Red Hat Customer Portal<https://access.redhat.com/solutions/327903>
access.redhat.com
Log In. Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

>> <https://access.redhat.com/solutions/327903> for more information. *
Log in to Your Red Hat Account - Red Hat Customer Portal<https://access.redhat.com/solutions/327903>
access.redhat.com
Log In. Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

>>
>> *2017-02-15 09:41:40 rhn_log.log_error: Traceback (most recent call
>last):*
>>
>> *  File "/usr/share/rhn/osad/jabber_lib.py", line 266, in
>setup_connection*
>>
>> *    c = self._get_jabber_client(js)*
>>
>> *  File "/usr/share/rhn/osad/jabber_lib.py", line 338, in
>> _get_jabber_client*
>>
>> *    c.connect()*
>>
>> *  File "/usr/share/rhn/osad/jabber_lib.py", line 612, in connect*
>>
>> *    raise socket.error(e)*
>>
>> *error: Unable to connect to the host and port specified*
>>
>>
>> *Traceback (most recent call last):*
>>
>> *  File "/usr/share/rhn/osad/jabber_lib.py", line 266, in
>setup_connection*
>>
>> *    c = self._get_jabber_client(js)*
>>
>> *  File "/usr/share/rhn/osad/jabber_lib.py", line 338, in
>> _get_jabber_client*
>>
>> *    c.connect()*
>>
>> *  File "/usr/share/rhn/osad/jabber_lib.py", line 612, in connect*
>>
>> *    raise socket.error(e)*
>>
>> *error: Unable to connect to the host and port specified*
>>
>>
>> I'm not doing anything different with this install than I've been
>doing
>> with all of my other RHEL servers.  This is an inside network, no
>firewall
>> in between.  I am using fully qualified domain names.  I can telnet
>to port
>> 5222 on the spacewalk server, and I can start osad with -N -v -v -v
>-v and
>> get connected, so there is no issue with the port, or resolving the
>server
>> name.  Could this be something in the 2.6 client and RHEL version
>6.6?
>>
>>
>> Thanks
>>
>>
>> Daryl
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
Spacewalk-list Info Page - Red Hat<https://www.redhat.com/mailman/listinfo/spacewalk-list>
www.redhat.com
To see the collection of prior postings to the list, visit the Spacewalk-list Archives. Using Spacewalk-list: To post a message to all the list ...

Hi Daryl,

You get connected when you run with -v -v -v -v but not when you just start the service? This does not make sense to me.

Could you please send the part where the connect succeeds from the call with very verbose mode?

Regards
Robert

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Spacewalk-list Info Page - Red Hat<https://www.redhat.com/mailman/listinfo/spacewalk-list>
www.redhat.com
To see the collection of prior postings to the list, visit the Spacewalk-list Archives. Using Spacewalk-list: To post a message to all the list ...

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