Git Product home page Git Product logo

check_mk_proxmox-qemu-backup's Introduction

Check MK Plugin to check Proxmox VM guest (QEMU) backups

Installation

On the Monitoring Server where Check_mk is installed:

For a detailed description how to work with mkp's goto https://docs.checkmk.com/latest/de/mkps.html.

Short tasks

  1. copy the XXXXXX.mkp (see dist folder) to your Check_mk server into the /tmp folder.
  2. su - <SITE_NAME> (mkp has to be installed on every site you are running!)
  3. mkp install /tmp/XXXXXX.mkp (replace XXXXXX with the filename downloaded)
  4. Check if installation worked
SITEUSER@monitoring01:/opt/omd# find . -name '*proxmox_qemu_*'
./sites/XXXX/local/share/check_mk/checks/proxmox_qemu_backup
./sites/XXXX/local/share/check_mk/checkman/proxmox_qemu_backup
./sites/XXXX/local/share/check_mk/web/plugins/wato/check_parameters_proxmox_qemu_backup.py
./sites/XXXX/local/share/check_mk/agents/plugins/proxmox_qemu_backup
  1. Goto your Check_mk webinterface. Open "Service Rules" and search for proxmox.

On the Proxmox Server (NOT THE CHECK_MK SERVER!):

  1. Copy the plugin script check_mk/agents/plugins/proxmox_qemu_backup into /usr/lib/check_mk_agent/plugins/
  2. chmod 755 /usr/lib/check_mk_agent/plugins/proxmox_qemu_backup
  3. Execute the script: /usr/lib/check_mk_agent/plugins/proxmox_qemu_backup. If everythings works the output should look like this
root@pve:/usr/lib/check_mk_agent/plugins# ./proxmox_qemu_backup
<<<proxmox_qemu_backup>>>
QEMU-MACHINE;;;;;/etc/pve/qemu-server/103.conf;;;;;machine1
QEMU-MACHINE;;;;;/etc/pve/qemu-server/102.conf;;;;;machine2
QEMU-MACHINE;;;;;/etc/pve/qemu-server/101.conf;;;;;machine3
QEMU-MACHINE;;;;;/etc/pve/qemu-server/105.conf;;;;;machine4
QEMU-MACHINE;;;;;/etc/pve/qemu-server/104.conf;;;;;machine5
/var/log/vzdump/qemu-100.log Jul 12 12:00:01 INFO: Starting Backup of VM 100 (qemu)
/var/log/vzdump/qemu-100.log Jul 12 12:00:01 INFO: status = running
/var/log/vzdump/qemu-100.log Jul 12 12:00:02 INFO: update VM 100: -lock backup
/var/log/vzdump/qemu-100.log Jul 12 12:00:02 INFO: VM Name: machine1
/var/log/vzdump/qemu-100.log Jul 12 12:00:02 INFO: backup mode: snapshot
/var/log/vzdump/qemu-100.log Jul 12 12:00:02 INFO: ionice priority: 7
/var/log/vzdump/qemu-100.log Jul 12 12:00:02 INFO: creating archive '/vmfs/bkp-fs-stor-001/dump/vzdump-qemu-100-2017_07_12-12_00_01.vma.gz'
/var/log/vzdump/qemu-100.log Jul 12 12:00:02 INFO: started backup task '0a8d0864-ffd8-497c-83ae-5422162ca8cd'
/var/log/vzdump/qemu-100.log Jul 12 12:30:31 INFO: transferred 16106 MB in 1829 seconds (8 MB/s)
/var/log/vzdump/qemu-100.log Jul 12 12:30:31 INFO: archive file size: 594MB
/var/log/vzdump/qemu-100.log Jul 12 12:30:31 INFO: delete old backup '/vmfs/bkp-fs-stor-001/dump/vzdump-qemu-100-2017_07_07-12_00_01.vma.gz'
/var/log/vzdump/qemu-100.log Jul 12 12:30:31 INFO: Finished Backup of VM 100 (00:30:30)
/var/log/vzdump/qemu-101.log 2018-02-23 07:40:02 INFO: Starting Backup of VM 101 (qemu)
/var/log/vzdump/qemu-101.log 2018-02-23 07:40:02 INFO: status = running
/var/log/vzdump/qemu-101.log 2018-02-23 07:40:02 INFO: update VM 101: -lock backup
...
...
...

Functions of the plugin

Services screenshot

check_mk_proxmox-qemu-backup's People

Contributors

aka-47 avatar dezeyer avatar edvler avatar nedjitef avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

check_mk_proxmox-qemu-backup's Issues

PVE7 / PBS2 / backup is running since

Using above Versions, the check_mk State remains in "backup is running since: ..." after the Backup is done.

This only occures for LXC Backups, QEMU are shown correctly.

Sample Output for a lxc job:

/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: Starting Backup of VM 800 (lxc)
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: status = running
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: CT Name: lnx-router
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: including mount point rootfs ('/') in backup
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: backup mode: snapshot
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: ionice priority: 7
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: HOOK: backup-start snapshot 800
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: HOOK-ENV: vmtype=lxc;storeid=PVE01-PBS;hostname=lnx-router;target=ct/800/2021-08-26T23:12:56Z
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: HOOK: pre-stop snapshot 800
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: HOOK-ENV: vmtype=lxc;storeid=PVE01-PBS;hostname=lnx-router;target=ct/800/2021-08-26T23:12:56Z
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: create storage snapshot 'vzdump'
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: HOOK: pre-restart snapshot 800
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: HOOK-ENV: vmtype=lxc;storeid=PVE01-PBS;hostname=lnx-router;target=ct/800/2021-08-26T23:12:56Z
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: HOOK: post-restart snapshot 800
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: HOOK-ENV: vmtype=lxc;storeid=PVE01-PBS;hostname=lnx-router;target=ct/800/2021-08-26T23:12:56Z
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: creating Proxmox Backup Server archive 'ct/800/2021-08-26T23:12:56Z'
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: run: lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup --crypt-mode=none pct.conf:/var/tmp/vzdumptmp2008121_800/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found --exclude=/tmp/?* --exclude=/var/tmp/?* --exclude=/var/run/?*.pid --backup-type ct --backup-id 800 --backup-time 1630019576 --repository root@[email protected]:Backup
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: Starting backup: ct/800/2021-08-26T23:12:56Z
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: Client name: pve01
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: Starting backup protocol: Fri Aug 27 01:12:56 2021
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: Downloading previous manifest (Thu Aug 26 09:31:31 2021)
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: Upload config file '/var/tmp/vzdumptmp2008121_800/etc/vzdump/pct.conf' to 'root@[email protected]:8007:Backup' as pct.conf.blob
/var/log/vzdump/lxc-800.log 2021-08-27 01:12:56 INFO: Upload directory '/mnt/vzsnap0' to 'root@[email protected]:8007:Backup' as root.pxar.didx
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:11 INFO: root.pxar: had to backup 323.36 MiB of 5.10 GiB (compressed 61.34 MiB) in 15.04s
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:11 INFO: root.pxar: average backup speed: 21.49 MiB/s
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:11 INFO: root.pxar: backup was done incrementally, reused 4.79 GiB (93.8%)
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:11 INFO: Uploaded backup catalog (892.03 KiB)
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:11 INFO: Duration: 15.25s
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:11 INFO: End Time: Fri Aug 27 01:13:11 2021
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:11 INFO: HOOK: backup-end snapshot 800
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:11 INFO: HOOK-ENV: vmtype=lxc;storeid=PVE01-PBS;hostname=lnx-router;target=ct/800/2021-08-26T23:12:56Z
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:12 INFO: cleanup temporary 'vzdump' snapshot
/var/log/vzdump/lxc-800.log 2021-08-27 01:13:12 INFO: Finished Backup of VM 800 (00:00:16)

And for qemu:

/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: Starting Backup of VM 503 (qemu)
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: status = stopped
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: backup mode: stop
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: ionice priority: 7
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: VM Name: esx03
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: include disk 'sata0' 'local-zfs-nvme2:vm-503-disk-0' 32G
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: HOOK: backup-start stop 503
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: HOOK-ENV: vmtype=qemu;storeid=PVE01-PBS;hostname=esx03;target=vm/503/2021-08-26T23:12:12Z
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: creating Proxmox Backup Server archive 'vm/503/2021-08-26T23:12:12Z'
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:12 INFO: starting kvm to execute backup task
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:13 INFO: started backup task 'c5c00529-1fc8-47f3-a7c6-923e14059cf5'
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:13 INFO: sata0: dirty-bitmap status: created new
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:16 INFO: 25% (8.2 GiB of 32.0 GiB) in 3s, read: 2.7 GiB/s, write: 0 B/s
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:19 INFO: 48% (15.4 GiB of 32.0 GiB) in 6s, read: 2.4 GiB/s, write: 0 B/s
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:22 INFO: 76% (24.6 GiB of 32.0 GiB) in 9s, read: 3.1 GiB/s, write: 0 B/s
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:25 INFO: 100% (32.0 GiB of 32.0 GiB) in 12s, read: 2.5 GiB/s, write: 0 B/s
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:25 INFO: backup is sparse: 30.66 GiB (95%) total zero data
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:25 INFO: backup was done incrementally, reused 32.00 GiB (100%)
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:25 INFO: transferred 32.00 GiB in 12 seconds (2.7 GiB/s)
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:25 INFO: stopping kvm after backup task
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:26 INFO: HOOK: backup-end stop 503
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:26 INFO: HOOK-ENV: vmtype=qemu;storeid=PVE01-PBS;hostname=esx03;target=vm/503/2021-08-26T23:12:12Z
/var/log/vzdump/qemu-503.log 2021-08-27 01:12:26 INFO: Finished Backup of VM 503 (00:00:14)

Question/Feature request

Hey there,
i run a proxmox cluster with a couple machines. Not all of them need to be backed up.
Since i have my Proxmox nodes grouped in a folder inside of checkmk i created a rule for this folder.
I tried the following settings but it either showed all as okay since they don't get checked (OK: disabled by plugin) or a lot of failed ones since i don't want them to be backed up and checked.
Is the Plugin working as intended or did i misunderstood something?
vzdump-1
vzdump2

I just want the ones checked which have a backup job (/etc/cron.d/vzdump)

plugin crashes when executed during a backup

The plugin crashes (on the check_mk site) regularly. If I see it right, it crashes while a backups is executed. I'm using check-mk 1.6.0b5 .

I'm not sure if it's the same bug as #1 , but I've tried the changed files from there, and it is exactly the same behaviour. Here the crash log:

Exception

IndexError (list index out of range)

Traceback

File "/omd/sites/rmm/lib/python/cmk_base/checking.py", line 319, in execute_check
raw_result = check_function(item, determine_check_params(params), section_content)
File "/omd/sites/rmm/local/share/check_mk/checks/proxmox_qemu_backup", line 112, in check_qemu_backup
startdate = getDateFromFileCreated(file_created[offset+6].split("/")[-1])

Locale variables

{'archive': 'nothing',
'content': u'05',
'd': time.struct_time(tm_year=2019, tm_mon=8, tm_mday=14, tm_hour=3, tm_min=17, tm_sec=49, tm_wday=2, tm_yday=226, tm_isdst=-1),
'error_count': 0,
'file_created': [u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:49',
u'INFO:',
u'creating',
u'archive',
u"'/mnt/backup_usb/dump/vzdump-qemu-100-2019_08_14-03_17_47.vma.gz'"],
'finished': 'nothing',
'info': [[u'QEMU-MACHINE;;;;;/etc/pve/qemu-server/104.conf;;;;;fischprogramme2'],
[u'QEMU-MACHINE;;;;;/etc/pve/qemu-server/100.conf;;;;;lasso'],
[u'QEMU-MACHINE;;;;;/etc/pve/qemu-server/105.conf;;;;;Win7Pro64bit'],
[u'QEMU-MACHINE;;;;;/etc/pve/qemu-server/103.conf;;;;;lasso-old'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:47',
u'INFO:',
u'Starting',
u'Backup',
u'of',
u'VM',
u'100',
u'(qemu)'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:47',
u'INFO:',
u'status',
u'=',
u'running'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:48',
u'INFO:',
u'update',
u'VM',
u'100:',
u'-lock',
u'backup'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:48',
u'INFO:',
u'VM',
u'Name:',
u'lasso'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:48',
u'INFO:',
u'include',
u'disk',
u"'virtio0'",
u"'lvm-vg-pve:vm-100-disk-2'",
u'250G'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:48',
u'INFO:',
u'include',
u'disk',
u"'virtio1'",
u"'lvm-vg-pve:vm-100-disk-1'",
u'2G'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:49',
u'INFO:',
u'backup',
u'mode:',
u'snapshot'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:49',
u'INFO:',
u'ionice',
u'priority:',
u'7'],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:49',
u'INFO:',
u'creating',
u'archive',
u"'/mnt/backup_usb/dump/vzdump-qemu-100-2019_08_14-03_17_47.vma.gz'"],
[u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:49',
u'INFO:',
u'started',
u'backup',
u'task',
u"'5e435ff3-b78c-4f21-b837-30f6c2b6ee17'"],
[u'/var/log/vzdump/qemu-100.log', u'2019-08-14', u'05'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:02',
u'INFO:',
u'Starting',
u'Backup',
u'of',
u'VM',
u'103',
u'(qemu)'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:02',
u'INFO:',
u'status',
u'=',
u'running'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:03',
u'INFO:',
u'update',
u'VM',
u'103:',
u'-lock',
u'backup'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:03',
u'INFO:',
u'VM',
u'Name:',
u'lasso2'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:03',
u'INFO:',
u'include',
u'disk',
u"'virtio0'",
u"'lvm-vg-pve:vm-103-disk-1'",
u'200G'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:03',
u'INFO:',
u'include',
u'disk',
u"'virtio1'",
u"'lvm-vg-pve:vm-103-disk-2'",
u'2G'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:03',
u'INFO:',
u'backup',
u'mode:',
u'snapshot'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:03',
u'INFO:',
u'ionice',
u'priority:',
u'7'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:03',
u'INFO:',
u'creating',
u'archive',
u"'/mnt/backup_usb/dump/vzdump-qemu-103-2019_06_14-00_15_02.vma.gz'"],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:15:03',
u'INFO:',
u'started',
u'backup',
u'task',
u"'ba7c6dbb-caf2-4cd5-bca5-9a6ec98033d8'"],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:27:09',
u'ERROR:',
u'vma_queue_write:',
u'write',
u'error',
u'-',
u'Broken',
u'pipe'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:27:09',
u'INFO:',
u'aborting',
u'backup',
u'job'],
[u'/var/log/vzdump/qemu-103.log',
u'2019-06-14',
u'00:27:11',
u'ERROR:',
u'Backup',
u'of',
u'VM',
u'103',
u'failed',
u'-',
u'vma_queue_write:',
u'write',
u'error',
u'-',
u'Broken',
u'pipe'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:41',
u'INFO:',
u'Starting',
u'Backup',
u'of',
u'VM',
u'104',
u'(qemu)'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:41',
u'INFO:',
u'status',
u'=',
u'running'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:42',
u'INFO:',
u'update',
u'VM',
u'104:',
u'-lock',
u'backup'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:42',
u'INFO:',
u'VM',
u'Name:',
u'fischprogramme2'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:42',
u'INFO:',
u'include',
u'disk',
u"'virtio0'",
u"'lvm-vg-pve:vm-104-disk-2'",
u'50G'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:42',
u'INFO:',
u'include',
u'disk',
u"'virtio1'",
u"'lvm-vg-pve:vm-104-disk-1'",
u'2G'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:42',
u'INFO:',
u'backup',
u'mode:',
u'snapshot'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:42',
u'INFO:',
u'ionice',
u'priority:',
u'7'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:42',
u'INFO:',
u'creating',
u'archive',
u"'/mnt/backup_usb/dump/vzdump-qemu-104-2019_08_14-02_34_41.vma.gz'"],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'02:34:42',
u'INFO:',
u'started',
u'backup',
u'task',
u"'88704680-7481-4107-840b-f2fb9298d331'"],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'03:17:46',
u'INFO:',
u'transferred',
u'55834',
u'MB',
u'in',
u'2584',
u'seconds',
u'(21',
u'MB/s)'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'03:17:46',
u'INFO:',
u'archive',
u'file',
u'size:',
u'8.93GB'],
[u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'03:17:47',
u'INFO:',
u'Finished',
u'Backup',
u'of',
u'VM',
u'104',
u'(00:43:06)']],
'item': u'lasso Id: 100',
'line': [u'/var/log/vzdump/qemu-104.log',
u'2019-08-14',
u'03:17:47',
u'INFO:',
u'Finished',
u'Backup',
u'of',
u'VM',
u'104',
u'(00:43:06)'],
'line_count': 11,
'logfile': u'/var/log/vzdump/qemu-100.log',
'offset': 1,
'params': {'backup_age': (93600, 108000),
'check_backup': 'check',
'running_time': 25200},
'qemu_id': u'100',
'started': [u'/var/log/vzdump/qemu-100.log',
u'2019-08-14',
u'03:17:47',
u'INFO:',
u'Starting',
u'Backup',
u'of',
u'VM',
u'100',
u'(qemu)'],
'warn_count': 0}

Agent output

<<<proxmox_qemu_backup>>>
QEMU-MACHINE;;;;;/etc/pve/qemu-server/104.conf;;;;;fischprogramme2
QEMU-MACHINE;;;;;/etc/pve/qemu-server/100.conf;;;;;lasso
QEMU-MACHINE;;;;;/etc/pve/qemu-server/105.conf;;;;;Win7Pro64bit
QEMU-MACHINE;;;;;/etc/pve/qemu-server/103.conf;;;;;lasso-old
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:47 INFO: Starting Backup of VM 100 (qemu)
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:47 INFO: status = running
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:48 INFO: update VM 100: -lock backup
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:48 INFO: VM Name: lasso
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:48 INFO: include disk 'virtio0' 'lvm-vg-pve:vm-100-disk-2' 250G
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:48 INFO: include disk 'virtio1' 'lvm-vg-pve:vm-100-disk-1' 2G
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:49 INFO: backup mode: snapshot
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:49 INFO: ionice priority: 7
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:49 INFO: creating archive '/mnt/backup_usb/dump/vzdump-qemu-100-2019_08_14-03_17_47.vma.gz'
/var/log/vzdump/qemu-100.log 2019-08-14 03:17:49 INFO: started backup task '5e435ff3-b78c-4f21-b837-30f6c2b6ee17'
/var/log/vzdump/qemu-100.log 2019-08-14 05
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:02 INFO: Starting Backup of VM 103 (qemu)
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:02 INFO: status = running
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:03 INFO: update VM 103: -lock backup
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:03 INFO: VM Name: lasso2
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:03 INFO: include disk 'virtio0' 'lvm-vg-pve:vm-103-disk-1' 200G
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:03 INFO: include disk 'virtio1' 'lvm-vg-pve:vm-103-disk-2' 2G
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:03 INFO: backup mode: snapshot
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:03 INFO: ionice priority: 7
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:03 INFO: creating archive '/mnt/backup_usb/dump/vzdump-qemu-103-2019_06_14-00_15_02.vma.gz'
/var/log/vzdump/qemu-103.log 2019-06-14 00:15:03 INFO: started backup task 'ba7c6dbb-caf2-4cd5-bca5-9a6ec98033d8'
/var/log/vzdump/qemu-103.log 2019-06-14 00:27:09 ERROR: vma_queue_write: write error - Broken pipe
/var/log/vzdump/qemu-103.log 2019-06-14 00:27:09 INFO: aborting backup job
/var/log/vzdump/qemu-103.log 2019-06-14 00:27:11 ERROR: Backup of VM 103 failed - vma_queue_write: write error - Broken pipe
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:41 INFO: Starting Backup of VM 104 (qemu)
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:41 INFO: status = running
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:42 INFO: update VM 104: -lock backup
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:42 INFO: VM Name: fischprogramme2
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:42 INFO: include disk 'virtio0' 'lvm-vg-pve:vm-104-disk-2' 50G
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:42 INFO: include disk 'virtio1' 'lvm-vg-pve:vm-104-disk-1' 2G
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:42 INFO: backup mode: snapshot
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:42 INFO: ionice priority: 7
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:42 INFO: creating archive '/mnt/backup_usb/dump/vzdump-qemu-104-2019_08_14-02_34_41.vma.gz'
/var/log/vzdump/qemu-104.log 2019-08-14 02:34:42 INFO: started backup task '88704680-7481-4107-840b-f2fb9298d331'
/var/log/vzdump/qemu-104.log 2019-08-14 03:17:46 INFO: transferred 55834 MB in 2584 seconds (21 MB/s)
/var/log/vzdump/qemu-104.log 2019-08-14 03:17:46 INFO: archive file size: 8.93GB
/var/log/vzdump/qemu-104.log 2019-08-14 03:17:47 INFO: Finished Backup of VM 104 (00:43:06)

Archive size not detected correctly with big VMs

Hello,

First of all - thanks for this plugin!

I've noticed with two of our VMs that archive size is not detected correctly and very possible cause is that size is in TB, ie:

2020-08-16 02:16:19 INFO: archive file size: 3.54TB

In CMK I can see the size as file_size=-1

Can you please fix that?

Thanks

During running Backup we get status UNKNOWN when using caching

Hi. We use and like your plugin buit use caching on agent.

We have the problem that during running KVM Backups we get Unknown status.
This seems because of our cached output...

It would be better to "save the state of the backup" before parsing and if its still running show the old state with additional info to the running job.
Setting to OK during run would reset possible acknowledgements on critical backups..

Here are the information fom the agent from one example VM:

Plugin Output:
Proxmox VM backup vm-xyz Id: 117 UNKN - error occured in check plugin. Please post a issue on https://github.com/edvler/check_mk_proxmox-qemu-backup/issues inlcuding the output of the agent plugin

<<<proxmox_qemu_backup>>>
QEMU-MACHINE;;;;;/etc/pve/qemu-server/117.conf;;;;;vm-xyz
/var/log/vzdump/qemu-117.log 2019-05-17 23:06:14 INFO: Starting Backup of VM 117 (qemu)
/var/log/vzdump/qemu-117.log 2019-05-17 23:06:14 INFO: status = running
/var/log/vzdump/qemu-117.log 2019-05-17 23:06:15 INFO: update VM 117: -lock backup
/var/log/vzdump/qemu-117.log 2019-05-17 23:06:15 INFO: VM Name: vm-xyz
/var/log/vzdump/qemu-117.log 2019-05-17 23:06:15 INFO: include disk 'scsi0' 'iSCSI-StorageXYZ-VOL601:vm-117-disk-0' 32G

.. thats all because its running

Maybe you can give us a fix for this or show how to avoid these?

Thanks

NameError: name 'check_info' is not defined

Hello,

I was trying out your plugin but noticed this error during the tests (using the latest version of check from GitHub):

$/usr/lib/check_mk_agent/local/proxmox_qemu_backup
Traceback (most recent call last):
  File "/usr/lib/check_mk_agent/local/proxmox_qemu_backup", line 207, in <module>
    'has_perfdata':              True,
NameError: name 'check_info' is not defined

Am I missing something?

Error message during CMK update from 2.1.0p14.cre to 2.1.0p15.cre

Hello,

during the update from p14 to p15 it shows me the following error:

Failed to load plugin /omd/sites/monitoring/local/share/check_mk/web/plugins/wato/check_parameters_proxmox_qemu_backup.py: module 'cmk.utils.version' has no attribute 'is_enterprise_version'
-| Traceback (most recent call last):
-| File "/omd/sites/monitoring/lib/python3/cmk/gui/utils/init.py", line 186, in load_web_plugins
-| exec(f.read(), globalvars)
-| File "", line 70, in
-| AttributeError: module 'cmk.utils.version' has no attribute 'is_enterprise_version'
-|
-| ERROR: Failed to load some GUI plugins. You will either have
-| to remove or update them to be compatible with this
-| Checkmk version.
-|
-| Updating Checkmk configuration...
-| ATTENTION: Some steps may take a long time depending on your installation, e.g. during major upgrades.
-| 1/27 Rewriting password store...
-| 2/27 Migrate Visuals context...
-| 3/27 Update global settings...
-| 4/27 Rewriting tags...
-| 5/27 Rewriting hosts and folders...
-| 6/27 Rewriting rulesets...
-| Replacing ruleset non_inline_snmp_hosts with snmp_backend_hosts
-| 7/27 Rewriting discovered host labels...
-| 8/27 Rewriting autochecks...
-| 9/27 Cleanup version specific caches...
-| 10/27 Migrating fs_used name...
-| 11/27 Migrate pagetype topics...
-| 12/27 Migrate dashlets...
-| 13/27 Migrate LDAP connections...
-| 14/27 Rewrite BI Configuration...
-| Skipping conversion of bi.mk (already done)
-| 15/27 Set version specific user attributes...
-| 16/27 Rewriting inventory data...
-| Skipping py2 inventory data update (already done)
-| 17/27 Migrate audit log...
-| No audit log present. Skipping.
-| 18/27 Sanitize audit log (Werk #13330)...
-| Skipping (already done)
-| 19/27 Rename discovered host label files...
-| 20/27 Rewriting host, service or contact groups...
-| 21/27 Rewriting notification configuration for ServiceNow...
-| 22/27 Renewing certificates without server name extension...
-| Skipping (nothing to do)
-| 23/27 Adding site CA to trusted CAs...
-| 24/27 Rewrite mknotifyd config for central site...
-| 25/27 Rewriting InfluxDB connections...
-| 26/27 Disabling unsafe EC rules...
-| 27/27 Update bakery links and settings...
-| Done

To fix the error:
remove if cmk_version.is_enterprise_version() or cmk_version.is_managed_version():
add if cmk_version.is_enterprise_edition() or cmk_version.is_managed_edition():

in check_parameters_proxmox_qemu_backup.py

Error with plugin

Hello,

I got the message that an error occurred on the plugin.

I don't see any specific errors (besides the backup error) in the attached logfile.

Am I doing something wrong?

Thanks!

log.txt

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.