[SOLVED] qmp command 'guest-fsfreeze-freeze' - Lässt VMe neustarten bei Backup

k.winter

New Member
May 24, 2022
14
2
3
Hallo,

beim nächtlichen Backup passiert es leider jede Nacht um die gleiche Uhrzeit. Der Cron läuft jedoch alle zwei Stunden und ich bin etwas ratlos.

Im Syslog bei Plesk sehe ich nur folgende Info: Guest-fsfreeze called

Danach startet die VM komplett neu.

Code:
root@pve1:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-6
pve-kernel-helper: 7.2-6
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-3
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-5
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

Kann hier jemand helfen?
 

k.winter

New Member
May 24, 2022
14
2
3
Nachtrag: Hier nochmal mehr Infos aus dem Syslog wenn diese helfen
Code:
Jul 4 02:00:02 server1 qemu-ga: info: guest-ping called
Jul 4 02:00:02 server1 qemu-ga: info: guest-fsfreeze called
Jul 4 02:00:02 server1 postfix/smtpd[15848]: warning: hostname liferson.de does not resolve to address 141.98.10.84: No address associated with hostname
Jul 4 02:00:02 server1 postfix/smtpd[15848]: connect from unknown[141.98.10.84]
Jul 4 02:00:05 server1 plesk_saslauthd[16232]: select timeout, exiting
Jul 4 02:00:05 server1 plesk_saslauthd[17630]: listen=6, status=5, dbpath='/plesk/passwd.db', keypath='/plesk/passwd_db_key', chroot=1, unprivileged=1
Jul 4 02:00:05 server1 plesk_saslauthd[17630]: privileges set to (107:114) (effective 107:114)
Jul 4 02:00:05 server1 plesk_saslauthd[17630]: failed mail authentication attempt for user 'demo' (password len=10)
Jul 4 02:00:05 server1 postfix/smtpd[15848]: warning: unknown[141.98.10.84]: SASL LOGIN authentication failed: authentication failure
Jul 4 02:00:05 server1 postfix/smtpd[15848]: disconnect from unknown[141.98.10.84] ehlo=2 starttls=1 auth=0/1 quit=1 commands=4/5
Jul 4 02:00:15 server1 systemd[1]: Created slice User Slice of UID 0.
Jul 4 02:00:15 server1 systemd[1]: Starting User Runtime Directory /run/user/0...
Jul 4 02:00:15 server1 systemd[1]: Started User Runtime Directory /run/user/0.
Jul 4 02:00:15 server1 systemd[1]: Starting User Manager for UID 0...
Jul 4 02:00:15 server1 systemd[23464]: Listening on GnuPG network certificate management daemon.
Jul 4 02:00:15 server1 systemd[23464]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 4 02:00:15 server1 systemd[23464]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 4 02:00:15 server1 systemd[23464]: Reached target Timers.
Jul 4 02:00:15 server1 systemd[23464]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 4 02:00:15 server1 systemd[23464]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 4 02:00:15 server1 systemd[23464]: Reached target Sockets.
Jul 4 02:00:15 server1 systemd[23464]: Reached target Paths.
Jul 4 02:00:15 server1 systemd[23464]: Reached target Basic System.
Jul 4 02:00:15 server1 systemd[23464]: Reached target Default.
Jul 4 02:00:15 server1 systemd[1]: Started User Manager for UID 0.
Jul 4 02:00:15 server1 systemd[23464]: Startup finished in 29ms.
Jul 4 02:00:15 server1 systemd[1]: Started Session 71561 of user root.
Jul 4 02:00:35 server1 plesk_saslauthd[17630]: select timeout, exiting
 

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 your own in 60 seconds.

Buy now!