Search results

Hi, I have searched here on the proxmox forum for a couple of hours without finding what i looking for. For example so have both solusvm and Opennebula created a feature called IP Hijacking, it prevent users to be able to add a different IP-adress on their virtual machine that's not belongs to...

check with df -h and see what takes up all the space.

Any update regarding this?

And yes the NFS server is not a part of the cluster. This is what i could find from the entire log: journalctl -lf -u corosync

1. No information in syslog. 2. journal gives me this if i search for "new membership" (journalctl -r | grep 'new membership') "Mar 13 01:10:01 tc01-c-h corosync[2065]: [TOTEM ] A new membership (10.10.13.102:178832) was formed. Members" Can the problem be the gigabit connection to the NFS...

Hi, i have run the test on all nodes and this is the results: node#1 You can find all nodes results here : https://pastebin.com/0d6kBJTL And yes the network is also used for an NFS connection to some containers, but on a separate VLAN of course.

I have running this command between the two nodes without any loss: nod#1 root@node1:~# omping -c 10000 -i 0.001 -F -q 10.10.13.102 10.10.13.103 10.10.13.103 : joined (S,G) = (*, 232.43.211.234), pinging 10.10.13.103 : waiting for response msg 10.10.13.103 : server told us to stop 10.10.13.103...

Hi, What i can see from the logs so is it something very strange that is going on with the cluster under heavy load (for a long amount of time, it could take about 3-4 days after the load was ended to the problem start to exist in the cluster. I can not found any drops on the interface that...

anyone ? :/

Hello Dietmar, ok, see host w02-c-h below : root@w02-c-h:~# pvecm nodes Membership information ---------------------- Nodeid Votes Name 1 1 w01-c-h 2 1 tc01-c-h 3 1 tc02-c-h 5 1 tc03-c-h 7 1...

Hello, I have in total 14 hosts added in my proxmox cluster and some machines can just see 13 of them. Under pvecm nodes it finds all the 14... Membership information ---------------------- Nodeid Votes Name 1 1 w01-c-h 2 1 tc01-c-h 3...

Yah that is something that i'm want to.

Sigxcpu, thanks for you fast answer, then i basically add this values for all hosts (physical) and all containers will get this?

Hi, What i want is to put this values direcly in to all lxc containers. net.core.rmem_max = 67108864 net.core.wmem_max = 67108864 net.core.rmem_default = 33554432 net.core.wmem_default = 33554432 net.core.optmem_max = 40960 net.ipv4.tcp_rmem = 4096 87380 33554432 net.ipv4.tcp_wmem = 4096 65536...

+1

then it should works good but you have to remember that 12GB raidcontroller vs HBA if there is just a few drives added the raid controller will win the battle.

how much space are we talking about?

You have to take in mind that the server will use a lot more memory if you going on with ZFS.

IF it works with Debian 8 then i dont see this as a problem. But why are you not going with a perc H730 raid controller instead?

adamb i have just solved the issue :-) I move the hostname back to the original tc-05-vm-c and recopy the files in /etc/pve/nodes and now the cluster comes up green. Now i can remove it from the cluster and reinstall the server :) See the below : pvecm nodes Membership information...