Search results

>> What do you mean with "my VM I had a large cache"? A PHP / Symfony and Git cache >> How do you emptying the cache? By deleting the files in these cache

Thats right, Thanks for your answer

Hello, In my previous installation, I was able to create a backup job with : node : All storage : an external NFS storage selected VMs to backup : VMs on both nodes of my cluster It was working fine with Proxmox 6 I replaced my previous installation with a new one (new servers and new...

After further tests, I found the problem : in my VM I had a large cache with many little files. By emptying the cache before the backup, I was then able to restore it. But, what I do not understand is why I could restore this VM on my previous proxmox server (v6.4) and cannot restore it on my...

Hello and happy new year, I just installed 2 servers with the last version of proxmox (last image + updates). On these 2 servers, I am able to restore some CTs but for (at least) 2 other CTs : - the restore process starts, - the corresponding disks is filled quite quickly - and suddenly, it...

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

Thanks for your help.

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

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

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

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

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

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

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

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

Thanks Fabian for your explanations Hakim

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

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

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