Search results

Just in case anyone else stumbles across this post when looking into this. I had a similar issue where I could not restart pve-cluster. I kept getting this error: root@vmh:/mnt# service pve-cluster restart Restarting pve cluster filesystem: pve-clusterstart-stop-daemon: warning: failed to kill...

Hi Everyone, There's a couple of bugs which I'm waiting to see when they're fixed and released. I've found the v3.4 release notes announcement post which is great, but I'm wondering if there's anywhere that tells me what and when stuff has been fixed and released to the pve-enterprise repo for...

Hi, We have had a kernel panic on almost all our hosts at different times. We have 7 Dell C8220 hosts with 192GB, 256GB or 512GB RAM and either Sandy bridge E5-2680 or Ivy bridge E5-2697v2 CPU's. This has happened on Proxmox kernels 3.10-5 and 3.10-7 as well as our own compiled 3.10.5 kernel...

Hi Everyone, Our cluster (Version: 3.3-5/bfebec03) occasionally gets some communication issues between nodes. We notice this in the web gui when browsing a machine on a different node than the one we're logged into. It shows up as: Communication Failure (0) And the VM Summary page will show "no...

It looks like we're still getting this. I checked and there definitely wasn't a backfill running this time. rbd ls -l <pool_name> is what clears the lock. It's a bit odd. Any ideas welcomed.

Currently 84 OSD's in the cluster.

Hey, Has anyone seen this before? Sometimes we are seeing a VM create (or clone) fail due to the following error: TASK ERROR: create failed - rbd error: got lock timeout When this happened earlier today I could reproduce the issue until I ran some rbd commands to check that I could create or...