Estou executando o espaço 2.6 no CentOS Linux versão 7.4.1708 (Core)
e ao iniciar o passeio espacial com o início do serviço de caminhada no espaço
Eu observo:
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.service
Após investigação adicional e pesquisando
#journalctl -xe
Mar 01 00:21:58 gss-spacewalk-1-prod.aws.a.b.c jabberd/c2s[4642]: SASL callback for non-existing host: spacewalk.a.b.c
Mar 01 00:23:13 gss-spacewalk-1-prod.aws.a.b.c jabberd/c2s[4642]: [25] [::ffff:1x.1xx.1xx.82, port=46909] connect
Mar 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, pac
Mar 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.
agora spacewalk.a.b.c parece ser um balanceador de carga aws:
$nslookup spacewalk.a.b.c
Server: 1x.xx.xxx.80
Address: 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.com
Address: 1x.1xx.1xx.55
Name: internal-GSS-Spacewalk-123456789.us-east-1.elb.amazonaws.com
Address: 1x.1xx.1xx.82
Eu pesquisei fóruns e blogs, mas não consigo encontrar uma resolução desse jabberd que não esteja iniciando
--------------- responder a @tukan ---------------------------- --------
Na verdade, existem 6 programas que são executados quando o jabberd é iniciado. Seus executáveis estão localizados nos seguintes locais:
1. /usr/bin/c2s
2. /usr/bin/jabberd
3. /usr/bin/resolver
4. /usr/bin/router
5. /usr/bin/s2s
6. /usr/bin/sm
jabberd configuration:
1. /usr/bin/c2s -c /etc/jabberd/c2s.xml https://pastebin.com/A1Qp44qp
2. /usr/bin/jabberd itself does not have a config ??
3. /usr/bin/sm -c /etc/jabberd/sm.xml https://pastebin.com/4gi4MR3g
4. /usr/bin/router -c /etc/jabberd/router.xml https://pastebin.com/cdRZqk5D
5. /usr/bin/s2s -c /etc/jabberd/s2s.xml https://pastebin.com/nPsMsde3
6. /usr/bin/sm -c /etc/jabberd/sm.xml https://pastebin.com/s7vQu3VE
c2s and sm are configured to encrypt information that passes through them. The cert and key used to do this are located in the /etc/jabberd/server.pem file.
ports:
[root@gss-spacewalk-1-prod jabberd]# nmap -sT -p 5200-5400 localhost
Starting Nmap 6.40 ( http://nmap.org ) at 2018-03-09 19:11 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00022s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 198 closed ports
PORT STATE SERVICE
5222/tcp open xmpp-client
5269/tcp open xmpp-server
5347/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds
[root@gss-spacewalk-1-prod jabberd]# netstat -nl | head
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:20048 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:36536 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25151 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:32000 0.0.0.0:* LISTEN
--------------------- Configuração do Firewall ------------------------ ---------------
# service iptables status
iptables: Firewall is not running.
# sestatus
SELinux status: enabled
SELinuxfs mount: /selinux
Current mode: enforcing
Mode from config file: enforcing
Policy version: 24
Policy from config file: targeted