Hi folks!
I want to start by apologizing for what might be a long and confusing post, but here goes:
We currently have a cluster with 3 frontends running Proxmox, using a shared Nexenta SAN for storage. The storage server is connected to our switches using 10Gb SFP and the frontends using...
Hello!
Since November 29th we have not been able to reach the Proxmox download-repos from our nodes.
I also tried pinging the IP from a completely different ISP (both in Norway though) but still nothing.
Is anyone else experiencing problems these days?
HA is configured and enabled for all vms running, so nothing new there. I still have not rebooted the node, I'm waiting until the next maintenance window.
Thanks again!
I'm sorry, could have been clearer.
When I ssh in to the box:
But when I'm logged in:
There it is correct.
vmfe01 is the correct hostname of the node.
intern01 that comes up right when I log in is the virual machine which I tried to migrate over.
It may be that the way we are migrating is a...
As I mentioned the hostname is correct after I login.
But if I just reboot the node is there a chance of corruption of the running vms?
Or could I live-migrate them to the other nodes (that would maybe not work since there state shows as stopped)?
I tried that command yesterday.
Just now I noticed that under "Services" on the node everything except SMTP has status stopped.
Tried restart pve-cluster, but got the following error:
Also, when I ssh into the box, it show the hostname and kernel of the virtual machine I recently tried to...
Hi everyone!
About 6 months ago we purchased brand new servers, installed Proxmox and started migrating our existing KVM virtual servers to the Proxmox platform.
We have 3 frontends running Proxmox in a cluster, all attached to a SAN running Nexenta.
Everything has been working smoothly, but a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.