Recent content by vashvampir

Hello! Hello. The lvextend command will not help in this case, since you do not have LVM. In your case you need: 1. Turn off swap (swapoff /dev/sda3) 2. Remove swap partition 3. Expand the root partition (for example you may see this guide...

Hello! Testing items in this template is possible only for items with the HTTP Agent type: * `pbs.ping` * `pbs.status.datastore-usage` * `pbs.node.status` * `pbs.tasks.failed` * `pbs.version` The remaining items are taken from them by parsing the above items. If it's not difficult, can you...

By the way, in the case of Windows - I would not recommend cloning a virtual machine that has already gone through OOBE. Perhaps you should make a template out of a VM that you set up in audit mode. This will avoid a lot of problems when introducing new VMs to Windows AD Domain. You can read...

you're welcome :) As I understand it, "host" is an emulation of a processor with the same manufacturer, model and set of supported instructions as on your host machine. True, I could be wrong here, it's better to ask for a more competent specialist in virtualization. In the case of...

Sorry, mistyped. On Node (PVE Server) in Web UI. But since there is no original virtual machine left, the comparison of the configuration no longer makes sense :) Yes. Try changing to "host". (Upd. While I was writing the message, you already did it :) )

Maybe not all the VM configuration was copied correctly? I had a similar issue with Windows 11 when PVE gave it the default emulated processor (Common KVM Processor) The easiest way to compare is by running the sdiff /etc/pve/qemu-server/<VMID1>.conf /etc/pve/qemu-server/<VMID2>.conf command in...

You can also try running the journalctl -b 0 -p err command and see the errors that happened on Proxmox in terms of Linux and services. It is quite possible that there is a reason for stopping the VM For example, having just entered this command, I found out that I have problems with QEMU Guest...

No, unfortunately there was no time to do this, and with the advent of the official template from the Zabbix team, I stopped developing my template for PVE. You can try setting the following privileges for the token: / - PVEAuditor

Hello! Replied to Issue on GitHub, copyng my answer here. Most likely, the user under which the template goes to the PBS API does not have enough permissions... Minimal needed permissions for user: /datastore - Audit /system/status - Audit /system/tasks - Audit

Ok, I will return the trigger when there are new failed tasks. It remains to understand how to do it correctly, because I will have to start not from the number of failed tasks, but from changing the response from the API (the last failed task).

Oops, I think I found a bug. The trigger fires only once, and fires again if closed by hands. Thinking how to fix... Upd. The trigger can now be closed 5 minutes after it fires. Now the values of the item "PBS: Last failed backup task" are saved once every 5 minutes in the history if the value...

Updated template: 1. Item "PBS: New failed tasks" has been removed. In the future, if necessary, new items will be added according to the number of failed tasks of a certain type. 2. Added new items: - PBS: Failed tasks - Failed tasks for all time (Without history) - PBS: Failed backup tasks...

Ok, give me some time to think and experiment with the PBS API, I'll try to figure out how it would be the most logical way to monitor

I think it can slightly redo the logic of work and look for failed tasks, for example, from the beginning of the day? Then there will be a history of failed daily tasks, with the value reset to 0 at 00:00.

sudo make me a sandwich