Konsole funtioniert nicht CT

T

Tigger-86

New Member
Oct 5, 2023
21
0
1
Hallo,
ich bin relativ neu was Proxmox angeht.. habe mittlerweile zwei CT die laufen..
jetzt beim dritten funktioniert leider die Konsole nicht und ich habe eine Fehlermeldung:
Code: 
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1

Wie kann ich das Problem lösen?

irtual Environment 8.0.4

Danke
 
Last edited:
Was passiert, wenn du versuchst, den problematischen Befehl direkt selbst in einer Shell auf dem Proxmox VE Host als root auszuführen?
Code: 
/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1

Das sollte dann hoffentlich eine bessere Fehlermeldung ausgeben.
 
Guten Morgen,
leider nein..

Code: 
root@Proxmox:~# /usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1
 
Hmm, und im journal/syslog ist auch kein Fehler ersichtlich? Also um dem Zeitpunkt, wenn die Konsole geöffnet wurde.

Was passiert, wenn folgender Befehl ausgeführt wird?
lxc-console -n 102
 
komischerweise verbindet er sich jetzt wieder normal..

sobald ich nochmal das problem hab, melde ich mich nochmal hier
Code: 
oot@Proxmox:~# lxc-console -n 102

Connected to tty 2
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
danke schonmal
 
doch wieder nach neustart vom ct
Code: 
Oct 06 14:31:15 Proxmox systemd[1]: Stopping user@0.service - User Manager for UID 0...
Oct 06 14:31:15 Proxmox systemd[202933]: Activating special unit exit.target...
Oct 06 14:31:15 Proxmox systemd[202933]: Stopped target default.target - Main User Target.
Oct 06 14:31:15 Proxmox systemd[202933]: Stopped target basic.target - Basic System.
Oct 06 14:31:15 Proxmox systemd[202933]: Stopped target paths.target - Paths.
Oct 06 14:31:15 Proxmox systemd[202933]: Stopped target sockets.target - Sockets.
Oct 06 14:31:15 Proxmox systemd[202933]: Stopped target timers.target - Timers.
Oct 06 14:31:15 Proxmox systemd[202933]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Oct 06 14:31:15 Proxmox systemd[202933]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 06 14:31:15 Proxmox systemd[202933]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Oct 06 14:31:15 Proxmox systemd[202933]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Oct 06 14:31:15 Proxmox systemd[202933]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Oct 06 14:31:15 Proxmox systemd[202933]: Removed slice app.slice - User Application Slice.
Oct 06 14:31:15 Proxmox systemd[202933]: Reached target shutdown.target - Shutdown.
Oct 06 14:31:15 Proxmox systemd[202933]: Finished systemd-exit.service - Exit the Session.
Oct 06 14:31:15 Proxmox systemd[202933]: Reached target exit.target - Exit the Session.
Oct 06 14:31:15 Proxmox systemd[1]: user@0.service: Deactivated successfully.
Oct 06 14:31:15 Proxmox systemd[1]: Stopped user@0.service - User Manager for UID 0.
Oct 06 14:31:15 Proxmox systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Oct 06 14:31:15 Proxmox systemd[1]: run-user-0.mount: Deactivated successfully.
Oct 06 14:31:15 Proxmox systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Oct 06 14:31:15 Proxmox systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Oct 06 14:31:15 Proxmox systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Oct 06 14:31:52 Proxmox pvedaemon[920]: <root@pam> starting task UPID:Proxmox:00031B17:00602BF7:651FFE38:vzstop:102:root@pam:
Oct 06 14:31:52 Proxmox pvedaemon[203543]: stopping CT 102: UPID:Proxmox:00031B17:00602BF7:651FFE38:vzstop:102:root@pam:
Oct 06 14:31:52 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered disabled state
Oct 06 14:31:52 Proxmox kernel: device veth102i0 left promiscuous mode
Oct 06 14:31:52 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered disabled state
Oct 06 14:31:52 Proxmox audit[203551]: AVC apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-102_</var/lib/lxc>" pid=203551 comm="apparmor_parser"
Oct 06 14:31:52 Proxmox kernel: audit: type=1400 audit(1696595512.504:46): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-102_</var/lib/lxc>" pid=203551 comm="apparmor_parser"
Oct 06 14:31:52 Proxmox pvedaemon[922]: unable to get PID for CT 102 (not running?)
Oct 06 14:31:53 Proxmox kernel: EXT4-fs (dm-8): unmounting filesystem d3d815fe-28ef-47b9-a101-8792938ef8cf.
Oct 06 14:31:53 Proxmox kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Oct 06 14:31:53 Proxmox kernel: vmbr0: port 3(fwpr102p0) entered disabled state
Oct 06 14:31:53 Proxmox kernel: device fwln102i0 left promiscuous mode
Oct 06 14:31:53 Proxmox kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Oct 06 14:31:53 Proxmox kernel: device fwpr102p0 left promiscuous mode
Oct 06 14:31:53 Proxmox kernel: vmbr0: port 3(fwpr102p0) entered disabled state
Oct 06 14:31:53 Proxmox pvedaemon[921]: <root@pam> end task UPID:Proxmox:00031A38:006019C6:651FFE09:vncproxy:102:root@pam: OK
Oct 06 14:31:53 Proxmox pvedaemon[920]: <root@pam> end task UPID:Proxmox:00031B17:00602BF7:651FFE38:vzstop:102:root@pam: OK
Oct 06 14:31:53 Proxmox systemd[1]: pve-container@102.service: Deactivated successfully.
Oct 06 14:32:00 Proxmox pvedaemon[203599]: starting CT 102: UPID:Proxmox:00031B4F:00602F45:651FFE40:vzstart:102:root@pam:
Oct 06 14:32:00 Proxmox pvedaemon[921]: <root@pam> starting task UPID:Proxmox:00031B4F:00602F45:651FFE40:vzstart:102:root@pam:
Oct 06 14:32:00 Proxmox systemd[1]: Started pve-container@102.service - PVE LXC Container: 102.
Oct 06 14:32:01 Proxmox kernel: EXT4-fs (dm-8): mounted filesystem d3d815fe-28ef-47b9-a101-8792938ef8cf with ordered data mode. Quota mode: none.
Oct 06 14:32:01 Proxmox audit[203622]: AVC apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-102_</var/lib/lxc>" pid=203622 comm="apparmor_parser"
Oct 06 14:32:01 Proxmox kernel: audit: type=1400 audit(1696595521.600:47): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-102_</var/lib/lxc>" pid=203622 comm="apparmor_parser"
Oct 06 14:32:02 Proxmox kernel: vmbr0: port 3(fwpr102p0) entered blocking state
Oct 06 14:32:02 Proxmox kernel: vmbr0: port 3(fwpr102p0) entered disabled state
Oct 06 14:32:02 Proxmox kernel: device fwpr102p0 entered promiscuous mode
Oct 06 14:32:02 Proxmox kernel: vmbr0: port 3(fwpr102p0) entered blocking state
Oct 06 14:32:02 Proxmox kernel: vmbr0: port 3(fwpr102p0) entered forwarding state
Oct 06 14:32:02 Proxmox kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Oct 06 14:32:02 Proxmox kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Oct 06 14:32:02 Proxmox kernel: device fwln102i0 entered promiscuous mode
Oct 06 14:32:02 Proxmox kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Oct 06 14:32:02 Proxmox kernel: fwbr102i0: port 1(fwln102i0) entered forwarding state
Oct 06 14:32:02 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered blocking state
Oct 06 14:32:02 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered disabled state
Oct 06 14:32:02 Proxmox kernel: device veth102i0 entered promiscuous mode
Oct 06 14:32:02 Proxmox kernel: eth0: renamed from veth1K2pdg
Oct 06 14:32:02 Proxmox pvedaemon[921]: <root@pam> end task UPID:Proxmox:00031B4F:00602F45:651FFE40:vzstart:102:root@pam: OK
Oct 06 14:32:02 Proxmox pvedaemon[921]: <root@pam> starting task UPID:Proxmox:00031BB2:00602FFD:651FFE42:vncproxy:102:root@pam:
Oct 06 14:32:02 Proxmox pvedaemon[203698]: starting lxc termproxy UPID:Proxmox:00031BB2:00602FFD:651FFE42:vncproxy:102:root@pam:
Oct 06 14:32:02 Proxmox pvedaemon[920]: <root@pam> starting task UPID:Proxmox:00031BC8:0060300D:651FFE42:vncproxy:102:root@pam:
Oct 06 14:32:02 Proxmox pvedaemon[203720]: starting lxc termproxy UPID:Proxmox:00031BC8:0060300D:651FFE42:vncproxy:102:root@pam:
Oct 06 14:32:02 Proxmox pvedaemon[921]: <root@pam> successful auth for user 'root@pam'
Oct 06 14:32:02 Proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 06 14:32:02 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered blocking state
Oct 06 14:32:02 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered forwarding state
Oct 06 14:32:12 Proxmox pvedaemon[203698]: command '/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1
Oct 06 14:32:12 Proxmox pvedaemon[921]: <root@pam> end task UPID:Proxmox:00031BB2:00602FFD:651FFE42:vncproxy:102:root@pam: command '/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1
Oct 06 14:32:19 Proxmox pvedaemon[920]: <root@pam> end task UPID:Proxmox:00031BC8:0060300D:651FFE42:vncproxy:102:root@pam: OK
Oct 06 14:32:20 Proxmox pvedaemon[920]: <root@pam> starting task UPID:Proxmox:00031C90:006036E5:651FFE54:vncproxy:102:root@pam:
Oct 06 14:32:20 Proxmox pvedaemon[203920]: starting lxc termproxy UPID:Proxmox:00031C90:006036E5:651FFE54:vncproxy:102:root@pam:
Oct 06 14:32:20 Proxmox pvedaemon[921]: <root@pam> successful auth for user 'root@pam'
Oct 06 14:32:35 Proxmox pvedaemon[920]: <root@pam> end task UPID:Proxmox:00031C90:006036E5:651FFE54:vncproxy:102:root@pam: OK
Oct 06 14:32:35 Proxmox pvedaemon[204008]: starting termproxy UPID:Proxmox:00031CE8:00603CF2:651FFE63:vncshell::root@pam:
Oct 06 14:32:35 Proxmox pvedaemon[920]: <root@pam> starting task UPID:Proxmox:00031CE8:00603CF2:651FFE63:vncshell::root@pam:
Oct 06 14:32:35 Proxmox pvedaemon[922]: <root@pam> successful auth for user 'root@pam'
Oct 06 14:32:35 Proxmox login[204011]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Oct 06 14:32:35 Proxmox systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Oct 06 14:32:35 Proxmox systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Oct 06 14:32:35 Proxmox systemd-logind[575]: New session 78 of user root.
Oct 06 14:32:35 Proxmox systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Oct 06 14:32:35 Proxmox systemd[1]: Starting user@0.service - User Manager for UID 0...
Oct 06 14:32:35 Proxmox (systemd)[204017]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Oct 06 14:32:35 Proxmox systemd[204017]: Queued start job for default target default.target.
Oct 06 14:32:35 Proxmox systemd[204017]: Created slice app.slice - User Application Slice.
Oct 06 14:32:35 Proxmox systemd[204017]: Reached target paths.target - Paths.
Oct 06 14:32:35 Proxmox systemd[204017]: Reached target timers.target - Timers.
Oct 06 14:32:35 Proxmox systemd[204017]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Oct 06 14:32:35 Proxmox systemd[204017]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 06 14:32:35 Proxmox systemd[204017]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Oct 06 14:32:35 Proxmox systemd[204017]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Oct 06 14:32:35 Proxmox systemd[204017]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Oct 06 14:32:35 Proxmox systemd[204017]: Reached target sockets.target - Sockets.
Oct 06 14:32:35 Proxmox systemd[204017]: Reached target basic.target - Basic System.
Oct 06 14:32:35 Proxmox systemd[204017]: Reached target default.target - Main User Target.
Oct 06 14:32:35 Proxmox systemd[204017]: Startup finished in 132ms.
Oct 06 14:32:35 Proxmox systemd[1]: Started user@0.service - User Manager for UID 0.
Oct 06 14:32:35 Proxmox systemd[1]: Started session-78.scope - Session 78 of User root.
Oct 06 14:32:35 Proxmox login[204033]: ROOT LOGIN  on '/dev/pts/0'
Oct 06 14:32:39 Proxmox systemd-logind[575]: Session 78 logged out. Waiting for processes to exit.
Oct 06 14:32:39 Proxmox systemd[1]: session-78.scope: Deactivated successfully.
Oct 06 14:32:39 Proxmox systemd-logind[575]: Removed session 78.
Oct 06 14:32:39 Proxmox pvedaemon[920]: <root@pam> end task UPID:Proxmox:00031CE8:00603CF2:651FFE63:vncshell::root@pam: OK
Oct 06 14:32:49 Proxmox systemd[1]: Stopping user@0.service - User Manager for UID 0...
Oct 06 14:32:49 Proxmox systemd[204017]: Activating special unit exit.target...
Oct 06 14:32:49 Proxmox systemd[204017]: Stopped target default.target - Main User Target.
Oct 06 14:32:49 Proxmox systemd[204017]: Stopped target basic.target - Basic System.
Oct 06 14:32:49 Proxmox systemd[204017]: Stopped target paths.target - Paths.
Oct 06 14:32:49 Proxmox systemd[204017]: Stopped target sockets.target - Sockets.
Oct 06 14:32:49 Proxmox systemd[204017]: Stopped target timers.target - Timers.
Oct 06 14:32:49 Proxmox systemd[204017]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Oct 06 14:32:49 Proxmox systemd[204017]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 06 14:32:49 Proxmox systemd[204017]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Oct 06 14:32:49 Proxmox systemd[204017]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Oct 06 14:32:49 Proxmox systemd[204017]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Oct 06 14:32:49 Proxmox systemd[204017]: Removed slice app.slice - User Application Slice.
Oct 06 14:32:49 Proxmox systemd[204017]: Reached target shutdown.target - Shutdown.
Oct 06 14:32:49 Proxmox systemd[204017]: Finished systemd-exit.service - Exit the Session.
Oct 06 14:32:49 Proxmox systemd[204017]: Reached target exit.target - Exit the Session.
Oct 06 14:32:49 Proxmox systemd[1]: user@0.service: Deactivated successfully.
Oct 06 14:32:49 Proxmox systemd[1]: Stopped user@0.service - User Manager for UID 0.
Oct 06 14:32:49 Proxmox systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Oct 06 14:32:49 Proxmox systemd[1]: run-user-0.mount: Deactivated successfully.
Oct 06 14:32:49 Proxmox systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Oct 06 14:32:49 Proxmox systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Oct 06 14:32:49 Proxmox systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Oct 06 14:33:16 Proxmox pvedaemon[921]: <root@pam> starting task UPID:Proxmox:00031DBD:00604CE6:651FFE8C:vncproxy:102:root@pam:
Oct 06 14:33:16 Proxmox pvedaemon[204221]: starting lxc termproxy UPID:Proxmox:00031DBD:00604CE6:651FFE8C:vncproxy:102:root@pam:
Oct 06 14:33:16 Proxmox pvedaemon[922]: <root@pam> successful auth for user 'root@pam'
Oct 06 14:33:38 Proxmox pvedaemon[920]: <root@pam> successful auth for user 'root@pam'
Oct 06 14:33:39 Proxmox pvedaemon[921]: <root@pam> end task UPID:Proxmox:00031DBD:00604CE6:651FFE8C:vncproxy:102:root@pam:

und hier aus dem task view

Code: 
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1

nach einer zeit.. funktioniert es.aber es scheint ja nicht normal zu sein.
 
Hmm, Container ist um 14:32:02 gestartet und der erste Versuch die Konsole zu öffnen passiert 10s später um 14:32:12, potentiell ist das System innerhalb des Containers zu dem Zeitpunkt einfach noch nicht bereit, und daher klappt es noch nicht eine Konsole anzuhängen.

Was läuft in dem Container? Gibt's da logs wo man schauen kann ab wann die CT distro fertig mit start-up ist?
 
ja, ich bin nur verwundert weil der andere container (motioneye) läuft schneller an. in dem betroffenen container ist noch nichts am laufen.
eigentlich soll da mal octopi laufen.. aber es funktioniert nicht wirklich
 
Tigger-86 said:
ja, ich bin nur verwundert weil der andere container (motioneye) läuft schneller an. in dem betroffenen container ist noch nichts am laufen.
eigentlich soll da mal octopi laufen.. aber es funktioniert nicht wirklich
Click to expand...

hab den ct nochmal gelöscht und nochmal einen erstellt..
gleiche problem.. die konsole startet zwar nach einer zeit aber im task view gibt es wieder die fehlermeldung:
Code: 
Oct 06 19:47:58 Proxmox kernel: device fwln102i0 entered promiscuous mode
Oct 06 19:47:58 Proxmox kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Oct 06 19:47:58 Proxmox kernel: fwbr102i0: port 1(fwln102i0) entered forwarding state
Oct 06 19:47:58 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered blocking state
Oct 06 19:47:58 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered disabled state
Oct 06 19:47:58 Proxmox kernel: device veth102i0 entered promiscuous mode
Oct 06 19:47:58 Proxmox kernel: eth0: renamed from vethazFfs0
Oct 06 19:47:59 Proxmox pvedaemon[206040]: <root@pam> end task UPID:Proxmox:00040765:007D1C41:6520484D:vzstart:102:root@pam: OK
Oct 06 19:47:59 Proxmox pvedaemon[206040]: <root@pam> starting task UPID:Proxmox:000407D8:007D1D02:6520484F:vncproxy:102:root@pam:
Oct 06 19:47:59 Proxmox pvedaemon[264152]: starting lxc termproxy UPID:Proxmox:000407D8:007D1D02:6520484F:vncproxy:102:root@pam:
Oct 06 19:47:59 Proxmox pveproxy[263518]: proxy detected vanished client connection
Oct 06 19:47:59 Proxmox pvedaemon[212432]: <root@pam> starting task UPID:Proxmox:000407DD:007D1D06:6520484F:vncproxy:102:root@pam:
Oct 06 19:47:59 Proxmox pvedaemon[264157]: starting lxc termproxy UPID:Proxmox:000407DD:007D1D06:6520484F:vncproxy:102:root@pam:
Oct 06 19:47:59 Proxmox pvedaemon[206040]: <root@pam> successful auth for user 'root@pam'
Oct 06 19:48:00 Proxmox audit[264212]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="nvidia_modprobe" pid=264212 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264212]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="nvidia_modprobe//kmod" pid=264212 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.092:50): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="nvidia_modprobe" pid=264212 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.092:51): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="nvidia_modprobe//kmod" pid=264212 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264219]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/bin/man" pid=264219 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264219]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="man_filter" pid=264219 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.296:52): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/bin/man" pid=264219 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.296:53): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="man_filter" pid=264219 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264219]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="man_groff" pid=264219 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.308:54): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="man_groff" pid=264219 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 06 19:48:00 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered blocking state
Oct 06 19:48:00 Proxmox kernel: fwbr102i0: port 2(veth102i0) entered forwarding state
Oct 06 19:48:00 Proxmox audit[264223]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/sbin/tcpdump" pid=264223 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.548:55): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/sbin/tcpdump" pid=264223 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264227]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="lsb_release" pid=264227 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.648:56): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="lsb_release" pid=264227 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264228]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=264228 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264228]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=264228 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264228]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=264228 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox audit[264228]: AVC apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/{,usr/}sbin/dhclient" pid=264228 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.976:57): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=264228 comm="apparmor_parser"
Oct 06 19:48:00 Proxmox kernel: audit: type=1400 audit(1696614480.976:58): apparmor="STATUS" operation="profile_load" label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=264228 comm="apparmor_parser"
Oct 06 19:48:09 Proxmox pvedaemon[264152]: command '/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1
Oct 06 19:48:09 Proxmox pvedaemon[206040]: <root@pam> end task UPID:Proxmox:000407D8:007D1D02:6520484F:vncproxy:102:root@pam: command '/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1
Oct 06 19:48:48 Proxmox pvedaemon[212432]: <root@pam> end task UPID:Proxmox:000407DD:007D1D06:6520484F:vncproxy:102:root@pam: OK


failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/102 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole102 -r winch -z lxc-console -n 102 -e -1' failed: exit code 1
 
Ja, wie gesagt, du musst innerhalb des Containers schauen was da so lang brauch bis der fertig gebooten hat.

Für Proxmox VE ist der CT gestartet, sobald das Initsystem des Containers (etwa systemd bei vielen modernen Distros) erfolgreich gestartet wurde. Das System kann dann aber selber natürlich noch viel länger benötigen bis alle Services, inklusive des TTY-Services, die die Konsole des Containers bereitstellen, gestartet sind.

Also bitte in den Container Einloggen (sobald die Konsole klappt) und dort die Logs anschauen, oder Tools wie systemd-analyze blame verwenden.

Das einzige wie das von Proxmox VE Seite beeinflusst werden könnte sind Device oder mount pass-throughs in der Container config die, wieso auch immer, den Start verzögern – evtl. noch die Ausgabe von pct config 102 posten.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom