[SOLVED] SSH-Login Flut in den Logs normal?

H

hauszduxjso

New Member
Jan 7, 2025
7
0
1
Hi,

ich bin noch Recht neu in Proxmox und habe in letzter Zeit einiges an Erfahrungen gesammelt. Aktuell habe ich 2 Nodes(pve01 und pve02) + 1 Quorum(Windows mit einer Debian VM in VirtualBox) in einem Cluster

Das Funktioniert auch alles so weit so gut. Das Quorum wurde erkannt alles gut.

Nun habe ich aber das Problem das nur auf dem pve02 Node in den Logs permanent irgendwelche Logins gespamt werden.

Oder ist das normal weil der andere Node(pve01) zur Zeit Laut Webinterface-Anzeige der Master ist?

Dankeschön für jede Antwort :)

Code: 
Mar 21 13:03:03 pve02 systemd-logind[1252]: Session 6774 logged out. Waiting for processes to exit.
Mar 21 13:03:03 pve02 systemd-logind[1252]: Removed session 6774.
Mar 21 13:03:03 pve02 sshd[317520]: Accepted publickey for root from 192.168.2.175 port 33222 ssh2: RSA SHA256:uZXau/a+SXqTgXpxjhQ
Mar 21 13:03:03 pve02 sshd[317520]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Mar 21 13:03:03 pve02 systemd-logind[1252]: New session 6775 of user root.
Mar 21 13:03:03 pve02 systemd[1]: Started session-6775.scope - Session 6775 of User root.
Mar 21 13:03:03 pve02 sshd[317520]: pam_env(sshd:session): deprecated reading of user environment enabled
Mar 21 13:03:04 pve02 sshd[317520]: Received disconnect from 192.168.2.175 port 33222:11: disconnected by user
Mar 21 13:03:04 pve02 sshd[317520]: Disconnected from user root 192.168.2.175 port 33222
Mar 21 13:03:04 pve02 sshd[317520]: pam_unix(sshd:session): session closed for user root
Mar 21 13:03:04 pve02 systemd[1]: session-6775.scope: Deactivated successfully.
Mar 21 13:03:04 pve02 systemd-logind[1252]: Session 6775 logged out. Waiting for processes to exit.
Mar 21 13:03:04 pve02 systemd-logind[1252]: Removed session 6775.
Mar 21 13:03:04 pve02 sshd[317534]: Accepted publickey for root from 192.168.2.175 port 33234 ssh2: RSA SHA256:uZXauzI4JJQIsa+SXxjhQ
Mar 21 13:03:04 pve02 sshd[317534]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Mar 21 13:03:04 pve02 systemd-logind[1252]: New session 6776 of user root.
Mar 21 13:03:04 pve02 systemd[1]: Started session-6776.scope - Session 6776 of User root.
Mar 21 13:03:04 pve02 sshd[317534]: pam_env(sshd:session): deprecated reading of user environment enabled
Mar 21 13:03:05 pve02 sshd[317534]: Received disconnect from 192.168.2.175 port 33234:11: disconnected by user
Mar 21 13:03:05 pve02 sshd[317534]: Disconnected from user root 192.168.2.175 port 33234
Mar 21 13:03:05 pve02 sshd[317534]: pam_unix(sshd:session): session closed for user root
Mar 21 13:03:05 pve02 systemd[1]: session-6776.scope: Deactivated successfully.
Mar 21 13:03:05 pve02 systemd-logind[1252]: Session 6776 logged out. Waiting for processes to exit.
Mar 21 13:03:05 pve02 systemd-logind[1252]: Removed session 6776.
Mar 21 13:03:05 pve02 sshd[317566]: Accepted publickey for root from 192.168.2.175 port 43080 ssh2: RSA SHA256:uZXau/I4JJQIsa+SXqTgXpxjhQ
Mar 21 13:03:05 pve02 sshd[317566]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Mar 21 13:03:05 pve02 systemd-logind[1252]: New session 6777 of user root.
Mar 21 13:03:05 pve02 systemd[1]: Started session-6777.scope - Session 6777 of User root.
Mar 21 13:03:05 pve02 sshd[317566]: pam_env(sshd:session): deprecated reading of user environment enabled
Mar 21 13:03:07 pve02 sshd[317566]: Received disconnect from 192.168.2.175 port 43080:11: disconnected by user
Mar 21 13:03:07 pve02 sshd[317566]: Disconnected from user root 192.168.2.175 port 43080
Mar 21 13:03:07 pve02 sshd[317566]: pam_unix(sshd:session): session closed for user root
Mar 21 13:03:07 pve02 systemd[1]: session-6777.scope: Deactivated successfully.
 
lucavornheder said:
Hi,
das ist normal. Innerhalb des clusters tauschen die nodes einiges per ssh aus.
Click to expand...
Danke für deine Antwort. Bin jetzt auch mittlerweile davon ausgegangen daß das normal ist. Ich hätte "damals" nur das Problem das meine Nodes unregelmäßig neu gebootet haben und dachte dann das das etwas damit zutun haben könnte, irgendwo muss man ja anfangen den Fehler zu suchen xd
 
You must log in or register to reply here.
Top Bottom