LINUX.ORG.RU
ФорумAdmin

Debian 10 по SSH доступа нет в логе пусто

 ,


0

1

Помогите, куда посмотреть. Дебиан 10 с последними обновлениями на HP Microserver N40L Стучу по ssh - тишина. Ребут по ресету - в логе пусто, только странный перерыв в логе между 5:45 и ручным ребутом в 18:22

Aug 14 05:17:01 dc CRON[15955]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Aug 14 05:19:51 dc syncthing[11840]: [B6XAB] INFO: Peer at 192.168.1.10:22000-192.168.1.25:53188/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 did not negotiate bep/1.0
Aug 14 05:24:51 dc syncthing[11840]: [B6XAB] INFO: Peer at 192.168.1.10:22000-192.168.1.25:53282/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 did not negotiate bep/1.0
Aug 14 05:24:51 dc syncthing[11840]: [B6XAB] WARNING: Connecting to OIMNOJP-R6B6NRB-EU2CWTW-RIEDLQG-6MVE23L-IBAU5T6-NHGIPXR-X2PXHQE (192.168.1.25:53282): the remote device speaks an unknown (newer?) version of the protocol
Aug 14 05:25:01 dc CRON[16081]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 14 05:29:51 dc syncthing[11840]: [B6XAB] INFO: Peer at 192.168.1.10:22000-192.168.1.25:53316/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 did not negotiate bep/1.0
Aug 14 05:34:52 dc syncthing[11840]: [B6XAB] INFO: Peer at 192.168.1.10:22000-192.168.1.25:53354/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 did not negotiate bep/1.0
Aug 14 05:35:01 dc CRON[16252]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 14 05:39:01 dc systemd[1]: Starting Clean php session files...
Aug 14 05:39:01 dc CRON[16325]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Aug 14 05:39:01 dc systemd[1]: phpsessionclean.service: Succeeded.
Aug 14 05:39:01 dc systemd[1]: Started Clean php session files.
Aug 14 05:39:52 dc syncthing[11840]: [B6XAB] INFO: Peer at 192.168.1.10:22000-192.168.1.25:53390/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 did not negotiate bep/1.0
Aug 14 05:39:52 dc syncthing[11840]: [B6XAB] WARNING: Connecting to OIMNOJP-R6B6NRB-EU2CWTW-RIEDLQG-6MVE23L-IBAU5T6-NHGIPXR-X2PXHQE (192.168.1.25:53390): the remote device speaks an unknown (newer?) version of the protocol
Aug 14 05:44:52 dc syncthing[11840]: [B6XAB] INFO: Peer at 192.168.1.10:22000-192.168.1.25:53408/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 did not negotiate bep/1.0
Aug 14 05:45:01 dc CRON[16514]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 14 18:22:55 dc kernel: [    0.000000] Linux version 4.19.0-8-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.98-1+deb10u1 (2020-04-27)
Aug 14 18:22:55 dc kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.19.0-8-amd64 root=UUID=5e183ce9-13c4-4ab0-be12-bfb83b270064 ro net.ifnames=0 biosdevname=0 clocksource=acpi_pm quiet
Aug 14 18:22:55 dc kernel: [    0.000000] x86/fpu: x87 FPU will use FXSAVE
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-provided physical RAM map:
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000d7f8ffff] usable
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x00000000d7f9e000-0x00000000d7f9ffff] type 9
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x00000000d7fa0000-0x00000000d7faa5ff] ACPI data
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x00000000d7faa600-0x00000000d7fdffff] ACPI NVS
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x00000000d7fe0000-0x00000000d7ffffff] reserved
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
Aug 14 18:22:55 dc kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000011fffffff] usable
куда еще можно посмотреть найти виноватого?

Сеть вообще настроена, сервер пингуется? Если да, то выше правильно написали - нужно смотреть, запущен ли ssh. Кроме этого неплохо бы проверить правила firewall - возможно, 22 порт закрыт.

Если все запущено и работает, то смотреть нужно файл /var/log/auth.log - там должна быть информация о всех попытках доступа к машине (как удачных, так и нет).

Serge10 ★★★★★ ()