Difference between revisions of "Proxmox"

From DWIKI
⧼monobook-jumptonavigation⧽⧼monobook-jumptosearch⧽
m
m
Line 64: Line 64:
  
 
 
 
 
 +
  
  
Line 98: Line 99:
 
 
 
 
  
 
+
== Backups ==
  
== unexpected property 'prune-backups' (500) ==
+
=== unexpected property 'prune-backups' (500) ===
  
 
When for example Add: iSCSI Uncheck "Keep all backups" in "Backup retention"
 
When for example Add: iSCSI Uncheck "Keep all backups" in "Backup retention"
  
 
 
  
 
+
=== FAILED 00:00:02 unable to activate storage ===
 +
TODO
 +
 
 +
 
 +
=== VM 101 Backup failed: VM is locked (snapshot) ===
 +
 
 +
Check if there's no snapshot running (how?)
 +
 
 +
qm unlock 101
 +
 
 +
 
 +
=== VM 101 Backup failed::= VM is locked (snapshot-delete) ===
 +
 
 +
Check /etc/pve/qemu-server/101.conf for 'snapstate'
 +
 
 +
If that says 'delete' for a snapshot try deleting the snapshot:
 +
 
 +
qm delsnapshot 101 snapname
 +
 
 +
If that throws like Failed to find logical volume 'pve/snap_vm-101-disk-0_saving'
 +
 
 +
  qm delsnapshot 101 snapname --force
 +
 
 +
to get it out of 101.conf
  
 
== Error: VM quit/powerdown failed - got timeout ==
 
== Error: VM quit/powerdown failed - got timeout ==
Line 216: Line 239:
 
  grep name /etc/pve/nodes/*/qemu-server/101.conf |head -n 1
 
  grep name /etc/pve/nodes/*/qemu-server/101.conf |head -n 1
 
        
 
        
 
== VM 101 Backup failed: VM is locked (snapshot) ==
 
 
Check if there's no snapshot running (how?)
 
 
qm unlock 101
 
 
  
  
== VM 101 Backup failed:: VM is locked (snapshot-delete) ==
 
 
Check /etc/pve/qemu-server/101.conf for 'snapstate'
 
 
If that says 'delete' for a snapshot try deleting the snapshot:
 
qm delsnapshot 101 snapname
 
 
If that throws like Failed to find logical volume  'pve/snap_vm-101-disk-0_saving'
 
  qm delsnapshot 101 snapname --force
 
to get it out of 101.conf
 
  
 
== Started Proxmox VE replication runner. ==
 
== Started Proxmox VE replication runner. ==

Revision as of 09:01, 9 August 2021

 

 

Contents

Links

 

 

Documentation

Directory structure

/etc/pve

/var/lib/vz

/var/lib/vz/template/iso

 

 

 

 

Proxmox cluster

Cluster manager

pvecm status
pvecm nodes

 

HA status

ha-manager status

Monitoring proxmox with zabbix

https://github.com/takala-jp/zabbix-proxmox

FAQ

Proxmox API call failed: Couldn't authenticate user: zabbix@pve

Funky characters in password string?

 

 

 

 





FAQ

Cores, sockets and vCPUs

vCPUs is what the vm uses

Stop all proxmox services

systemctl stop pve-cluster systemctl stop pvedaemon systemctl stop pveproxy systemctl stop pvestatd

 

switch to community repository

cat /etc/apt/sources.list.d/pve-enterprise.list 
#deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
echo "deb http://download.proxmox.com/debian/pve buster pve-no-subscription" > /etc/apt/sources.list.d/pve-no-subscription.list 
apt update

W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!

cehck sources.list :)

 

Backups

unexpected property 'prune-backups' (500)

When for example Add: iSCSI Uncheck "Keep all backups" in "Backup retention"


FAILED 00:00:02 unable to activate storage

TODO


VM 101 Backup failed: VM is locked (snapshot)

Check if there's no snapshot running (how?)

qm unlock 101


VM 101 Backup failed::= VM is locked (snapshot-delete)

Check /etc/pve/qemu-server/101.conf for 'snapstate'

If that says 'delete' for a snapshot try deleting the snapshot:

qm delsnapshot 101 snapname

If that throws like Failed to find logical volume 'pve/snap_vm-101-disk-0_saving'

 qm delsnapshot 101 snapname --force

to get it out of 101.conf

Error: VM quit/powerdown failed - got timeout

qm stop VMID

if that complains about lock, remove the lock and try again

 

a used vhost backend has no free memory slots left

You have not turned on protection against thin pools running out of space.

serial console from command line

qm terminal <id}

enable serial console in guest

looks like this is not needed:

systemctl enable serial-getty@ttyS0.service

in /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0 console=tty0"

ttyS0 is for qm terminal, tty0 is for the "console" buttion in UI

  1. debian based

update-grub

  1. redhat based

grub2-mkconfig --output=/boot/grub2/grub.cfg

 

add

serial0: socket

to /etc/pve/qemu-server/[vmid].conf and restart

 

agetty: /dev/ttyS0: not a device

systemctl status useless again, means the serial bit is missing from <vmid>.conf

TASK ERROR: command 'apt-get update' failed: exit code 100

subtle way of telling you to get subscription of at least change the sources list

Import vmdk to lvm

https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#_importing_virtual_machines_and_disk_images

Can't apply changes to memory allocation

Maybe try enabling NUMA in CPU settings

 

 

Adding hardware shows orange

something is not supported (Options->Hotplug)

"Connection error 401: no ticket"

Login session expired?

can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout (500)

Maybe someone else has/had webui open

== TASK ERROR: Can't use string ("keep-all=0,keep-last=3") as a HASH ref while "strict refs" in use at /usr/share/perl5/PVE/VZDump.pm line 502. ==

Classic, means incorrect syntax in your /etc/pve/storage.cfg

 

The current guest configuration does not support taking new snapshots

You're using raw instead of qcow2. Convert: Hardware->Hard disk "Move Disk"

 

WARNING: Device /dev/dm-21 not initialized in udev database even after waiting 10000000 microseconds.

Until someone fixes it:

udevadm trigger

"connection error - server offline?"

Try reconnection browser

 

Find vm name by id

grep name /etc/pve/nodes/*/qemu-server/101.conf |head -n 1
      


Started Proxmox VE replication runner.

??

Find ID by name

grep -l "name: <NAME>"  /etc/pve/nodes/*/qemu-server/*conf| sed 's/^.*\/\([0-9]*\)\.conf/\1/g'