Problem mit Advanced SSH & Terminal

Allgemein
1

Hallo zusammen
ich bin ziemlich neu mit HA und habe folgendes Problem:
HA läuft mittels Virtual Machine auf einem Synology NAS

Das SSH&Terminal Addon lässt sich nicht mehr starten… Log sieht wie folgt aus:

s6-rc: info: service ttyd successfully stopped
s6-rc: info: service init-user: stopping
s6-rc: info: service init-user successfully stopped
s6-rc: info: service init-ssh: stopping
s6-rc: info: service init-ssh successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------

 Add-on: Advanced SSH & Web Terminal
 A supercharged SSH & Web Terminal access to your Home Assistant instance
-----------------------------------------------------------
 Add-on version: 17.2.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.3  (amd64 / qemux86-64)
 Home Assistant Core: 2024.5.3
 Home Assistant Supervisor: 2024.05.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-ssh: starting
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-docker: starting
s6-rc: info: service init-docker successfully started
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service init-mysql successfully started
[19:05:42] WARNING: 
[19:05:43] WARNING: Logging in with a SSH password is security wise, a bad idea!
[19:05:43] WARNING: Please, consider using a public/private key pair.
[19:05:43] WARNING: What is this? https://kb.iu.edu/d/aews
[19:05:43] WARNING: 
[19:05:43] NOTICE: RSA host key missing, generating one...
Generating public/private rsa key pair.
Your identification has been saved in /data/ssh_host_rsa_key
Your public key has been saved in /data/ssh_host_rsa_key.pub
The key fingerprint is:
SHA256:eBlvFIHB1WlIvPFvUSMFiPt+suEqpO9rXx3rCcwguNs root@a0d7b954-ssh
The key's randomart image is:
+---[RSA 3072]----+
|       ..**+.oo. |
|        o.+o+. ..|
|        . o=  ...|
|      .. *. . .  |
|     ...S.+  o . |
|      .o..+.. =  |
|     .o   .* +   |
|     .oo  oo+..  |
|     .+E+o.o+o   |
+----[SHA256]-----+
[19:05:43] NOTICE: ED25519 host key missing, generating one...
Generating public/private ed25519 key pair.
Your identification has been saved in /data/ssh_host_ed25519_key
Your public key has been saved in /data/ssh_host_ed25519_key.pub
The key fingerprint is:
SHA256:8npibaMVs6xW0Ur2pzm28Xigse+fmRklKWVtjCIsFxM root@a0d7b954-ssh
The key's randomart image is:
+--[ED25519 256]--+
|        E.       |
|       . o   +   |
|      . +.. + +  |
|       o+..+ o   |
|      .oS+. o .  |
|       +++o..o   |
|       o=+.=.    |
|      ++B =+.*   |
|     o+= ===B    |
+----[SHA256]-----+
s6-rc: info: service init-ssh successfully started
s6-rc: info: service init-user: starting
[19:05:44] NOTICE: Session sharing has been disabled!
s6-rc: info: service init-user successfully started
s6-rc: info: service ttyd: starting
s6-rc: info: service sshd: starting
s6-rc: info: service ttyd successfully started
s6-rc: info: service sshd successfully started
s6-rc: info: service legacy-services: starting
[19:05:44] INFO: Starting the ttyd daemon...
[19:05:44] INFO: Starting the SSH daemon...
s6-rc: info: service legacy-services successfully started
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.

:crayon:by HarryP: Codezeilen formatiert (bitte in </> einbinden)

2

Was heisst es lässt sich nicht starten?!

Dein Log endet mit

s6-rc: info: service legacy-services successfully started
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.

Also läuft doch alles.

Das einzige was angemerkt wird ist die Warnung, dass Du einen ssh key verwende sollst.

Gruß
Osorkon

3

Ja, dass ist ja das komische daran… das habe ich dem log auch entnommen.
Jedoch kann ich das Terminal nicht aufrufen resp. wenn das Addon gestartet wurde steht kurze Zeit darauf wieder “starten”.
(siehe fotos)

Bildschirmfoto 2024-05-13 um 19.53.55
Bildschirmfoto 2024-05-13 um 19.53.551784×1160 192 KB

Bildschirmfoto 2024-05-13 um 19.54.06
Bildschirmfoto 2024-05-13 um 19.54.061784×1160 68.3 KB

4

Moin,

ein herzlich willkommen im Forum.

Also es lief schon einmal ohne Probleme?
Wenn ja, was hast Du als letztes gemacht, bevor es nicht mehr lief?

Was mich imitiert, ist das, das Log von der Ersteinrichtung?
Oder kommt jedes Mal der Part mit dem

[19:05:43] NOTICE: RSA host key missing, generating one...
Generating public/private rsa key pair.
Your identification has been saved in /data/ssh_host_rsa_key
Your public key has been saved in /data/ssh_host_rsa_key.pub
The key fingerprint is:
SHA256:eBlvFIHB1WlIvPFvUSMFiPt+suEqpO9rXx3rCcwguNs root@a0d7b954-ssh
The key's randomart image is:
+---[RSA 3072]----+
|       ..**+.oo. |
|        o.+o+. ..|
|        . o=  ...|
|      .. *. . .  |
|     ...S.+  o . |
|      .o..+.. =  |
|     .o   .* +   |
|     .oo  oo+..  |
|     .+E+o.o+o   |
+----[SHA256]-----+
[19:05:43] NOTICE: ED25519 host key missing, generating one...
Generating public/private ed25519 key pair.
Your identification has been saved in /data/ssh_host_ed25519_key
Your public key has been saved in /data/ssh_host_ed25519_key.pub
The key fingerprint is:
SHA256:8npibaMVs6xW0Ur2pzm28Xigse+fmRklKWVtjCIsFxM root@a0d7b954-ssh
The key's randomart image is:
+--[ED25519 256]--+
|        E.       |
|       . o   +   |
|      . +.. + +  |
|       o+..+ o   |
|      .oS+. o .  |
|       +++o..o   |
|       o=+.=.    |
|      ++B =+.*   |
|     o+= ===B    |
+----[SHA256]-----+

Keine Ahnung wie das mit Synology und VM geht, Du redest sicherlich vom VMM. gibt es denn auch von VMM logs, stimmen da vielleicht die Rechte nicht?
Du kannst ja mal das Add-on deinstallieren und die VM neu starten, dann noch einmal neu installieren.

VG
Bernd

5

Hallo Bernd
Danke dir für deine Antwort. Von VMM habe ich leider keinen log gefunden. Jedoch hat es mit deiner Idee (Addon deinstal / VMM neustarten) geklappt und SSH funktioniert wieder wie gewohnt. =)