I am running spacewalk 2.6 on CentOS Linux release 7.4.1708 (Core) and on starting spacewalk with spacewalk-service start I observe: jabberd.service - Jabber Server Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled; vendor preset: disabled) Active: active (exited) since Wed 2018-02-28 16:24:06 UTC; 7h ago Process: 4644 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 4644 (code=exited, status=0/SUCCESS) Memory: 0B CGroup: /system.slice/jabberd.serviceUpon further investigation, and googling #journalctl -xeMar 01 00:21:58 gss-spacewalk-1-prod.aws.a.b.c jabberd/c2s[4642]: SASL callback for non-existing host: spacewalk.a.b.cMar 01 00:23:13 gss-spacewalk-1-prod.aws.a.b.c jabberd/c2s[4642]: [25] [::ffff:1x.1xx.1xx.82, port=46909] connectMar 01 00:23:13 gss-spacewalk-1-prod.aws.a.b.c. jabberd/c2s[4642]: [25] [::ffff:1x.1xx.1xx.82, port=46909] disconnect jid=unbound, pacMar 01 00:23:13 gss-spacewalk-1-prod.aws.a.b.c. jabberd/c2s[4642]: SASL callback for non-existing host: spacewalk.a.b.c.now spacewalk.a.b.c seems to be an aws load balancer: $nslookup spacewalk.a.b.cServer: 1x.xx.xxx.80Address: 1x.xx.1xx.80#53 spacewalk.a.b.c canonical name = internal-GSS-Spacewalk-123456789.us-east-1.elb.amazonaws.com.Name: internal-GSS-Spacewalk-123456789.us-east-1.elb.amazonaws.comAddress: 1x.1xx.1xx.55Name: internal-GSS-Spacewalk-123456789.us-east-1.elb.amazonaws.comAddress: 1x.1xx.1xx.82I have searched forums and blogs, but cannot find a resolution of this jabberd not starting
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
