Recent content by cdukes

Just wanted to say thanks! This seems to be a new issue, most likely with the latest cloudflared. We were running an old cloudflared from last year and just updated it over the weekend when this started happening. For anyone else that ends up here. Here are the settings:

Backups ran last night and it happened again. Can anyone please help?

Yes, all vm's have it. LZO compression and Snapshot mode Underlying storage for the VM's are ZFS on 4k block NVMe drives. (see attached screenshots)

# pveversion pve-manager/6.1-3/37248ce6 (running kernel: 5.3.10-1-pve) I can't seem to figure out why this is happening, but every time our backups run, the vm's that were backed up come back up with read-only filesystems and I have to restore form the backup to get them working again. This is...

I have verified 100% that the port on the switch this is connected to is correct I have replaced the cable (even though there were no errors on the switch - just in case) Both the switch and the server (ethtool) say the port is ip When the cable is unplugged, both the server and the switch show...

Anyone? I could really use some help here. Our cluster is still down.

Nothing there. Nothing in dmesg either.

Anyone out there?

I can't figure out why this is happening. I have 3 servers and all can ping the backend cluster vlan except for the primary The primary - 192.168.29.14 can ping all other nodes on their other vlans: vlan 29 - cluster comms - no ping vlan 28 - works vlan 10 - works As a result, the cluster won't...

I ran into this problem today. It is a symlink issue and my proxmox server are up to date. This fixed it: find /mnt/pve/SOMEMOUNT -type l ! -exec test -e {} \; -print If any results show there, it means there's a broken symlink. Remove it and all will be well.

Hi Tom, is there a link to documentation for this new method?

Working server (pve4): cartman:/volume1/proxmox on /mnt/pve/cartman type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.16.28.2,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=10.16.28.2) pve5 server...

dmesg says: [Tue Apr 9 10:45:01 2019] nfs: server cartman not responding, timed out [Tue Apr 9 10:45:01 2019] nfs: server cartman not responding, timed out [Tue Apr 9 10:45:07 2019] nfs: server cartman not responding, timed out [Tue Apr 9 10:45:07 2019] nfs: server cartman not responding...

Which version should it be in once released?

/mnt/pve/cartman does exist on all nodes, but on pve5, I can't `ls` or `df` because it's hung. if I `umount -l` and then mount it from the shell using `mount -t nfs cartman:/volume1/proxmox /mnt/pve/cartman`, it mounts and works in the shell, but not in the gui. Storage config: root@pve5 [~]...