Search results

Unfortunately, I cannot take the server offline for an extended period of time so am hoping to do a live copy of some sort. Any one have experience with Veeam backup for doing this?

I would like to convert a physical Windows 2012 R2 server to a KVM based VM. The difficult part is that the server is currently in a remote data center and I don't have local hands access to it. Therefore I need to be able to do a live copy over the internet to an image that I can be imported...

Is there an upgrade path for PMG 5.x to 6.4?

Proxmox 6 has some timeout issues dealing with NFS v3 or 4 on Synology which causes it to hang. Unfortunately, I have not found a fix other than using some other NFS server besides Synology.

Turns out our firewall had an http/https block on this range for some reason. It is all sorted out now. Sorry for the noise.

I am still seeing the same issue today. The license says it is Active and next due date is in 2022 so pretty sure it is not a license issue. I forced a re-issue of the license and then tried the following: Via the gui ... starting apt-get update Get:1 http://security.debian.org buster/updates...

I am setting up a new node and have installed the valid subscription but when I try to do an apt update, I get enterprise.proxmox.com 144.217.225.162 connection timed out. Is the proxmox enterprise repository down? Guessing it might be related to the OVH data center fires yesterday in...

Here is the output of the mount command on both hosts. Working 172.16.4.10:/volume3/proxmoxv3 on /mnt/pve/backup3 type nfs...

No nothing to speak of on the NFS server. I have another host on the latest PVE and it has the same problem so it doesn't seem to be related to the host and as I mentioned older PVE hosts have no issue going to same NAS. I've read some other threads that there seems to be a timeout issue on the...

Here are 2 nodes for comparison. The first is the working and the second is the non-working. The only difference is the working one is an older version of 6.x proxmox. FWIW, I had about 200+ VM's backup OK on the older version this weekend to the same NAS the newer ones are having issues with...

I have a newly setup proxmox server and I am having issues where the vzdump process locks up connecting to the NFS after about 2% of the backup is complete. At this point the VM is locked up and I cannot kill the vzdump process. An entire reboot of proxmox is necessary to bring things back...

I found a work around for this issue. In my case, I just removed the NFS mounts and re-set them up for NFS v3 and they worked like a charm. There must be something with NFS v4 and our NAS that was not compatible or working correctly.

I found a work around for this issue. In my case, I just removed the NFS mounts and re-set them up for NFS v3 and they worked like a charm. There must be something with NFS v4 and our NAS that was not compatible or working correctly.

I am just curious if you ever found a solution to your issue? I am seeing the same issue and am running latest proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve) . Best regards, Eric

Have you figured out what the issue was? I am still seeing this issue.

This thread is quite old but I am just curious if anything definitive has been figured out with Proxmox 6 and NFS? We are in a similar situation. We have two Proxmox clusters running v4 and v5 with no issues connecting via NFS to a Synology NAS that we use for VM backups. Our Proxmox 6 cluster...

Awesome. Many thanks!!!

In regards to the/ var/spool/pmg/cluster/2/spam/ , I looked on mx1 and verified that the same files that are on mx2 DO exist on mx1 so that looks good. Here are the only logs back from Feb 27 regarding the pmgtunnel services. There is nothing recently regarding that service in the daemon.log...

Yes, both nodes are the same size. Note that the disk shown on the command below is because I manually ran the purge again today. It was at approximate 19% on mx2 before doing that. pmgcm status NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK mx1(1)...

Here are the results... systemctl start pmgspamreport.service Job for pmgspamreport.service failed because the control process exited with error code. See "systemctl status pmgspamreport.service" and "journalctl -xe" for details. root@mx2:~# journalctl -xe -- -- The result is failed. Mar 02...