In a cluster, every nodes can access each other with root privileges. Therefore, if one node get compromised all other are also compromised.
Is there a way to mitigate the impact of a compromised cluster node on the other nodes ?
A way to maybe only give an elevation of privilege to the...
I have a cluster on which I removed a node following Proxmox doc.
Now, I want to remove a VM from one of the existin cluster nodes, but this VM has a replication scheduled on the node which was removed.
I tried to remove the scheduled replication job from the Web UI, but it fails with no...
For whom it may help,
It appears that for an obvious reason, when two nodes have problem to communicate the nodes cannot be rebooted (need hardware reboot).
The problem of communication was because not only the nodes communicate on TCP 22 and UDP 5404,5405 (which is described in the doc) but...
Well it was a problem with the server firewall ...
After using :
iptables -A INPUT -i vmbr1 -s 10.1.0.0/24 -m pkttype --pkt-type multicast -j ACCEPT
Multicast was working...
But ... I had weird problem with my servers : could not reboot (either from the console or from GUI), the server and...
Thanks for your reply, in fact it was a typo mistake,
I did : pvecm add 10.1.0.1, and get the waiting for quorum error
After testing with omping, I have a multicast problem, that I am trying to troubleshoot.
unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev =...
l installed 3 new Proxmox servers v5.1, and I would like to set them as a cluster.
on serv1 (10.1.0.1) :
pvecm create MYCLUSTER
on serv2 (10.1.0.2) :
pvecm add 10.1.0.2
=> I entered the root password
and I get process messages and then it was blocked on :
waiting for quorum...
I am installing a new server with Proxmox 5.
I have errors in my syslog :
zed: error: all-notify.sh: eid=1: "mail" not installed
and the mail command is not working :
-bash: mail: command not found
In all my previous proxmox versions, mail command was working without installing...
This error is reccurent in the syslog (and on the console) :
systemd-sysv-generator: Ignoring creation of an alias umountiscsi.service for itself
As explained before, it happens both :
- at each reboot
- and after doing an upgrade
Does anybody knows what it is about ?
I have the same kind of error message in my syslog :
- for each reboot
- and apparently also after doing an upgrade
Il also noticed that other users have the same kind of error in the middle of the log that they post in this forum.
Any idea what can it be ?
From what I have seen (looking at the final rules generated by iptables - using iptables-save, as suggested in the doc), the rules that are applied to the containers are FORWARD rules (at the host level). An the default FORWARD chain accept all the traffic.
This might be why the DC and...
Each time I restore a KVM vm in my ZFS dataset filesystem, I get the following message :
WARNING: Image format was not specified for '/dev/zvol/proxmox/vm-100-disk-1' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will...
I noticed the same kind of problem using e1000 NIC (on a KVM vm) : I had about 1/3 of my packets with error (in Proxmox 4), and I did not have this kind of problem with Proxmox 3.4.
Using Virtio NIC instead was a solution for me, but there is apparently a problem with the e1000 driver (which is...
>> And you power cycled the VMs after setting this (stop/start)?
Thanks for your answer. Yes I did it - many times.
I look at the iptables rules generated and I do not see anything that could match my drop rules. I also tried to specify the interface (net0), (after looking at the iptables -...