meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
vm:proxmox:issues [2020/11/26 19:24] – niziakvm:proxmox:issues [2024/03/26 19:39] (current) – niziak
Line 1: Line 1:
 ====== Issues ====== ====== Issues ======
  
-===== failed to load local private key ===== 
  
-Node is reachable from SSH but PVE services are not working correctly. Journal shows:+===== run replication first ===== 
 <code> <code>
-/etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1737.+TASK ERROR: snapshot 'up' needed by replication job '122-2' - run replication first
 </code> </code>
  
-Directory `/etc/pve` is empty. No cluster FS propagated. +Job was previously (months ago) removed but stuck in ''Removal Scheduled'' state.  
-<code bash>systemctl start pve-cluster</code>+It looks like jobs must be enabled to perform delete remote snapshots. 
 +Snapshots was deleted months ago, so only ''force'' will help.
  
-Propagte Cluster FS but still errors in journal:+<code bash>pvesr delete 122-1 --force 1</code> 
 + 
 +Or remove jobs from file ''/etc/pve/replication.cfg'' 
 + 
 + 
 +===== Permission denied (os error 13) ===== 
 +During CT backup:
 <code> <code>
-Nov 26 19:20:13 pve5 pmxcfs[31368]: [main] notice: unable to acquire pmxcfs lock - trying again +INFO: Error: unable to create backup group "/mnt/datastore/backup/ns/home/ns/not_important/ct/114" - Permission denied (os error 13)
-Nov 26 19:20:13 pve5 pmxcfs[31368]: [main] notice: unable to acquire pmxcfs lock - trying again+
 </code> </code>
  
-reboot solves problem :(+**Solution:** fix directory permissions on Proxmox Backup Server to allow given user to create new dir. 
 + 
 +===== Full clone feature is not supported for drive 'scsi2' (500) ===== 
 +Try to clone machine from snapshot. 
 +Selecting snapshot 'current' for clone source works. 
 + 
 +**REASON:** 
 +  * It is not possible to clone disk from ZFS snapshot. It is not possible to easily and safe mount ZFS snapshot as block device to get it as source of clone. 
 +  * [[https://forum.proxmox.com/threads/full-clone-feature-is-not-supported-for-drive-efidisk0-500.71511/|Full clone feature is not supported for drive 'efidisk0' (500)?]] 
 +  * It will work with: LVM, CEPH, QCOW2 images 
 + 
 + 
 +===== Replication Job: 151-1 failed ===== 
 +<code>command 'zfs snapshot nvmpool/data/vm-151-disk-0@__replicate_151-1_1610641828__' failed: got timeout</code> 
 + 
 +''this described problem normally occurs is the pool is under load and snapshot has a lower priority.'' 
 +''Yes, the snapshot will be created because it is in the ZFS low priority queue.'' 
 + 
 +===== The current guest configuration does not support taking new snapshots ===== 
 + 
 +LXC container created on ''local-zfs'' and mount point ''/var/lib/docker'' to ''local'' storage (RAW file on disk). 
 +It is becasue ''local'' (DIR type) doesn't support snapshots! 
 +Solution is to move from ''local'' to ''RBD'' storage.