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

[Robert Paschedag]

Am 27. Juni 2017 08:18:45 MESZ schrieb Bruce Wainer <bruce at brucewainer.com>:
>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.paschedag at web.de>
>wrote:
>
>> Am 27. Juni 2017 03:25:00 MESZ schrieb Bruce Wainer
><bruce at 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]
>> >[::ffff:192.168.10.20, port=45018] connect
>> >Jun 26 21:09:37 NETMAN.ad.brucewainer.com jabberd/c2s[1003]: [7]
>> >[::ffff: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 "<id>" tags are correct.

Robert