Search results

  1. hakim

    How to mitigate the impact of a compromised cluster node ?

    Hi, 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...
  2. hakim

    [SOLVED] Cannot remove VM with replication on removed node

    Hi, 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...
  3. hakim

    [SOLVED] New cluster : Waiting for quorum...

    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...
  4. hakim

    [SOLVED] New cluster : Waiting for quorum...

    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...
  5. hakim

    [SOLVED] New cluster : Waiting for quorum...

    Hi, 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 =...
  6. hakim

    [SOLVED] New cluster : Waiting for quorum...

    Sorry, I looked around (and did not find anything about) but forget to simply : apt-get install omping
  7. hakim

    [SOLVED] New cluster : Waiting for quorum...

    I tried the command and it does not work ("command not found"). Any clue on how to install it ? :-/
  8. hakim

    [SOLVED] New cluster : Waiting for quorum...

    Hi, 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... From...
  9. hakim

    [SOLVED] mail: command not found

    Thanks, I installed bsd-mailx, and mails are working.
  10. hakim

    [SOLVED] mail: command not found

    Hi, 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 : # mail -bash: mail: command not found In all my previous proxmox versions, mail command was working without installing...
  11. hakim

    Errormessage at updates..

    Thanks Fabian for your explanations Hakim
  12. hakim

    Errormessage at updates..

    Hi, This error is reccurent in the syslog (and on the console) : systemd-sysv-generator[3008]: 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 ? Thanks, Hakim
  13. hakim

    Errormessage at updates..

    Hi, 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 ? Thanks, Hakim
  14. hakim

    differences between firewall level

    Hi, 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...
  15. hakim

    Warning about raw format with ZFS and KVM

    proxmox-ve: 4.1-41 (running kernel: 4.2.8-1-pve) pve-manager: 4.1-22 (running version: 4.1-22/aca130cf) pve-kernel-4.2.8-1-pve: 4.2.8-41 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-36 qemu-server: 4.0-64 pve-firmware: 1.1-7 libpve-common-perl: 4.0-54...
  16. hakim

    Warning about raw format with ZFS and KVM

    Hi, 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...
  17. hakim

    Isolating 2 KVM on the same VMBR

    >> And you also enable it in firewall/Options? It was the problem... :-/ Thanks Dietmar for your help
  18. hakim

    After updating, errors on e1000 virtual NICs

    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...
  19. hakim

    Isolating 2 KVM on the same VMBR

    >> 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 -...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!