Erro "systemctl status stunnel4.service" and "journalctl -xe"

1. Erro "systemctl status stunnel4.service" and "journalctl -xe"

João Pedro Soares de Lima
Visonsoft

(usa XUbuntu)

Enviado em 21/03/2018 - 15:45h

Ola gentebtudo bem, eu comecei agr e estou tendo um problema na intalacao de ssl na minja ssheu tenho um servidor vpn e faço ssh pra vender pra se conectar com http injetor, porem a oi para se conectar no 3g precisa de uma ssl, mas quando ta quase dando certo e vou dar o ultimo comando, "service stunnel4 start" aparece esses erros systemctl status "stunnel4.service" and "journalctl -xe" alguem me ajuda pf


  


2. Re: Erro "systemctl status stunnel4.service" and "journalctl -xe"

Daniel Lara Souza
danniel-lara

(usa Fedora)

Enviado em 21/03/2018 - 17:19h

journalctl -xe

posta o erro


3. Na mao

João Pedro Soares de Lima
Visonsoft

(usa XUbuntu)

Enviado em 22/03/2018 - 01:20h

[email protected]:~# journalctl -xe
Mar 22 00:15:15 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:16 nippy-cracker CRON[18398]: pam_unix(cron:session): session closed for user root
Mar 22 00:15:17 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:20 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:22 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:26 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:27 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:31 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:32 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:36 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:15 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:16 nippy-cracker CRON[18398]: pam_unix(cron:session): session closed for user root
Mar 22 00:15:17 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:20 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:22 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:26 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:27 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:31 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:32 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:36 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed. Mar 22 00:15:37 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:41 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:43 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:47 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:48 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:52 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed. Mar 22 00:15:53 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed. Mar 22 00:15:57 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:15:59 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:16:01 nippy-cracker sshd[18776]: pam_unix(sshd:auth): authentication failure; logname= uid=0Mar 22 00:16:02 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:16:03 nippy-cracker sshd[18776]: Failed password for root from 35.204.45.13 port 55622 ssh2
Mar 22 00:16:05 nippy-cracker sshd[17067]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:16:06 nippy-cracker sshd[18776]: Connection closed by 35.204.45.13 port 55622 [preauth]
Mar 22 00:16:07 nippy-cracker sshd[16706]: error: connect_to 127.0.0.1 port 7300: failed.
Mar 22 00:16:09 nippy-cracker sshd[18811]: Accepted password for root from 31.220.56.204 port 43396 ssMar 22 00:16:09 nippy-cracker sshd[18811]: pam_unix(sshd:session): session opened for user root by (uiMar 22 00:16:09 nippy-cracker systemd-logind[229]: New session 1233616 of user root.
-- Subject: A new session 1233616 has been created for user root
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--


4. E o outro

João Pedro Soares de Lima
Visonsoft

(usa XUbuntu)

Enviado em 22/03/2018 - 01:24h

[email protected]:~# systemctl status stunnel4.service
● stunnel4.service - LSB: Start or stop stunnel 4.x (SSL tunnel for network daemons)
Loaded: loaded (/etc/init.d/stunnel4; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-03-22 00:07:33 EDT; 13min ago
Docs: man:systemd-sysv-generator(8)
Process: 10093 ExecStop=/etc/init.d/stunnel4 stop (code=exited, status=0/SUCCESS)
Process: 15719 ExecStart=/etc/init.d/stunnel4 start (code=exited, status=1/FAILURE)

Mar 22 00:07:33 nippy-cracker stunnel4[15719]: [!] bind: Address already in use (98)
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: [!] Error binding service [ssh] to 31.220.56.204:443
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: [ ] Closing service [ssh]
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: [ ] Service [ssh] closed
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: failed (no pid=pidfile specified!)
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: You should check that you have specified the pid= in yoMar 22 00:07:33 nippy-cracker systemd[1]: stunnel4.service: Control process exited, code=exited statusMar 22 00:07:33 nippy-cracker systemd[1]: Failed to start LSB: Start or stop stunnel 4.x (SSL tunnel fMar 22 00:07:33 nippy-cracker systemd[1]: stunnel4.service: Unit entered failed state.
Mar 22 00:07:33 nippy-cracker systemd[1]: stunnel4.service: Failed with result 'exit-code'.
...skipping...
● stunnel4.service - LSB: Start or stop stunnel 4.x (SSL tunnel for network daemons)
Loaded: loaded (/etc/init.d/stunnel4; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-03-22 00:07:33 EDT; 13min ago
Docs: man:systemd-sysv-generator(8)
Process: 10093 ExecStop=/etc/init.d/stunnel4 stop (code=exited, status=0/SUCCESS)
Process: 15719 ExecStart=/etc/init.d/stunnel4 start (code=exited, status=1/FAILURE)

Mar 22 00:07:33 nippy-cracker stunnel4[15719]: [!] bind: Address already in use (98)
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: [!] Error binding service [ssh] to 31.220.56.204:443
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: [ ] Closing service [ssh]
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: [ ] Service [ssh] closed
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: failed (no pid=pidfile specified!)
Mar 22 00:07:33 nippy-cracker stunnel4[15719]: You should check that you have specified the pid= in yoMar 22 00:07:33 nippy-cracker systemd[1]: stunnel4.service: Control process exited, code=exited statusMar 22 00:07:33 nippy-cracker systemd[1]: Failed to start LSB: Start or stop stunnel 4.x (SSL tunnel fMar 22 00:07:33 nippy-cracker systemd[1]: stunnel4.service: Unit entered failed state.
Mar 22 00:07:33 nippy-cracker systemd[1]: stunnel4.service: Failed with result 'exit-code'.
~






Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts