Search results

Here are the logs of a backup: INFO: Starting Backup of VM 1329 (lxc) INFO: Backup started at 2021-09-29 00:22:32 INFO: status = running INFO: CT Name: mycontainername INFO: including mount point rootfs ('/') in backup INFO: backup mode: snapshot INFO: ionice priority: 7 INFO: create storage...

Hello, I'm having an issue with my LXC guests using fuse-overlayfs (docker storage): they can't be either replicated (ZFS replication between nodes) nor backed up over my NAS (NFS share). The container freezes and will never resume its frozen state. I'm runing the latest 7.0 ...

I'm on pve-entreprise, I see the pve-manager and qemu-server upgrades. I must have missed something but is it worth installing without installing a patched kernel ? (If new kernels leaves the pvetest/pve-no-subscription zone to a stable one soon, then I probably should wait and install all at...

Hi, Any idea of when the patched kernels will leave pvetest ? 'Kinda worried to switch to pvetest on production servers...

Posting how I solved it: Manually restarted all nodes that were not in sync and made sure the sqlite file had nos corruption: On one node I had duplicate entries that I had to manually delete from backup.db before restoring the backup into database_fixed.db Got all my nodes running smoothly...

In case you have an issue with pmxcfs as I did, I'll update the other thread I started after I finally had the upgrade done:

I fired up all my nodes (17), and only 6 are synced.. Some of my nodes are up for over 2 hours, all containers are up, but nodes are still not synced... Any way to force a sync ? I'm kind of worried anything happens if I let it this way..

Hi, I have an issue with my cluster (5.1), newly updated, I have only 3 nodes synced (pmxfs / dcdb) out of 10 nodes up. The 7 remaining never catch up to date... It seems the updates are sent, but always the same amount of updates, and I've not seen any node catching up... Here are the...

Ok, in case it ever happens to someone else, I managed to update by manually stop corosync and pve-cluster on all nodes, then apt-get -f install.

It seems "/usr/bin/pvecm updatecert" times out when trying to restart pve-cluster Any hint ?

Hi Tom, thanks for your reply. I did a regular upgrade: apt-get update apt-get dist-upgrade repos are valid. If I try to apt install proxmox-ve, it also hangs when trying to install pve-cluster (5.0-15)...

Here is what happens when I try to apt-get -f install: Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires : corosync-pve docutils-common docutils-doc javascript-common libalgorithm-c3-perl libarchive-extract-perl libasprintf0c2 libb-hooks-endofscope-perl...

Hi, On my 17 nodes cluster I have half of my nodes that won't perform the upgrade from 5.0 to 5.1. All the missing nodes fails installing pve-cluster, here are the logs: Paramétrage de wget (1.18-5+deb9u1) ... Paramétrage de pve-cluster (5.0-15) ... Job for pve-cluster.service failed because a...

2 of them are indeed. One working and the one not working. Are there some logs that could talk about any multicast issue at startup ? I can't find/track anything..

Hi, I have a 15 nodes cluster that apparently does not work with multicast, and I would like to enable it. I've read the Multicast notes from https://pve.proxmox.com/wiki/Multicast_notes Multicast IS enable on my network, I tested ssmping on all nodes without issue. I have 3 proxmox...

Finaly found a way to fix my issue: it seems the target node where the CT was migrated was correctly online but "alone" from its point of view.. It was the only entry in /etc/pve/.members Fixed after restart of the node.

Hi, After a failed "restart" migration, now have an LXC container that refuses to start and that I can't destroy. On the GUI, I do have the CT appearing on the correct node but the API seems to reply a 500 error code. On the GUI any action gives "Error: Configuration file...

A few weeks later, I did not experience any cluster/gui issue since. All nodes stays available at all time on the gui, so I'd say it did the trick for me ! I did have some backups issues since I turned nfs mounts to soft type, and had several "NFS server is not available" so you'd better watch...

Quick follow-up since I started the thread: - I changed NFS mount from hard to soft - changed corosync token time from default (1000) to 3000. No red node nor cluster gui unavailable for the last 24h. My best guess would be that 1 - for some reason NFS server may have been overloaded during...

3000ms instead of 1000ms.