Search results

I found out it was because i had ntpdate & ntp installed both (see release notes about this). Didn´t read the manual well enough.

Did you find the cause of this yet? I have the same problem with one of our servers going from proxmox 7 to proxmox 8. Still can't find what is causing the hang.

Hi all, I would like to check with the community about my findings for storage replication for a specific use case. In short: I have a CCTV VM which stores incoming CCTV video recordings. For simplicity it's a Windows VM with a 100GB OS disk (on a ZFS RAID1 with 2x 240GB SSD's) and a 10TB data...

Some more digging revealed that the proxmox-backup-daily-update.service creates the /var/log/proxmox-backup/tasks directory with root:root ownership if the directory doesn't exist. maybe this has already been fixed in newer PBS versions but here's how to reproduce in pbs 1.1.13-2: 1. Stop all...

After some digging i found out that the culprit was that the /var/log/proxmox-backup/tasks directory was owned by root:root in stead of backup:backup. Whenever you delete /var/log/proxmox-backup directory it is automatically created upon service restart. The api directory is correctly set to...

Hi All, I seem to have botched my installation of pbs and cannot seem to find the reason why. whenever i backup a vm it results in: INFO: starting new backup job: vzdump 100 --node stellar01 --remove 0 --mode snapshot --storage pbs INFO: Starting Backup of VM 100 (qemu) INFO: Backup started...

Hi All, I've setup many ZFS two node clusters in the past (technically 3 node using a small HA node) and CEPH clusters in the past but i'm thinking about the following idea: 4 main nodes and a small HA node 1. Create a cluster using all five nodes. 2. Setup ZFS storage replication between...

Would it be possible to combine both ZFS Storage Replication and pve-zsync for a single VM? For instance, we have a 'main' site with a 3-node ZFS cluster (2 full nodes and a small node for HA) using Storage Replication so we have High Availability for the VM Next i would like to have some...

Thanks for the hints! It turned out i had /etc/systemd/system/systemd-udevd.service.d/override.conf configured only containing: [Service] ExecStartPost=/bin/sleep 15 Removing this file before the upgrade fixed the problem. I didn't expect this small change could potentially lead to a broken...

I seem to be running into some major problems during upgrade. The udev and/or systemd crash upon restarting udev after upgrade: When the upgrade proces comes to udev: ----- Setting up udev (241-5) ... Configuration file '/etc/init.d/udev' ==> Modified (by you or by a script) since...

+1 for this I am using EC pools with 12.2.5 so i'm fearing the worst but hopefully my workload didn't trigger any corruption.

Well it's actually the other way around: To use erasure coded pools for RBD you need to create an RBD image on a replicated pool and specify a seperate data pool (which is erasure coded). This ensures all metadata to be written on the replicated pool and the actual data is written to the...

Hi, In a 3 node CEPH/Proxmox 4 HA Cluster, I recently had a Windows 7 Guest VM hang (BSOD). As expected HA never kicked in because in proxmox' point of view the VM is up and running. I thought maybe the QEMU Guest Agent would help checking for hung VM's but when I checked the wiki page it only...

Hi all, We have a 4 node proxmox 4.2 cluster. We cannot seem to get the HA manager in a healthy state. The config of HA looks empty (resources.cfg = empty and ha-manager config shows nothing). BUT the status shows different (same output on all 4 nodes): # ha-manager status -verbose quorum OK...

Thank you both for the replies. I managed to pinpoint the problem to the USB Controller and or firmware. I installed proxmox into a USB Harddisk of 256GB, I guess the HP's have a limit of some sort to be able to boot USB devices beyond a certain size (I've read 4GB will boot, but 8GB and 16GB...

Hi All, I'm trying to revive some old hardware to have some use. I was hoping to create a small test Proxmox 4.2 Ceph cluster with 4 HP Proliant DL380 G5 Servers. Installing Proxmox 4.2 finishes without errors HOWEVER booting fails (in fact loading grub fails) It says: error: unknown...

Sorry forgot the version info: # pveversion -v proxmox-ve: 4.1-39 (running kernel: 4.2.8-1-pve) pve-manager: 4.1-15 (running version: 4.1-15/8cd55b52) pve-kernel-4.2.8-1-pve: 4.2.8-39 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-33 qemu-server: 4.0-62 pve-firmware...

Hi all, When I shutdown a pve node (using the GUI, select the node and then select the shutdown button in the upper right) I noticed that one of the first services to actually stop is CEPH. CEPH is stopped before pve-manager for instance. When pve-manager is stopped, it tries to cleanly...

Me too! Thanks for fixing!

Any news on this issue? Is there a patch available we can test?