Discussion:
[Spacewalk-list] Spacewalk osad-dispatcher cannot connect to jabber
Jérôme Meyer
2018-10-05 12:01:29 UTC
Permalink
Hi Team,

Spacewalk server cannot connect with the osad-dispatcher and following error appears (for an unknown reason because it was running before) :

2018/10/05 13:46:42 +02:00 2413 0.0.0.0: osad/jabber_lib._waitForResponse('after get_one_stanza',)
2018/10/05 13:46:42 +02:00 2413 0.0.0.0: osad/jabber_lib.register('ERROR', 'Invalid password')

I've read on some post than the /var/lib/jabber/db must be deleted but I don't use this DB but the PostgreSQL.

Here're the version's packages:

Jabberd-2.6.1-1.el7.x86_64
spacewalk-common-2.8.2-1.el7.centos.noarch
postgresql-9.2.23-3.el7_4.x86_64

As anyone an idea?

Best regards,
Jérôme
Jérôme Meyer
2018-10-05 12:13:01 UTC
Permalink
I've found the following regarding the jabber's connection:

# netstat -tulpen|grep 52
tcp6 0 0 :::5222 :::* LISTEN 995 31383 2388/c2s
tcp6 0 0 :::5269 :::* LISTEN 995 30223 2387/s2s

Could be possible that the osad-dispatcher are trying to reach the jabber with IPv6 where it is not in used.
Is it possible to start jabberd only with IPv4? Are these problems in relation?

Best regards,
Jérôme

From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Jérôme Meyer
Sent: Freitag, 5. Oktober 2018 14:01
To: 'spacewalk-***@redhat.com'
Subject: [Spacewalk-list] Spacewalk osad-dispatcher cannot connect to jabber

Hi Team,

Spacewalk server cannot connect with the osad-dispatcher and following error appears (for an unknown reason because it was running before) :

2018/10/05 13:46:42 +02:00 2413 0.0.0.0: osad/jabber_lib._waitForResponse('after get_one_stanza',)
2018/10/05 13:46:42 +02:00 2413 0.0.0.0: osad/jabber_lib.register('ERROR', 'Invalid password')

I've read on some post than the /var/lib/jabber/db must be deleted but I don't use this DB but the PostgreSQL.

Here're the version's packages:

Jabberd-2.6.1-1.el7.x86_64
spacewalk-common-2.8.2-1.el7.centos.noarch
postgresql-9.2.23-3.el7_4.x86_64

As anyone an idea?

Best regards,
Jérôme
Dimitri Yioulos
2018-10-05 14:28:42 UTC
Permalink
Unless you use IPv6 in your environment, try disabling it on your SW server. For RHEL/CentOS, edit sysctl.conf and your interface file.

HTH

From: spacewalk-list-***@redhat.com <spacewalk-list-***@redhat.com> On Behalf Of Jérôme Meyer
Sent: Friday, October 05, 2018 8:13 AM
To: 'spacewalk-***@redhat.com' <spacewalk-***@redhat.com>
Subject: Re: [Spacewalk-list] Spacewalk osad-dispatcher cannot connect to jabber

I've found the following regarding the jabber's connection:

# netstat -tulpen|grep 52
tcp6 0 0 :::5222 :::* LISTEN 995 31383 2388/c2s
tcp6 0 0 :::5269 :::* LISTEN 995 30223 2387/s2s

Could be possible that the osad-dispatcher are trying to reach the jabber with IPv6 where it is not in used.
Is it possible to start jabberd only with IPv4? Are these problems in relation?

Best regards,
Jérôme

From: spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com> [mailto:spacewalk-list-***@redhat.com] On Behalf Of Jérôme Meyer
Sent: Freitag, 5. Oktober 2018 14:01
To: 'spacewalk-***@redhat.com'
Subject: [Spacewalk-list] Spacewalk osad-dispatcher cannot connect to jabber

Hi Team,

Spacewalk server cannot connect with the osad-dispatcher and following error appears (for an unknown reason because it was running before) :

2018/10/05 13:46:42 +02:00 2413 0.0.0.0: osad/jabber_lib._waitForResponse('after get_one_stanza',)
2018/10/05 13:46:42 +02:00 2413 0.0.0.0: osad/jabber_lib.register('ERROR', 'Invalid password')

I've read on some post than the /var/lib/jabber/db must be deleted but I don't use this DB but the PostgreSQL.

Here're the version's packages:

Jabberd-2.6.1-1.el7.x86_64
spacewalk-common-2.8.2-1.el7.centos.noarch
postgresql-9.2.23-3.el7_4.x86_64

As anyone an idea?

Best regards,
Jérôme
Jérôme Meyer
2018-10-08 06:01:53 UTC
Permalink
Thanks Dimitri,
We don't use IPv6, so I've disabled it on my system.
But the osa-dispatcher.service remains down with issue: 'ERROR', 'Invalid password')

Which is this password? could you change it ore regenerate it?

Best regards,
Jérôme


From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Dimitri Yioulos
Sent: Freitag, 5. Oktober 2018 16:29
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk osad-dispatcher cannot connect to jabber

Unless you use IPv6 in your environment, try disabling it on your SW server. For RHEL/CentOS, edit sysctl.conf and your interface file.

HTH

From: spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com> <spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com>> On Behalf Of Jérôme Meyer
Sent: Friday, October 05, 2018 8:13 AM
To: 'spacewalk-***@redhat.com' <spacewalk-***@redhat.com<mailto:spacewalk-***@redhat.com>>
Subject: Re: [Spacewalk-list] Spacewalk osad-dispatcher cannot connect to jabber

I've found the following regarding the jabber's connection:

# netstat -tulpen|grep 52
tcp6 0 0 :::5222 :::* LISTEN 995 31383 2388/c2s
tcp6 0 0 :::5269 :::* LISTEN 995 30223 2387/s2s

Could be possible that the osad-dispatcher are trying to reach the jabber with IPv6 where it is not in used.
Is it possible to start jabberd only with IPv4? Are these problems in relation?

Best regards,
Jérôme

From: spacewalk-list-***@redhat.com<mailto:spacewalk-list-***@redhat.com> [mailto:spacewalk-list-***@redhat.com] On Behalf Of Jérôme Meyer
Sent: Freitag, 5. Oktober 2018 14:01
To: 'spacewalk-***@redhat.com'
Subject: [Spacewalk-list] Spacewalk osad-dispatcher cannot connect to jabber

Hi Team,

Spacewalk server cannot connect with the osad-dispatcher and following error appears (for an unknown reason because it was running before) :

2018/10/05 13:46:42 +02:00 2413 0.0.0.0: osad/jabber_lib._waitForResponse('after get_one_stanza',)
2018/10/05 13:46:42 +02:00 2413 0.0.0.0: osad/jabber_lib.register('ERROR', 'Invalid password')

I've read on some post than the /var/lib/jabber/db must be deleted but I don't use this DB but the PostgreSQL.

Here're the version's packages:

Jabberd-2.6.1-1.el7.x86_64
spacewalk-common-2.8.2-1.el7.centos.noarch
postgresql-9.2.23-3.el7_4.x86_64

As anyone an idea?

Best regards,
Jérôme

Loading...