I'm running proxmox (Latest community) on a Hp micro server gen 8.
Every time i create a new CT and start it, I get this error:
<root@pam> end task UPID:local1:000079DF:007F34B9:5AC8B6C3:vzstart:103:root@pam: command 'systemctl start pve-container@103' failed: exit code 1
And nothing else in...
I've also got the same issue, I was the one that commented on the bug-tracker.
Would be nice if we could get an official Proxmox answer on this issue, It's extremely annoying and present in all of our backups and VM's (Since all of them use special characters in one way or another).
Again i have this issue but this time on THE MAIN SERVER IP!!! This is getting so tiresome it's ridiculous!!
This time doing an ARP ping does "fix" the download, but it does NOT solve the uplink that is below 20Mbit/s.
Maybe it's time to make some noise on Webhostingtalk and other places so...
This is clearly a router/gateway issue, doing an ARP Cache broadcast towards the OVH Gateway, restores speed again for 7 minutes!
Do this on a VM and see for yourselves:
arping -c 1 -S VMIP GATEWAYIP
EDIT: arping included in iputils is not the same, i had to do apt-get install arping for it to...
An official guide doesn't seem to exist for Proxmox 4.x and vRack is a security issue:
Since it seems you have to do proxy forwarding of internal traffic to the VLAN, something that leaves you vulnerable to customers changing...
I'm well aware of their vRack guide, but this is not part of the issue (Plus their guides are ancient).
This is the official Proxmox guide för OVH and it doesn't require vRack:
Or are you saying that the issue don't exist on OVH with vRack and failover IP's?
I think it's because the connection is reseted on the switch that causes it, I've seen high speeds for about 2-3 seconds and then go down FAST. It seems this effect is larger when you reboot the VM (You get the same effect if you reset the network on the VM too). I'm sure it's not Proxmox...