Seit letztem Upade des Proxmox Hosts geht Backup Snapshot nicht mehr richtig.

H

Haxley

Well-Known Member
Jan 7, 2018
32
0
46
54
Hallo,
ich habe einen Server mit Proxmox der einige VMs hat. Die "backupt " er alle 2h auf einen Proxmox Backup Server per Snapshot. Das funktionierte bisher super. Während des Snapshots war die VM gang normal weiter verwendbar.
Seit dem letzten Update wird die VM aber nun gestoppt obwohl weiterhin Snapshot ausgewäht ist und es erscheint ein Diskettensymbol.
Das ist natürlich großer Mist, noch dazu wnen das Backup 40 Min dauert.
Hab es jetzt übergangsweis eauf 3:00 Uhr nachts gestellt wo der Schaden nicht so groß ist.

Hat das noch jemand beobachtet? Was kann man da machen? An was genau liegt das?
Das log gibt da jetz auch nicht viel her:
Das die Email nicht geht ist ja klar weil der MTA auf der angehaltenen VM liegt.
Code: 
Jan 17 10:00:12 pve pvescheduler[2817614]: <root@pam> starting task UPID:pve:002AFE4F:17A2E843:678A1C1C:vzdump:100:root@pam:
Jan 17 10:00:13 pve pvescheduler[2817615]: INFO: starting new backup job: vzdump 100 --notes-template '{{guestname}}' --storage backup --mailto admin@meinemail.de --mode snapshot --mailnotification failure --quiet 1
Jan 17 10:00:13 pve pvescheduler[2817615]: INFO: Starting Backup of VM 100 (lxc)
Jan 17 10:17:01 pve CRON[2829585]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 17 10:17:01 pve CRON[2829586]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 17 10:17:01 pve CRON[2829585]: pam_unix(cron:session): session closed for user root
Jan 17 10:28:51 pve pvedaemon[1426076]: <root@pam> successful auth for user 'root@pam
Jan 17 10:29:09 pve pvedaemon[1426076]: <root@pam> starting task UPID:pve:002B4145:17A58E76:678A22E5:vzreboot:100:root@pam:
Jan 17 10:29:09 pve pvedaemon[2834757]: requesting reboot of CT 100: UPID:pve:002B4145:17A58E76:678A22E5:vzreboot:100:root@pam:
Jan 17 10:29:33 pve kernel: fwbr100i0: port 2(veth100i0) entered disabled state
Jan 17 10:29:34 pve kernel: fwbr100i0: port 2(veth100i0) entered disabled state
Jan 17 10:29:34 pve kernel: veth100i0 (unregistering): left allmulticast mode
Jan 17 10:29:34 pve kernel: veth100i0 (unregistering): left promiscuous mode
Jan 17 10:29:34 pve kernel: fwbr100i0: port 2(veth100i0) entered disabled state
Jan 17 10:29:34 pve audit[2835479]: AVC apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-100_</var/lib/lxc>" pid=2835479 comm="apparmor_parser"
Jan 17 10:29:34 pve kernel: audit: type=1400 audit(1737106174.571:295): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-100_</var/lib/lxc>" pid=2835479 comm="apparmor_parser"
Jan 17 10:29:35 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:36 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:37 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:38 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:39 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:39 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:39 pve pvestatd[1288]: modified cpu set for lxc/102: 0-2,10-11,15-16,23
Jan 17 10:29:40 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:40 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:42 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:43 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:44 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:45 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:46 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:47 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:48 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:49 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:49 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:50 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:51 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:52 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:53 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:54 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:55 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:56 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:57 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:58 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:29:59 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:00 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:00 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:01 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:02 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:03 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:04 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:05 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:06 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:08 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:09 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:09 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:09 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:11 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:12 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:13 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:14 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:15 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:16 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:18 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:19 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:19 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:19 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:20 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:21 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:22 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:24 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:25 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:26 pve pvedaemon[1426074]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:27 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:28 pve pvedaemon[1426075]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:29 pve kernel: EXT4-fs (dm-5): unmounting filesystem 81d755ba-358a-4b53-9598-d3681b4aa340.
Jan 17 10:30:29 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:30 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jan 17 10:30:30 pve kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jan 17 10:30:30 pve kernel: fwln100i0 (unregistering): left allmulticast mode
Jan 17 10:30:30 pve kernel: fwln100i0 (unregistering): left promiscuous mode
Jan 17 10:30:30 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jan 17 10:30:30 pve kernel: fwpr100p0 (unregistering): left allmulticast mode
Jan 17 10:30:30 pve kernel: fwpr100p0 (unregistering): left promiscuous mode
Jan 17 10:30:30 pve kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jan 17 10:30:30 pve systemd[1]: pve-container@100.service: Deactivated successfully.
Jan 17 10:30:30 pve systemd[1]: pve-container@100.service: Consumed 1.813s CPU time.
Jan 17 10:30:30 pve systemd[1]: Started pve-container@100.service - PVE LXC Container: 100.
Jan 17 10:30:31 pve pvestatd[1288]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:31 pve pvedaemon[1426076]: unable to get PID for CT 100 (not running?)
Jan 17 10:30:31 pve pvedaemon[2834757]: startup for container '100' failed
Jan 17 10:30:31 pve pvedaemon[1426076]: <root@pam> end task UPID:pve:002B4145:17A58E76:678A22E5:vzreboot:100:root@pam: startup for container '100' failed
Jan 17 10:30:33 pve systemd[1]: pve-container@100.service: Main process exited, code=exited, status=1/FAILURE
Jan 17 10:30:33 pve systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Jan 17 10:30:33 pve systemd[1]: pve-container@100.service: Consumed 2.427s CPU time.
Jan 17 10:32:01 pve CRON[2836585]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 17 10:32:01 pve CRON[2836586]: (root) CMD (if test -x /usr/sbin/apticron; then /usr/sbin/apticron --cron; else true; fi)
Jan 17 10:32:01 pve CRON[2836585]: pam_unix(cron:session): session closed for user root
Jan 17 10:34:25 pve pvedaemon[1426075]: <root@pam> starting task UPID:pve:002B4C82:17A60A39:678A2421:vzstart:100:root@pam:
Jan 17 10:34:25 pve pvedaemon[2837634]: starting CT 100: UPID:pve:002B4C82:17A60A39:678A2421:vzstart:100:root@pam:
Jan 17 10:34:25 pve pvedaemon[2837634]: CT is locked (backup)
Jan 17 10:34:25 pve pvedaemon[1426075]: <root@pam> end task UPID:pve:002B4C82:17A60A39:678A2421:vzstart:100:root@pam: CT is locked (backup)
Jan 17 10:42:12 pve pvescheduler[2817615]: INFO: Finished Backup of VM 100 (00:41:59)
'
 
Hi!

Wie schaut die Config von dem Container (pct config 100) und der Task Log zu dem Backup Job im PVE WebGUI aus?
 
You must log in or register to reply here.
Top Bottom