Robert, Here is everything that is logged in /var/log/messages from the time I call "systemctl start osa-dispatcher" to the time that the process dies:
Jun 27 16:59:02 NETMAN systemd: Starting OSA Dispatcher daemon... Jun 27 16:59:02 NETMAN jabberd/c2s[996]: [7] [::1, port=57726] connect Jun 27 16:59:02 NETMAN jabberd/c2s[996]: [7] [::1, port=57726] disconnect jid=unbound, packets: 0, bytes: 168 Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:02 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: [7] [::1, port=57728] connect Jun 27 16:59:03 NETMAN jabberd/c2s[996]: [7] [::1, port=57728] disconnect jid=unbound, packets: 0, bytes: 168 Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:03 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: [7] [::1, port=57730] connect Jun 27 16:59:04 NETMAN jabberd/c2s[996]: [7] [::1, port=57730] disconnect jid=unbound, packets: 0, bytes: 168 Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:04 NETMAN jabberd/c2s[996]: SASL callback for non-existing host: NETMAN.ad.brucewainer.com Jun 27 16:59:05 NETMAN osa-dispatcher: Spacewalk 2974 2017/06/27 16:59:05 -04:00: ('Not able to reconnect - See https://access.redhat.com/solutions/45332 for possible solutions.\n',) Jun 27 16:59:05 NETMAN osa-dispatcher: Spacewalk 2974 2017/06/27 16:59:05 -04:00: ('Error caught:',) Jun 27 16:59:05 NETMAN osa-dispatcher: ERROR: 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: <c2s> ... <local> ... <id require-starttls="false" pemfile="/etc/pki/spacewalk/jabberd/server.pem" realm="" register-enable="true">NETMAN.ad.brucewainer.com</id> ... </local> ... </c2s> and from /etc/jabberd/sm.xml: <sm> <id>NETMAN.ad.brucewainer.com</id> ... <local> ... <id>NETMAN.ad.brucewainer.com</id> ... </local> ... </sm> 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 <id> > >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&tstart=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] > >>> >[::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 > >>> > >>> > >> _______________________________________________ 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 > > Is there something mentioned in /var/log/messages? > > Robert >
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list