Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Michael Mraka]

Bruce Wainer:
> Sorry to double-post, but I just realized, shouldn't spacewalk-setup be
> checking that the hostname is all-lowercase, at the same time that it
> checks that it is a valid FQDN? I know that I definitely didn't get any
> warnings about CASE when running it, and I set it up at least twice from

Hi Bruce,

Fair enough. I've added warning about fqdn and lowercase to the wiki and
also updatad spacewalk-setup to test that.

> scratch. Should I submit a bug report requesting this?
> Thanks,
> Bruce
> 
> Bruce Wainer

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Bruce Wainer]

Sorry to double-post, but I just realized, shouldn't spacewalk-setup be
checking that the hostname is all-lowercase, at the same time that it
checks that it is a valid FQDN? I know that I definitely didn't get any
warnings about CASE when running it, and I set it up at least twice from
scratch. Should I submit a bug report requesting this?
Thanks,
Bruce

Bruce Wainer

On Sun, Dec 10, 2017 at 8:17 PM, Bruce Wainer  wrote:

> After leaving this be a few months I returned to the issue. I found the
> cause to be that my hostname had capitalized letters in it. Renaming the
> host with all lowercase and running the spacewalk-hostname-rename script
> resolved the issue. Apparently, the Satellite 5.8 Installation Guide (
> https://access.redhat.com/documentation/en-us/red_hat_
> satellite/5.8/html-single/installation_guide/index Section 2.4.8) has a
> note that saying not to do this as it would cause problems between jabberd
> and OSAD (exactly what I was seeing) but this warning is NOT present in the
> up-to-date install guide for Spacewalk ( https://github.com/
> spacewalkproject/spacewalk/wiki/HowToInstall ). I think that needs to be
> fixed.
> Here is the bug report that tipped me off to this issue:
> https://bugzilla.redhat.com/show_bug.cgi?id=528145
>
> I've never used github aside from downloading releases and contributing to
> bug reports, so I don't know how to edit the wiki myself (looks like I have
> to make a clone/fork of it, and then a pull request with my changed
> version?) If someone wouldn't mind adding a note about using all-lower-case
> hostnames, maybe copied directly from the Satellite Install Guide, I think
> that would help future users. Nothing in the outputs of jabberd-c2s or osad
> help point to this being an issue, you just get errors like "no host
> available for requested domain", "SASL callback for non-existing host", and
> "bind.c:38 not auth'd, offering auth and register".
>
> Hope this helps someone (maybe a future person searching for a solution to
> this issue),
> Bruce
>
> Bruce Wainer
>
> On Wed, Jun 28, 2017 at 1:56 AM, Bruce Wainer 
> wrote:
>
>> Robert,
>>
>> I beg to differ. I have looked that up, and that string appears in every
>> single error that osa-dispatcher throws. It appears to be an incorrectly
>> written exception handling code, that causes its own exception. It always
>> appears right after "('Error caught:',)" which was clearly intended to
>> print out a particular error message, but instead fails and causes another
>> exception. See:
>> https://www.redhat.com/archives/spacewalk-list/2016-June/msg00021.html
>> https://www.redhat.com/archives/spacewalk-list/2016-Septembe
>> r/msg3.html
>> https://bugzilla.redhat.com/show_bug.cgi?id=1336426 (this isn't a bug
>> for this issue, just one that has a log that shows this activity)
>> http://spacewalk-list.redhat.narkive.com/k0ly5UDb/error-conn
>> ecting-to-jabber
>>
>> These are all cases where different osa-dispatcher errors all are
>> followed by
>> ('Error caught:',)
>> ERROR: unhandled exception occurred: (unicode argument expected, got
>> 'str')
>>
>> So I have to conclude that this particular message is not the cause of my
>> problem. And even if it were, I don't see any way I could have caused or
>> fix this error. My hostname doesn't have unicode in it, and expecting
>> unicode in a hostname would be very silly (allowing unicode in a hostname
>> might be ok, but not requiring it). The fact that there is an unhandled
>> exception at all means that there is a bug in the code, but I'm 99% sure
>> that is in the Error-handling code and not something that is functional to
>> the program. If you really think this is the problem that is affecting me,
>> please provide some help as to fixing it, as Google brings up nothing.
>>
>> Bruce Wainer
>>
>> On Wed, Jun 28, 2017 at 1:22 AM, Robert Paschedag <
>> robert.pasche...@web.de> wrote:
>>
>>>
>>> Jun 27 16:59:05 NETMAN osa-dispatcher: ERROR: unhandled exception
>>> occurred: (unicode argument expected, got 'str').
>>>
>>> That's your reason.
>>>
>>>
>>
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Bruce Wainer]

After leaving this be a few months I returned to the issue. I found the
cause to be that my hostname had capitalized letters in it. Renaming the
host with all lowercase and running the spacewalk-hostname-rename script
resolved the issue. Apparently, the Satellite 5.8 Installation Guide (
https://access.redhat.com/documentation/en-us/red_hat_satellite/5.8/html-single/installation_guide/index
Section 2.4.8) has a note that saying not to do this as it would cause
problems between jabberd and OSAD (exactly what I was seeing) but this
warning is NOT present in the up-to-date install guide for Spacewalk (
https://github.com/spacewalkproject/spacewalk/wiki/HowToInstall ). I think
that needs to be fixed.
Here is the bug report that tipped me off to this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=528145

I've never used github aside from downloading releases and contributing to
bug reports, so I don't know how to edit the wiki myself (looks like I have
to make a clone/fork of it, and then a pull request with my changed
version?) If someone wouldn't mind adding a note about using all-lower-case
hostnames, maybe copied directly from the Satellite Install Guide, I think
that would help future users. Nothing in the outputs of jabberd-c2s or osad
help point to this being an issue, you just get errors like "no host
available for requested domain", "SASL callback for non-existing host", and
"bind.c:38 not auth'd, offering auth and register".

Hope this helps someone (maybe a future person searching for a solution to
this issue),
Bruce

Bruce Wainer

On Wed, Jun 28, 2017 at 1:56 AM, Bruce Wainer  wrote:

> Robert,
>
> I beg to differ. I have looked that up, and that string appears in every
> single error that osa-dispatcher throws. It appears to be an incorrectly
> written exception handling code, that causes its own exception. It always
> appears right after "('Error caught:',)" which was clearly intended to
> print out a particular error message, but instead fails and causes another
> exception. See:
> https://www.redhat.com/archives/spacewalk-list/2016-June/msg00021.html
> https://www.redhat.com/archives/spacewalk-list/2016-
> September/msg3.html
> https://bugzilla.redhat.com/show_bug.cgi?id=1336426 (this isn't a bug for
> this issue, just one that has a log that shows this activity)
> http://spacewalk-list.redhat.narkive.com/k0ly5UDb/error-
> connecting-to-jabber
>
> These are all cases where different osa-dispatcher errors all are followed
> by
> ('Error caught:',)
> ERROR: unhandled exception occurred: (unicode argument expected, got 'str')
>
> So I have to conclude that this particular message is not the cause of my
> problem. And even if it were, I don't see any way I could have caused or
> fix this error. My hostname doesn't have unicode in it, and expecting
> unicode in a hostname would be very silly (allowing unicode in a hostname
> might be ok, but not requiring it). The fact that there is an unhandled
> exception at all means that there is a bug in the code, but I'm 99% sure
> that is in the Error-handling code and not something that is functional to
> the program. If you really think this is the problem that is affecting me,
> please provide some help as to fixing it, as Google brings up nothing.
>
> Bruce Wainer
>
> On Wed, Jun 28, 2017 at 1:22 AM, Robert Paschedag  > wrote:
>
>>
>> Jun 27 16:59:05 NETMAN osa-dispatcher: ERROR: unhandled exception
>> occurred: (unicode argument expected, got 'str').
>>
>> That's your reason.
>>
>>
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Bruce Wainer]

Robert,

I beg to differ. I have looked that up, and that string appears in every
single error that osa-dispatcher throws. It appears to be an incorrectly
written exception handling code, that causes its own exception. It always
appears right after "('Error caught:',)" which was clearly intended to
print out a particular error message, but instead fails and causes another
exception. See:
https://www.redhat.com/archives/spacewalk-list/2016-June/msg00021.html
https://www.redhat.com/archives/spacewalk-list/2016-September/msg3.html
https://bugzilla.redhat.com/show_bug.cgi?id=1336426 (this isn't a bug for
this issue, just one that has a log that shows this activity)
http://spacewalk-list.redhat.narkive.com/k0ly5UDb/error-connecting-to-jabber

These are all cases where different osa-dispatcher errors all are followed
by
('Error caught:',)
ERROR: unhandled exception occurred: (unicode argument expected, got 'str')

So I have to conclude that this particular message is not the cause of my
problem. And even if it were, I don't see any way I could have caused or
fix this error. My hostname doesn't have unicode in it, and expecting
unicode in a hostname would be very silly (allowing unicode in a hostname
might be ok, but not requiring it). The fact that there is an unhandled
exception at all means that there is a bug in the code, but I'm 99% sure
that is in the Error-handling code and not something that is functional to
the program. If you really think this is the problem that is affecting me,
please provide some help as to fixing it, as Google brings up nothing.

Bruce Wainer

On Wed, Jun 28, 2017 at 1:22 AM, Robert Paschedag 
wrote:

>
> Jun 27 16:59:05 NETMAN osa-dispatcher: ERROR: unhandled exception
> occurred: (unicode argument expected, got 'str').
>
> That's your reason.
>
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Robert Paschedag]

ROR: unhandled exception
>occurred:
>(unicode argument expected, got 'str').
>Jun 27 16:59:05 NETMAN systemd: osa-dispatcher.service: control process
>exited, code=exited status=255
>Jun 27 16:59:05 NETMAN systemd: Failed to start OSA Dispatcher daemon.
>Jun 27 16:59:05 NETMAN systemd: Unit osa-dispatcher.service entered
>failed
>state.
>Jun 27 16:59:05 NETMAN systemd: osa-dispatcher.service failed.
>
>The three errors logged by osa-dispatcher seem to be caused by the
>jabberd/c2s error. Also, the URL listed in the error is a page that
>requires a RedHat support account which I do not have.
>
>As a followup to the prior messages, here is a snippet from
>/etc/jabberd/c2s.xml:
>
>...
>
>...
> pemfile="/etc/pki/spacewalk/jabberd/server.pem" realm=""
>register-enable="true">NETMAN.ad.brucewainer.com
>...
>
>...
>
>
>and from /etc/jabberd/sm.xml:
>
>NETMAN.ad.brucewainer.com
>...
>
>...
>NETMAN.ad.brucewainer.com
>...
>
>...
>
>
>Again, both of these files seem to have been pre-configured properly by
>the
>install script, and if there was a problem with these files it would
>mean
>there is a bug in the installer, as I haven't edited these files, and
>there
>was no instruction to do so.
>
>Bruce
>
>Bruce Wainer
>
>On Tue, Jun 27, 2017 at 12:19 PM, Robert Paschedag
><robert.pasche...@web.de>
>wrote:
>
>> Am 27. Juni 2017 17:43:22 MESZ schrieb Bruce Wainer
><br...@brucewainer.com
>> >:
>> >Robert,
>> >
>> >Thanks for the attempt at helping, but I've already checked these
>two
>> >xml files. The spacewalk installer had properly set up the 
>> >entries, and the redhat troubleshooting page I linked in my original
>> >thread includes checking the contents of these files also. I believe
>I
>> >have also looked at this particular page as well in the past - I
>really
>> >have looked at almost every google result for relevant search terms
>on
>> >this error.
>> >
>> >Bruce
>> >
>> >> On Jun 27, 2017, at 7:23 AM, Robert Paschedag
>> ><robert.pasche...@web.de> wrote:
>> >>
>> >>
>> >> Hi Bruce,
>> >>
>> >> maybe this might help. Just a quick googleing.
>> >>
>> >> https://discussions.apple.com/thread/3706169?start=0=0 (not
>a
>> >spacewalk link... I know ;-) )
>> >>
>> >> Robert
>> >>
>> >> Gesendet: Dienstag, 27. Juni 2017 um 08:18 Uhr
>> >> Von: "Bruce Wainer" <br...@brucewainer.com>
>> >> An: spacewalk-list@redhat.com
>> >> Betreff: Re: [Spacewalk-list] Problem installing Spacewalk on
>CentOS7
>> >(Brand new install)
>> >> Robert,
>> >> Using any type of DNS lookup tool does properly resolve the FQDN
>to
>> >the machine's IP address, both on this machine and on others in the
>> >network that use the internal DNS servers. Is reverse lookups (IP ->
>> >FQDN) required as well?
>> >>
>> >> # host netman.ad.brucewainer.com
>> >> netman.ad.brucewainer.com has address 192.168.10.20
>> >>
>> >> Thanks,
>> >> Bruce
>> >>
>> >> Bruce Wainer
>> >>
>> >>> On Tue, Jun 27, 2017 at 12:34 AM, Robert Paschedag
>> ><robert.pasche...@web.de> wrote:
>> >>> Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer
>> ><br...@brucewainer.com>:
>> >>> >Hello all,
>> >>> >
>> >>> >I have found an issue installing SpaceWalk on CentOS7 that I
>have
>> >not
>> >>> >been
>> >>> >able to diagnose/resolve (aside from the required downgrade of
>c3p0
>> >as
>> >>> >mentioned here
>https://bugzilla.redhat.com/show_bug.cgi?id=1442140
>> >).
>> >>> >
>> >>> >Issue: osa-dispatcher.service crashes on start with "'Not able
>to
>> >>> >reconnect"
>> >>> >
>> >>> >Background Information: Brand new install of CentOS7, set the
>> >hostname
>> >>> >durin the installer, ran updates, made sure hostname was correct
>in
>> >all
>> >>> >locations including /etc/hosts, followed the spacewalk
>installation
>> >>> >instructions verbatim.
>> >>> >
>> >>> >Every time osa-dispatcher is started, "journal -xe" logs the
>> >follow

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Bruce Wainer]

abberd/c2s error. Also, the URL listed in the error is a page that
requires a RedHat support account which I do not have.

As a followup to the prior messages, here is a snippet from
/etc/jabberd/c2s.xml:

...

...
 NETMAN.ad.brucewainer.com
...

...


and from /etc/jabberd/sm.xml:

NETMAN.ad.brucewainer.com
...

...
NETMAN.ad.brucewainer.com
...

...


Again, both of these files seem to have been pre-configured properly by the
install script, and if there was a problem with these files it would mean
there is a bug in the installer, as I haven't edited these files, and there
was no instruction to do so.

Bruce

Bruce Wainer

On Tue, Jun 27, 2017 at 12:19 PM, Robert Paschedag <robert.pasche...@web.de>
wrote:

> Am 27. Juni 2017 17:43:22 MESZ schrieb Bruce Wainer <br...@brucewainer.com
> >:
> >Robert,
> >
> >Thanks for the attempt at helping, but I've already checked these two
> >xml files. The spacewalk installer had properly set up the 
> >entries, and the redhat troubleshooting page I linked in my original
> >thread includes checking the contents of these files also. I believe I
> >have also looked at this particular page as well in the past - I really
> >have looked at almost every google result for relevant search terms on
> >this error.
> >
> >Bruce
> >
> >> On Jun 27, 2017, at 7:23 AM, Robert Paschedag
> ><robert.pasche...@web.de> wrote:
> >>
> >>
> >> Hi Bruce,
> >>
> >> maybe this might help. Just a quick googleing.
> >>
> >> https://discussions.apple.com/thread/3706169?start=0=0 (not a
> >spacewalk link... I know ;-) )
> >>
> >> Robert
> >>
> >> Gesendet: Dienstag, 27. Juni 2017 um 08:18 Uhr
> >> Von: "Bruce Wainer" <br...@brucewainer.com>
> >> An: spacewalk-list@redhat.com
> >> Betreff: Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7
> >(Brand new install)
> >> Robert,
> >> Using any type of DNS lookup tool does properly resolve the FQDN to
> >the machine's IP address, both on this machine and on others in the
> >network that use the internal DNS servers. Is reverse lookups (IP ->
> >FQDN) required as well?
> >>
> >> # host netman.ad.brucewainer.com
> >> netman.ad.brucewainer.com has address 192.168.10.20
> >>
> >> Thanks,
> >> Bruce
> >>
> >> Bruce Wainer
> >>
> >>> On Tue, Jun 27, 2017 at 12:34 AM, Robert Paschedag
> ><robert.pasche...@web.de> wrote:
> >>> Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer
> ><br...@brucewainer.com>:
> >>> >Hello all,
> >>> >
> >>> >I have found an issue installing SpaceWalk on CentOS7 that I have
> >not
> >>> >been
> >>> >able to diagnose/resolve (aside from the required downgrade of c3p0
> >as
> >>> >mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=1442140
> >).
> >>> >
> >>> >Issue: osa-dispatcher.service crashes on start with "'Not able to
> >>> >reconnect"
> >>> >
> >>> >Background Information: Brand new install of CentOS7, set the
> >hostname
> >>> >durin the installer, ran updates, made sure hostname was correct in
> >all
> >>> >locations including /etc/hosts, followed the spacewalk installation
> >>> >instructions verbatim.
> >>> >
> >>> >Every time osa-dispatcher is started, "journal -xe" logs the
> >following
> >>> >3
> >>> >times (I think due to three connection attempts)
> >>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
> >>> >[:::192.168.10.20, port=45018] connect
> >>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
> >>> >[:::192.168.10.20, port=45018] disconnect jid=unbound, packets:
> >0,
> >>> >bytes: 168
> >>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >>> >callback
> >>> >for non-existing host: NETMAN.ad.brucewainer.com
> >>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >>> >callback
> >>> >for non-existing host: NETMAN.ad.brucewainer.com
> >>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >>> >callback
> >>> >for non-existing host: NETMAN.ad.brucewainer.com
> >>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SAS

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Robert Paschedag]

Am 27. Juni 2017 17:43:22 MESZ schrieb Bruce Wainer <br...@brucewainer.com>:
>Robert,
>
>Thanks for the attempt at helping, but I've already checked these two
>xml files. The spacewalk installer had properly set up the 
>entries, and the redhat troubleshooting page I linked in my original
>thread includes checking the contents of these files also. I believe I
>have also looked at this particular page as well in the past - I really
>have looked at almost every google result for relevant search terms on
>this error.
>
>Bruce
>
>> On Jun 27, 2017, at 7:23 AM, Robert Paschedag
><robert.pasche...@web.de> wrote:
>> 
>>  
>> Hi Bruce,
>>  
>> maybe this might help. Just a quick googleing.
>>  
>> https://discussions.apple.com/thread/3706169?start=0=0 (not a
>spacewalk link... I know ;-) )
>>  
>> Robert
>>  
>> Gesendet: Dienstag, 27. Juni 2017 um 08:18 Uhr
>> Von: "Bruce Wainer" <br...@brucewainer.com>
>> An: spacewalk-list@redhat.com
>> Betreff: Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7
>(Brand new install)
>> Robert,
>> Using any type of DNS lookup tool does properly resolve the FQDN to
>the machine's IP address, both on this machine and on others in the
>network that use the internal DNS servers. Is reverse lookups (IP ->
>FQDN) required as well?
>> 
>> # host netman.ad.brucewainer.com
>> netman.ad.brucewainer.com has address 192.168.10.20
>>  
>> Thanks,
>> Bruce
>>  
>> Bruce Wainer
>>  
>>> On Tue, Jun 27, 2017 at 12:34 AM, Robert Paschedag
><robert.pasche...@web.de> wrote:
>>> Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer
><br...@brucewainer.com>:
>>> >Hello all,
>>> >
>>> >I have found an issue installing SpaceWalk on CentOS7 that I have
>not
>>> >been
>>> >able to diagnose/resolve (aside from the required downgrade of c3p0
>as
>>> >mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=1442140
>).
>>> >
>>> >Issue: osa-dispatcher.service crashes on start with "'Not able to
>>> >reconnect"
>>> >
>>> >Background Information: Brand new install of CentOS7, set the
>hostname
>>> >durin the installer, ran updates, made sure hostname was correct in
>all
>>> >locations including /etc/hosts, followed the spacewalk installation
>>> >instructions verbatim.
>>> >
>>> >Every time osa-dispatcher is started, "journal -xe" logs the
>following
>>> >3
>>> >times (I think due to three connection attempts)
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>>> >[:::192.168.10.20, port=45018] connect
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>>> >[:::192.168.10.20, port=45018] disconnect jid=unbound, packets:
>0,
>>> >bytes: 168
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>>> >callback
>>> >for non-existing host: NETMAN.ad.brucewainer.com
>>

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Bruce Wainer]

Robert,

Thanks for the attempt at helping, but I've already checked these two xml 
files. The spacewalk installer had properly set up the  entries, and the 
redhat troubleshooting page I linked in my original thread includes checking 
the contents of these files also. I believe I have also looked at this 
particular page as well in the past - I really have looked at almost every 
google result for relevant search terms on this error.

Bruce

> On Jun 27, 2017, at 7:23 AM, Robert Paschedag <robert.pasche...@web.de> wrote:
> 
>  
> Hi Bruce,
>  
> maybe this might help. Just a quick googleing.
>  
> https://discussions.apple.com/thread/3706169?start=0=0 (not a 
> spacewalk link... I know ;-) )
>  
> Robert
>  
> Gesendet: Dienstag, 27. Juni 2017 um 08:18 Uhr
> Von: "Bruce Wainer" <br...@brucewainer.com>
> An: spacewalk-list@redhat.com
> Betreff: Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand 
> new install)
> Robert,
> Using any type of DNS lookup tool does properly resolve the FQDN to the 
> machine's IP address, both on this machine and on others in the network that 
> use the internal DNS servers. Is reverse lookups (IP -> FQDN) required as 
> well?
> 
> # host netman.ad.brucewainer.com
> netman.ad.brucewainer.com has address 192.168.10.20
>  
> Thanks,
> Bruce
>  
> Bruce Wainer
>  
>> On Tue, Jun 27, 2017 at 12:34 AM, Robert Paschedag <robert.pasche...@web.de> 
>> wrote:
>> Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer <br...@brucewainer.com>:
>> >Hello all,
>> >
>> >I have found an issue installing SpaceWalk on CentOS7 that I have not
>> >been
>> >able to diagnose/resolve (aside from the required downgrade of c3p0 as
>> >mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=1442140 ).
>> >
>> >Issue: osa-dispatcher.service crashes on start with "'Not able to
>> >reconnect"
>> >
>> >Background Information: Brand new install of CentOS7, set the hostname
>> >durin the installer, ran updates, made sure hostname was correct in all
>> >locations including /etc/hosts, followed the spacewalk installation
>> >instructions verbatim.
>> >
>> >Every time osa-dispatcher is started, "journal -xe" logs the following
>> >3
>> >times (I think due to three connection attempts)
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>> >[:::192.168.10.20, port=45018] connect
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>> >[:::192.168.10.20, port=45018] disconnect jid=unbound, packets: 0,
>> >bytes: 168
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >
>> >Based on this it seems like jabberd isn't recognizing the hostname, but
>> >I
>> >have followed the "Resolution" and "Diagnostic Steps" here:
>> >https://access.redhat.com/solutions/327903 to no avail, as well as
>> >every
>>

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Robert Paschedag]

Am 27. Juni 2017 08:18:45 MESZ schrieb Bruce Wainer :
>Robert,
>Using any type of DNS lookup tool does properly resolve the FQDN to the
>machine's IP address, both on this machine and on others in the network
>that use the internal DNS servers. Is reverse lookups (IP -> FQDN)
>required
>as well?
>
># host netman.ad.brucewainer.com
>netman.ad.brucewainer.com has address 192.168.10.20
>
>Thanks,
>Bruce
>
>Bruce Wainer
>
>On Tue, Jun 27, 2017 at 12:34 AM, Robert Paschedag
>
>wrote:
>
>> Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer
>> >:
>> >Hello all,
>> >
>> >I have found an issue installing SpaceWalk on CentOS7 that I have
>not
>> >been
>> >able to diagnose/resolve (aside from the required downgrade of c3p0
>as
>> >mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=1442140
>).
>> >
>> >Issue: osa-dispatcher.service crashes on start with "'Not able to
>> >reconnect"
>> >
>> >Background Information: Brand new install of CentOS7, set the
>hostname
>> >durin the installer, ran updates, made sure hostname was correct in
>all
>> >locations including /etc/hosts, followed the spacewalk installation
>> >instructions verbatim.
>> >
>> >Every time osa-dispatcher is started, "journal -xe" logs the
>following
>> >3
>> >times (I think due to three connection attempts)
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>> >[:::192.168.10.20, port=45018] connect
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>> >[:::192.168.10.20, port=45018] disconnect jid=unbound, packets:
>0,
>> >bytes: 168
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>> >callback
>> >for non-existing host: NETMAN.ad.brucewainer.com
>> >
>> >Based on this it seems like jabberd isn't recognizing the hostname,
>but
>> >I
>> >have followed the "Resolution" and "Diagnostic Steps" here:
>> >https://access.redhat.com/solutions/327903 to no avail, as well as
>> >every
>> >other google result related to "SASL callback for non-existing
>host".
>> >Since
>> >my hostname was set during the installation, it was automatically
>and
>> >correctly put into every config file that matters, other than
>> >/etc/hosts
>> >which I have rechecked a haf dozen times. You can see in the
>journalctl
>> >output that the host that jabberd is seeing matches the actual
>> >hostname.
>> >I've done the complete setup from scratch twice to make sure I
>hadn't
>> >missed any step in the installation instructions.
>> >
>> >Joe Belliveau, it sounded like you ran into an issue like this with
>> >your
>> >new install?
>> >
>> >Thanks in advance for any assistance,
>> >Bruce Wainer
>>
>> So Testing your DNS resolution with "dig" or "host" or "nslookup"
>does
>> resolve your hostname correctly?
>>
>> Just found this right now but it looks there was no answer yet...
>>
>>
>https://www.redhat.com/archives/spacewalk-list/2017-February/msg00022.html
>>
>> Robert
>>
>>
>>

Hi Bruce,

No, PTR record is not a must have here.

Please check the jabber configuration files in /etc/jabberd/

c2s.xml

And the others. Just don't have them on my mind right now. Sorry. Be sure, that 
the "" tags are correct.

Robert

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Robert Paschedag]

 

Hi Bruce,

 

maybe this might help. Just a quick googleing.

 

https://discussions.apple.com/thread/3706169?start=0=0 (not a spacewalk link... I know ;-) )

 

Robert

 


Gesendet: Dienstag, 27. Juni 2017 um 08:18 Uhr
Von: "Bruce Wainer" <br...@brucewainer.com>
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)





Robert,
Using any type of DNS lookup tool does properly resolve the FQDN to the machine's IP address, both on this machine and on others in the network that use the internal DNS servers. Is reverse lookups (IP -> FQDN) required as well?

# host netman.ad.brucewainer.com
netman.ad.brucewainer.com has address 192.168.10.20
 
Thanks,
Bruce

 

Bruce Wainer

 

On Tue, Jun 27, 2017 at 12:34 AM, Robert Paschedag <robert.pasche...@web.de> wrote:



Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer <br...@brucewainer.com>:
>Hello all,
>
>I have found an issue installing SpaceWalk on CentOS7 that I have not
>been
>able to diagnose/resolve (aside from the required downgrade of c3p0 as
>mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=1442140 ).
>
>Issue: osa-dispatcher.service crashes on start with "'Not able to
>reconnect"
>
>Background Information: Brand new install of CentOS7, set the hostname
>durin the installer, ran updates, made sure hostname was correct in all
>locations including /etc/hosts, followed the spacewalk installation
>instructions verbatim.
>
>Every time osa-dispatcher is started, "journal -xe" logs the following
>3
>times (I think due to three connection attempts)
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>[:::192.168.10.20, port=45018] connect
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>[:::192.168.10.20, port=45018] disconnect jid=unbound, packets: 0,
>bytes: 168
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>
>Based on this it seems like jabberd isn't recognizing the hostname, but
>I
>have followed the "Resolution" and "Diagnostic Steps" here:
>https://access.redhat.com/solutions/327903 to no avail, as well as
>every
>other google result related to "SASL callback for non-existing host".
>Since
>my hostname was set during the installation, it was automatically and
>correctly put into every config file that matters, other than
>/etc/hosts
>which I have rechecked a haf dozen times. You can see in the journalctl
>output that the host that jabberd is seeing matches the actual
>hostname.
>I've done the complete setup from scratch twice to make sure I hadn't
>missed any step in the installation instructions.
>
>Joe Belliveau, it sounded like you ran into an issue like this with
>your
>new install?
>
>Thanks in advance for any assistance,
>Bruce Wainer
 

So Testing your DNS resolution with "dig" or "host" or "nslookup" does resolve your hostname correctly?

Just found this right now but it looks there was no answer yet...

https://www.redhat.com/archives/spacewalk-list/2017-February/msg00022.html

Robert

 



___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list




___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Bruce Wainer]

Robert,
Using any type of DNS lookup tool does properly resolve the FQDN to the
machine's IP address, both on this machine and on others in the network
that use the internal DNS servers. Is reverse lookups (IP -> FQDN) required
as well?

# host netman.ad.brucewainer.com
netman.ad.brucewainer.com has address 192.168.10.20

Thanks,
Bruce

Bruce Wainer

On Tue, Jun 27, 2017 at 12:34 AM, Robert Paschedag 
wrote:

> Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer  >:
> >Hello all,
> >
> >I have found an issue installing SpaceWalk on CentOS7 that I have not
> >been
> >able to diagnose/resolve (aside from the required downgrade of c3p0 as
> >mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=1442140 ).
> >
> >Issue: osa-dispatcher.service crashes on start with "'Not able to
> >reconnect"
> >
> >Background Information: Brand new install of CentOS7, set the hostname
> >durin the installer, ran updates, made sure hostname was correct in all
> >locations including /etc/hosts, followed the spacewalk installation
> >instructions verbatim.
> >
> >Every time osa-dispatcher is started, "journal -xe" logs the following
> >3
> >times (I think due to three connection attempts)
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
> >[:::192.168.10.20, port=45018] connect
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
> >[:::192.168.10.20, port=45018] disconnect jid=unbound, packets: 0,
> >bytes: 168
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
> >callback
> >for non-existing host: NETMAN.ad.brucewainer.com
> >
> >Based on this it seems like jabberd isn't recognizing the hostname, but
> >I
> >have followed the "Resolution" and "Diagnostic Steps" here:
> >https://access.redhat.com/solutions/327903 to no avail, as well as
> >every
> >other google result related to "SASL callback for non-existing host".
> >Since
> >my hostname was set during the installation, it was automatically and
> >correctly put into every config file that matters, other than
> >/etc/hosts
> >which I have rechecked a haf dozen times. You can see in the journalctl
> >output that the host that jabberd is seeing matches the actual
> >hostname.
> >I've done the complete setup from scratch twice to make sure I hadn't
> >missed any step in the installation instructions.
> >
> >Joe Belliveau, it sounded like you ran into an issue like this with
> >your
> >new install?
> >
> >Thanks in advance for any assistance,
> >Bruce Wainer
>
> So Testing your DNS resolution with "dig" or "host" or "nslookup" does
> resolve your hostname correctly?
>
> Just found this right now but it looks there was no answer yet...
>
> https://www.redhat.com/archives/spacewalk-list/2017-February/msg00022.html
>
> Robert
>
>
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problem installing Spacewalk on CentOS7 (Brand new install)

[Robert Paschedag]

Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer :
>Hello all,
>
>I have found an issue installing SpaceWalk on CentOS7 that I have not
>been
>able to diagnose/resolve (aside from the required downgrade of c3p0 as
>mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=1442140 ).
>
>Issue: osa-dispatcher.service crashes on start with "'Not able to
>reconnect"
>
>Background Information: Brand new install of CentOS7, set the hostname
>durin the installer, ran updates, made sure hostname was correct in all
>locations including /etc/hosts, followed the spacewalk installation
>instructions verbatim.
>
>Every time osa-dispatcher is started, "journal -xe" logs the following
>3
>times (I think due to three connection attempts)
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>[:::192.168.10.20, port=45018] connect
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>[:::192.168.10.20, port=45018] disconnect jid=unbound, packets: 0,
>bytes: 168
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: SASL
>callback
>for non-existing host: NETMAN.ad.brucewainer.com
>
>Based on this it seems like jabberd isn't recognizing the hostname, but
>I
>have followed the "Resolution" and "Diagnostic Steps" here:
>https://access.redhat.com/solutions/327903 to no avail, as well as
>every
>other google result related to "SASL callback for non-existing host".
>Since
>my hostname was set during the installation, it was automatically and
>correctly put into every config file that matters, other than
>/etc/hosts
>which I have rechecked a haf dozen times. You can see in the journalctl
>output that the host that jabberd is seeing matches the actual
>hostname.
>I've done the complete setup from scratch twice to make sure I hadn't
>missed any step in the installation instructions.
>
>Joe Belliveau, it sounded like you ran into an issue like this with
>your
>new install?
>
>Thanks in advance for any assistance,
>Bruce Wainer

So Testing your DNS resolution with "dig" or "host" or "nslookup" does 
resolve your hostname correctly?

Just found this right now but it looks there was no answer yet...

https://www.redhat.com/archives/spacewalk-list/2017-February/msg00022.html

Robert



___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list