migration aktive vm Fehler (Unable to write to socket: Broken pipe) - migration stopped vm OK

RoFrie

Member
May 10, 2020
6
0
6
67
Die Migration einiger VMs schlägt fehl, solange diese aktiv sind. Die gestoppten VMs lassen sich problemlos migrieren.

Hier die Fehlermeldung einer Migration:
Code:
2023-06-20 10:21:20 starting migration of VM 108 to node 'pve72' (192.168.178.128)
2023-06-20 10:21:21 starting VM 108 on remote node 'pve72'
2023-06-20 10:21:23 start remote tunnel
2023-06-20 10:21:24 ssh tunnel ver 1
2023-06-20 10:21:24 starting online/live migration on unix:/run/qemu-server/108.migrate
2023-06-20 10:21:24 set migration capabilities
2023-06-20 10:21:24 migration downtime limit: 100 ms
2023-06-20 10:21:24 migration cachesize: 1.0 GiB
2023-06-20 10:21:24 set migration parameters
2023-06-20 10:21:24 start migrate command to unix:/run/qemu-server/108.migrate
channel 2: open failed: connect failed: open failed

2023-06-20 10:21:25 migration status error: failed - Unable to write to socket: Broken pipe
2023-06-20 10:21:25 ERROR: online migrate failure - aborting
2023-06-20 10:21:25 aborting phase 2 - cleanup resources
2023-06-20 10:21:25 migrate_cancel
2023-06-20 10:21:28 ERROR: migration finished with problems (duration 00:00:08)
TASK ERROR: migration problems

Code:
sudo pvecm status
Cluster information
-------------------
Name:             proxmox-cluster
Config Version:   12
Transport:        knet
Secure auth:      on


Quorum information
------------------
Date:             Tue Jun 20 10:25:19 2023
Quorum provider:  corosync_votequorum
Nodes:            3
Node ID:          0x00000005
Ring ID:          2.28c1
Quorate:          Yes


Votequorum information
----------------------
Expected votes:   3
Highest expected: 3
Total votes:      3
Quorum:           2
Flags:            Quorate


Membership information
----------------------
    Nodeid      Votes Name
0x00000002          1 192.168.178.123
0x00000003          1 192.168.178.128
0x00000005          1 192.168.178.132 (local)

Code:
sudo pvesm status
Name                       Type     Status           Total            Used       Available        %
NFSTemp                     nfs     active      5621463168      2537725312      3083737856   45.14%
NFS_DS                      nfs     active     28096132608     14603108096     13493024512   51.98%
NFS_OurCloudStation         nfs     active     28096132608     14603108096     13493024512   51.98%
NFS_PBS                     nfs     active     28096132608     14603108096     13493024512   51.98%
NFS_PBSTemp                 nfs     active      5621463168      2537725312      3083737856   45.14%
NFS_Proxmox                 nfs     active     28096132608     14603108096     13493024512   51.98%
NFS_TUnterlagen             nfs     active      5621463168      2537725312      3083737856   45.14%
NFS_Unterlagen              nfs     active     28096132608     14603108096     13493024512   51.98%
NFS_bkp2                    nfs     active     28096132608     14603108096     13493024512   51.98%
PBS                         pbs     active     28096132608     14603108096     13493024512   51.98%
ceph                        rbd     active      1776175433       246355401      1529820032   13.87%
local                       dir     active        98497780         7177660        86270572    7.29%
local-lvm               lvmthin     active       366276608               0       366276608    0.00%
urbackup                    nfs     active     28096132608     14603108096     13493024512   51.98%
 
irgendwas im "start" log der VM auf der target node seite sichtbar?
 
Was ist mit start log gemeint? Die Datei /var/log/pve-cluster.log existiert auf beiden Servern nicht.
 
bei einer live migration wird die VM am ziel node gestartet, dass erzeugt einen eintrag in der task history.

zusaetzlich waere das journal von beiden nodes waehrend der fehlgeschlagenen migration hilfreich (journalctl --since ... --until ...)
 
Code:
date; sudo qm migrate 300 pve72 --online; date
Tue 20 Jun 2023 06:24:30 PM CEST
2023-06-20 18:24:31 starting migration of VM 300 to node 'pve72' (192.168.178.128)
2023-06-20 18:24:31 starting VM 300 on remote node 'pve72'
2023-06-20 18:24:34 start remote tunnel
2023-06-20 18:24:35 ssh tunnel ver 1
2023-06-20 18:24:35 starting online/live migration on unix:/run/qemu-server/300.migrate
2023-06-20 18:24:35 set migration capabilities
2023-06-20 18:24:35 migration downtime limit: 100 ms
2023-06-20 18:24:35 migration cachesize: 4.0 GiB
2023-06-20 18:24:35 set migration parameters
2023-06-20 18:24:35 spice client_migrate_info
2023-06-20 18:24:35 start migrate command to unix:/run/qemu-server/300.migrate
channel 2: open failed: connect failed: open failed
2023-06-20 18:24:36 migration status error: failed - Unable to write to socket: Broken pipe
2023-06-20 18:24:36 ERROR: online migrate failure - aborting
2023-06-20 18:24:36 aborting phase 2 - cleanup resources
2023-06-20 18:24:36 migrate_cancel
2023-06-20 18:24:38 ERROR: migration finished with problems (duration 00:00:07)
migration problems
Tue 20 Jun 2023 06:24:38 PM CEST


Code:
 sudo journalctl --since "2023-06-20 18:24:30" --until  "2023-06-20 18:25:00"
-- Journal begins at Mon 2023-06-05 13:17:48 CEST, ends at Tue 2023-06-20 18:30:26 CEST. --
Jun 20 18:24:30 pve74 sudo[1370823]:     rolf : TTY=pts/0 ; PWD=/home/rolf ; USER=root ; COMMAND=/usr/sbin/qm migrate 300 pve72 --online
Jun 20 18:24:30 pve74 sudo[1370823]: pam_unix(sudo:session): session opened for user root(uid=0) by rolf(uid=1000)
Jun 20 18:24:31 pve74 qm[1370824]: <root@pam> starting task UPID:pve74:XXX:qmigrate:300:root@pam:
Jun 20 18:24:32 pve74 pmxcfs[1150]: [status] notice: received log
Jun 20 18:24:34 pve74 pmxcfs[1150]: [status] notice: received log
Jun 20 18:24:34 pve74 kernel: overlayfs: fs on '/var/lib/docker/overlay2/l/XXX does not support file handles, falling back to xino=off.
Jun 20 18:24:34 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered blocking state
Jun 20 18:24:34 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered disabled state
Jun 20 18:24:34 pve74 kernel: device veth5a8968e entered promiscuous mode
Jun 20 18:24:34 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered blocking state
Jun 20 18:24:34 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered forwarding state
Jun 20 18:24:34 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered disabled state
Jun 20 18:24:34 pve74 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2cd9599: link becomes ready
Jun 20 18:24:34 pve74 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5a8968e: link becomes ready
Jun 20 18:24:34 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered blocking state
Jun 20 18:24:34 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered forwarding state
Jun 20 18:24:35 pve74 QEMU[3729813]: kvm: Unable to write to socket: Broken pipe
Jun 20 18:24:35 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered disabled state
Jun 20 18:24:35 pve74 kernel: eth0: renamed from veth2cd9599
Jun 20 18:24:35 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered blocking state
Jun 20 18:24:35 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered forwarding state
Jun 20 18:24:35 pve74 kernel: veth2cd9599: renamed from eth0
Jun 20 18:24:35 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered disabled state
Jun 20 18:24:35 pve74 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2cd9599: link becomes ready
Jun 20 18:24:35 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered blocking state
Jun 20 18:24:35 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered forwarding state
Jun 20 18:24:36 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered disabled state
Jun 20 18:24:36 pve74 kernel: device veth5a8968e left promiscuous mode
Jun 20 18:24:36 pve74 kernel: br-77474fcda2ac: port 3(veth5a8968e) entered disabled state
Jun 20 18:24:37 pve74 pmxcfs[1150]: [status] notice: received log
Jun 20 18:24:37 pve74 pmxcfs[1150]: [status] notice: received log
Jun 20 18:24:38 pve74 qm[1370826]: migration problems
Jun 20 18:24:38 pve74 qm[1370824]: <root@pam> end task UPID:pve74:XXXX:qmigrate:300:root@pam: migration problems
Jun 20 18:24:38 pve74 sudo[1370823]: pam_unix(sudo:session): session closed for user root
 
Code:
Jun 20 18:24:31 pve72 pmxcfs[2067]: [status] notice: received log
Jun 20 18:24:31 pve72 sshd[2239060]: rexec line 46: Deprecated option UsePrivilegeSeparation
Jun 20 18:24:31 pve72 sshd[2239060]: Accepted publickey for root from 192.168.178.132 port 34850 ssh2: RSA SHA256:XXXX
Jun 20 18:24:31 pve72 sshd[2239060]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jun 20 18:24:31 pve72 systemd[1]: Created slice User Slice of UID 0.
Jun 20 18:24:31 pve72 systemd[1]: Starting User Runtime Directory /run/user/0...
Jun 20 18:24:31 pve72 systemd-logind[869]: New session 25149 of user root.
Jun 20 18:24:31 pve72 systemd[1]: Finished User Runtime Directory /run/user/0.
Jun 20 18:24:31 pve72 systemd[1]: Starting User Manager for UID 0...
Jun 20 18:24:31 pve72 systemd[2239063]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Jun 20 18:24:31 pve72 systemd-xdg-autostart-generator[2239076]: Exec binary '/usr/libexec/at-spi-bus-launcher' does not exist: No such file or directory
Jun 20 18:24:31 pve72 systemd-xdg-autostart-generator[2239076]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, error parsing Exec= line: No su>
Jun 20 18:24:31 pve72 systemd[2239063]: Queued start job for default target Main User Target.
Jun 20 18:24:31 pve72 systemd[2239063]: Created slice User Application Slice.
Jun 20 18:24:31 pve72 systemd[2239063]: Reached target Paths.
Jun 20 18:24:31 pve72 systemd[2239063]: Reached target Timers.
Jun 20 18:24:31 pve72 systemd[2239063]: Starting D-Bus User Message Bus Socket.
Jun 20 18:24:31 pve72 systemd[2239063]: Listening on GnuPG network certificate management daemon.
Jun 20 18:24:31 pve72 systemd[2239063]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jun 20 18:24:31 pve72 systemd[2239063]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jun 20 18:24:31 pve72 systemd[2239063]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jun 20 18:24:31 pve72 systemd[2239063]: Listening on GnuPG cryptographic agent and passphrase cache.
Jun 20 18:24:31 pve72 systemd[2239063]: Listening on debconf communication socket.
Jun 20 18:24:31 pve72 systemd[2239063]: Listening on Podman API Socket.
Jun 20 18:24:31 pve72 systemd[2239063]: Listening on D-Bus User Message Bus Socket.
Jun 20 18:24:31 pve72 systemd[2239063]: Reached target Sockets.
Jun 20 18:24:31 pve72 systemd[2239063]: Reached target Basic System.
Jun 20 18:24:31 pve72 systemd[2239063]: Reached target Main User Target.
Jun 20 18:24:31 pve72 systemd[2239063]: Startup finished in 126ms.
Jun 20 18:24:31 pve72 systemd[1]: Started User Manager for UID 0.
Jun 20 18:24:31 pve72 systemd[1]: Started Session 25149 of user root.
Jun 20 18:24:31 pve72 sshd[2239060]: Received disconnect from 192.168.178.132 port 34850:11: disconnected by user
Jun 20 18:24:31 pve72 sshd[2239060]: Disconnected from user root 192.168.178.132 port 34850
Jun 20 18:24:31 pve72 sshd[2239060]: pam_unix(sshd:session): session closed for user root
Jun 20 18:24:31 pve72 systemd[1]: session-25149.scope: Succeeded.
Jun 20 18:24:31 pve72 systemd-logind[869]: Session 25149 logged out. Waiting for processes to exit.
Jun 20 18:24:31 pve72 systemd-logind[869]: Removed session 25149.
Jun 20 18:24:31 pve72 sshd[2239084]: rexec line 46: Deprecated option UsePrivilegeSeparation
Jun 20 18:24:31 pve72 sshd[2239084]: Accepted publickey for root from 192.168.178.132 port 34866 ssh2: RSA SHA256:XXX
Jun 20 18:24:31 pve72 sshd[2239084]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jun 20 18:24:31 pve72 systemd-logind[869]: New session 25151 of user root.
Jun 20 18:24:31 pve72 systemd[1]: Started Session 25151 of user root.
Jun 20 18:24:32 pve72 qm[2239091]: <root@pam> starting task UPID:pve72:XXXX:qmstart:300:root@pam:
Jun 20 18:24:32 pve72 qm[2239174]: start VM 300: UPID:pve72:XXX:qmstart:300:root@pam:
Jun 20 18:24:33 pve72 systemd[1]: Started 300.scope.
Jun 20 18:24:33 pve72 systemd-udevd[2239214]: Using default interface naming scheme 'v247'.
Jun 20 18:24:33 pve72 systemd-udevd[2239214]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 20 18:24:33 pve72 kernel: device tap300i0 entered promiscuous mode
Jun 20 18:24:33 pve72 systemd-udevd[2239214]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 20 18:24:33 pve72 systemd-udevd[2239214]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 20 18:24:33 pve72 systemd-udevd[2239213]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 20 18:24:33 pve72 systemd-udevd[2239213]: Using default interface naming scheme 'v247'.
Jun 20 18:24:33 pve72 kernel: vmbr0: port 3(fwpr300p0) entered blocking state
Jun 20 18:24:33 pve72 kernel: vmbr0: port 3(fwpr300p0) entered disabled state
Jun 20 18:24:33 pve72 kernel: device fwpr300p0 entered promiscuous mode
Jun 20 18:24:33 pve72 kernel: vmbr0: port 3(fwpr300p0) entered blocking state
Jun 20 18:24:33 pve72 kernel: vmbr0: port 3(fwpr300p0) entered forwarding state
Jun 20 18:24:33 pve72 kernel: fwbr300i0: port 1(fwln300i0) entered blocking state
Jun 20 18:24:33 pve72 kernel: fwbr300i0: port 1(fwln300i0) entered disabled state
Jun 20 18:24:33 pve72 kernel: device fwln300i0 entered promiscuous mode
Jun 20 18:24:33 pve72 kernel: fwbr300i0: port 1(fwln300i0) entered blocking state
Jun 20 18:24:33 pve72 kernel: fwbr300i0: port 1(fwln300i0) entered forwarding state
Jun 20 18:24:33 pve72 kernel: fwbr300i0: port 2(tap300i0) entered blocking state
Jun 20 18:24:33 pve72 kernel: fwbr300i0: port 2(tap300i0) entered disabled state
Jun 20 18:24:33 pve72 kernel: fwbr300i0: port 2(tap300i0) entered blocking state
Jun 20 18:24:33 pve72 kernel: fwbr300i0: port 2(tap300i0) entered forwarding state
Jun 20 18:24:34 pve72 qm[2239091]: <root@pam> end task UPID:pve72:XXX:qmstart:300:root@pam: OK
Jun 20 18:24:34 pve72 sshd[2239084]: Received disconnect from 192.168.178.132 port 34866:11: disconnected by user
Jun 20 18:24:34 pve72 sshd[2239084]: Disconnected from user root 192.168.178.132 port 34866
Jun 20 18:24:34 pve72 sshd[2239084]: pam_unix(sshd:session): session closed for user root
Jun 20 18:24:34 pve72 systemd[1]: session-25151.scope: Succeeded.
Jun 20 18:24:34 pve72 systemd[1]: session-25151.scope: Consumed 1.197s CPU time.
Jun 20 18:24:34 pve72 systemd-logind[869]: Session 25151 logged out. Waiting for processes to exit.
Jun 20 18:24:34 pve72 systemd-logind[869]: Removed session 25151.
Jun 20 18:24:34 pve72 sshd[2239289]: rexec line 46: Deprecated option UsePrivilegeSeparation
Jun 20 18:24:34 pve72 sshd[2239289]: Accepted publickey for root from 192.168.178.132 port 38952 ssh2: RSA SHA256:XXX
Jun 20 18:24:34 pve72 sshd[2239289]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jun 20 18:24:34 pve72 systemd-logind[869]: New session 25152 of user root.
Jun 20 18:24:34 pve72 systemd[1]: Started Session 25152 of user root.
Jun 20 18:24:35 pve72 sshd[2239289]: Received request to connect to path /run/qemu-server/300.migrate, but the request was denied.
Jun 20 18:24:36 pve72 sshd[2239298]: rexec line 46: Deprecated option UsePrivilegeSeparation
Jun 20 18:24:36 pve72 sshd[2239298]: Accepted publickey for root from 192.168.178.132 port 38954 ssh2: RSA SHA256:XXXX
Jun 20 18:24:36 pve72 sshd[2239298]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jun 20 18:24:36 pve72 systemd-logind[869]: New session 25153 of user root.
Jun 20 18:24:36 pve72 systemd[1]: Started Session 25153 of user root.
Jun 20 18:24:37 pve72 qm[2239305]: <root@pam> starting task UPID:pve72:XXXX:qmstop:300:root@pam:
Jun 20 18:24:37 pve72 qm[2239323]: stop VM 300: UPID:pve72:00222B5B:XXXX:qmstop:300:root@pam:
Jun 20 18:24:37 pve72 QEMU[2239191]: kvm: terminating on signal 15 from pid 2239323 (task UPID:pve72:XXXX:qmstop:300:root@pam:)
Jun 20 18:24:37 pve72 qm[2239305]: <root@pam> end task UPID:pve72:XXXX:qmstop:300:root@pam: OK
Jun 20 18:24:37 pve72 sshd[2239298]: Received disconnect from 192.168.178.132 port 38954:11: disconnected by user
Jun 20 18:24:37 pve72 sshd[2239298]: Disconnected from user root 192.168.178.132 port 38954
Jun 20 18:24:37 pve72 sshd[2239298]: pam_unix(sshd:session): session closed for user root
Jun 20 18:24:37 pve72 systemd[1]: session-25153.scope: Succeeded.
Jun 20 18:24:37 pve72 systemd[1]: session-25153.scope: Consumed 1.214s CPU time.
Jun 20 18:24:37 pve72 systemd-logind[869]: Session 25153 logged out. Waiting for processes to exit.
Jun 20 18:24:37 pve72 systemd-logind[869]: Removed session 25153.
Jun 20 18:24:37 pve72 sshd[2239289]: Received disconnect from 192.168.178.132 port 38952:11: disconnected by user
Jun 20 18:24:37 pve72 sshd[2239289]: Disconnected from user root 192.168.178.132 port 38952
Jun 20 18:24:37 pve72 sshd[2239289]: pam_unix(sshd:session): session closed for user root
Jun 20 18:24:37 pve72 systemd[1]: session-25152.scope: Succeeded.
Jun 20 18:24:37 pve72 systemd-logind[869]: Session 25152 logged out. Waiting for processes to exit.
Jun 20 18:24:37 pve72 systemd-logind[869]: Removed session 25152.
Jun 20 18:24:37 pve72 kernel: fwbr300i0: port 2(tap300i0) entered disabled state
Jun 20 18:24:37 pve72 kernel: fwbr300i0: port 1(fwln300i0) entered disabled state
Jun 20 18:24:37 pve72 kernel: vmbr0: port 3(fwpr300p0) entered disabled state
Jun 20 18:24:37 pve72 kernel: device fwln300i0 left promiscuous mode
Jun 20 18:24:37 pve72 kernel: fwbr300i0: port 1(fwln300i0) entered disabled state
Jun 20 18:24:37 pve72 bgpd[931]: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF fwln300i0 in VRF 0
Jun 20 18:24:37 pve72 kernel: device fwpr300p0 left promiscuous mode
Jun 20 18:24:37 pve72 kernel: vmbr0: port 3(fwpr300p0) entered disabled state
Jun 20 18:24:37 pve72 bgpd[931]: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF fwpr300p0 in VRF 0
Jun 20 18:24:38 pve72 bgpd[931]: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF fwbr300i0 in VRF 0
Jun 20 18:24:38 pve72 bgpd[931]: [VCGF0-X62M1][EC 100663301] INTERFACE_STATE: Cannot find IF tap300i0 in VRF 0
Jun 20 18:24:38 pve72 qmeventd[864]: read: Connection reset by peer
Jun 20 18:24:38 pve72 systemd[1]: 300.scope: Succeeded.
Jun 20 18:24:38 pve72 systemd[1]: 300.scope: Consumed 1.170s CPU time.
Jun 20 18:24:38 pve72 sshd[2239336]: rexec line 46: Deprecated option UsePrivilegeSeparation
Jun 20 18:24:38 pve72 sshd[2239336]: Accepted publickey for root from 192.168.178.132 port 38962 ssh2: RSA SHA256:XXX
Jun 20 18:24:38 pve72 sshd[2239336]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jun 20 18:24:38 pve72 systemd-logind[869]: New session 25154 of user root.
Jun 20 18:24:38 pve72 systemd[1]: Started Session 25154 of user root.
Jun 20 18:24:38 pve72 sshd[2239336]: Received disconnect from 192.168.178.132 port 38962:11: disconnected by user
Jun 20 18:24:38 pve72 sshd[2239336]: Disconnected from user root 192.168.178.132 port 38962
Jun 20 18:24:38 pve72 sshd[2239336]: pam_unix(sshd:session): session closed for user root
Jun 20 18:24:38 pve72 systemd[1]: session-25154.scope: Succeeded.
Jun 20 18:24:38 pve72 systemd-logind[869]: Session 25154 logged out. Waiting for processes to exit.
Jun 20 18:24:38 pve72 systemd-logind[869]: Removed session 25154.
Jun 20 18:24:38 pve72 pmxcfs[2067]: [status] notice: received log
Jun 20 18:24:48 pve72 systemd[1]: Stopping User Manager for UID 0...
Jun 20 18:24:48 pve72 systemd[2239063]: Stopped target Main User Target.
Jun 20 18:24:48 pve72 systemd[2239063]: Stopped target Basic System.
Jun 20 18:24:48 pve72 systemd[2239063]: Stopped target Paths.
Jun 20 18:24:48 pve72 systemd[2239063]: Stopped target Sockets.
Jun 20 18:24:48 pve72 systemd[2239063]: Stopped target Timers.
Jun 20 18:24:48 pve72 systemd[2239063]: dbus.socket: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Closed D-Bus User Message Bus Socket.
Jun 20 18:24:48 pve72 systemd[2239063]: dirmngr.socket: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Closed GnuPG network certificate management daemon.
Jun 20 18:24:48 pve72 systemd[2239063]: gpg-agent-browser.socket: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jun 20 18:24:48 pve72 systemd[2239063]: gpg-agent-extra.socket: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jun 20 18:24:48 pve72 systemd[2239063]: gpg-agent-ssh.socket: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jun 20 18:24:48 pve72 systemd[2239063]: gpg-agent.socket: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Closed GnuPG cryptographic agent and passphrase cache.
Jun 20 18:24:48 pve72 systemd[2239063]: pk-debconf-helper.socket: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Closed debconf communication socket.
Jun 20 18:24:48 pve72 systemd[2239063]: podman.socket: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Closed Podman API Socket.
Jun 20 18:24:48 pve72 systemd[2239063]: Removed slice User Application Slice.
Jun 20 18:24:48 pve72 systemd[2239063]: Reached target Shutdown.
Jun 20 18:24:48 pve72 systemd[2239063]: systemd-exit.service: Succeeded.
Jun 20 18:24:48 pve72 systemd[2239063]: Finished Exit the Session.
Jun 20 18:24:48 pve72 systemd[2239063]: Reached target Exit the Session.
Jun 20 18:24:48 pve72 systemd[1]: user@0.service: Succeeded.
Jun 20 18:24:48 pve72 systemd[1]: Stopped User Manager for UID 0.
Jun 20 18:24:48 pve72 systemd[1]: Stopping User Runtime Directory /run/user/0...
Jun 20 18:24:48 pve72 systemd[1]: run-user-0.mount: Succeeded.
Jun 20 18:24:49 pve72 systemd[1]: user-runtime-dir@0.service: Succeeded.
Jun 20 18:24:49 pve72 systemd[1]: Stopped User Runtime Directory /run/user/0.
Jun 20 18:24:49 pve72 systemd[1]: Removed slice User Slice of UID 0.
Jun 20 18:24:49 pve72 systemd[1]: user-0.slice: Consumed 3.511s CPU time.
Jun 20 18:24:59 pve72 systemd[1]: Starting Checkmk agent (192.168.178.134:33292)...
 
Code:
Jun 20 18:24:35 pve72 sshd[2239289]: Received request to connect to path /run/qemu-server/300.migrate, but the request was denied.

irgendwas nicht standard an der SSH (server) konfiguration - forwarding scheint abgedreht zu sein?
 
Last edited:
nicht das ich wuesste..
 
Hi,
bitte auch die Ausgabe von pveversion -v posten.
 

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!

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!