Search results

Udo - I've tried to search information about postscreen. I realize that is not a Proxmox question and do not want to so to far in putting non pve topics here. However could send or post how you use it in postfix config ? Or send an email please . thanks

our mail system is in an openvz . moving to kvm if it is better for high availability is something I'd do. I've a rough idea, but how is kvm better for high availability then using openvz? ps: which mail system do you use? we use postfix + dovecot + amavis.

OK got it. One more thing - can you tell me a little about ' Failover Domains' ? I googled it and will check further, but a user to user short answer would be appreciated.

e100: thanks, I think we'll try using a pair of nodes for drbd with ' The LVM on DRBD is marked as being available only on the two nodes that run DRBD.' . Then the 3-rd node can be used for development and ready to run the VM's from backup. I've never used drbd in Primary/Primary . Any...

We have a couple of containers where data changes a lot. One is a mail system. Currently for high availability we use drbd and heartbeat. So disk writes always occur at two physical servers. If the primary system fails , the other takes over and has all the emails. But heartbeat does not...

Had to do this as 'pvecm updatecerts ' did not work here cd /root/.ssh ln -sf /etc/pve/priv/authorized_keys ln -sf /etc/pve/priv/authorized_keys authorized_keys.org then rebooted all nodes as i was getting connection errors to 2 of the nodes at pve . all seems well now. thank you!

OK I fixed multicast on our switches . Rebooted and the cluster.conf updated. Now I just need to fix the symlinks in /root/.ssh Could someone please post the output of ls -l /root/.ssh so that I can try to fix root's .ssh information? thanks for the help. ps: I put pics of Netgear...

Tom - thanks - I did not notice the missing 'multicast' lines. I'll get multicast working correctly before trying to make a cluster.....

I thought that was my mistake - letting our script update /root/.ssh/ keys. so I'll disable that update then 1- remove the 2 bad nodes 2- reinstall proxmox on them 3- add them to cluster. My question- for the 'main' node , is there a way to fix the missing symlinks at /root/.ssh/ , or...

/etc/cluster/cluster.conf good file is on fbc240 . fbc246 and fbc247 had out of date /etc/cluster/cluster.conf . rebooted 246 and 247 . /etc/cluster/cluster.conf is still old on 246 and 247.

are keys in /root/.ssh taken over by cluster set up? I ask as we've been syncing a common id_rsa and id_rsa.pub to our servers for some time. maybe that is causing our issue. here is /root/.ssh : s009 fbc240 ~/.ssh # ll total 132 -rw------- 1 root root 9040 Mar 29 20:40 authorized_keys...

I had not checked the 1-st node , there is something there s009 fbc240 /var/log # zgrep cman syslog* syslog.0:Apr 6 19:38:11 s009 pmxcfs[33658]: [dcdb] crit: cman_tool version failed with exit code 1#010 syslog.0:Apr 6 19:44:07 s009 pmxcfs[33658]: [dcdb] crit: cman_tool version failed with...

not that I can see: zgrep cman syslog* syslog.2.gz:Apr 6 20:17:48 s010 corosync[2489]: [MAIN ] Successfully parsed cman config syslog.2.gz:Apr 6 20:17:48 s010 corosync[2489]: [QUORUM] Using quorum provider quorum_cman syslog.2.gz:Apr 6 20:17:48 s010 corosync[2489]...

this occured: s002 fbc247 ~ # pvecm add 10.100.100.240 copy corosync auth key stopping pve-cluster service Stopping pve cluster filesystem: pve-cluster. backup old database Starting pve cluster filesystem : pve-cluster. Starting cluster: Checking if cluster has been disabled at boot... [...

Ok I tried to set up a 3 node cluster. First made sure multicast was all set using ssmping . Then on 1-st node ran pvecm create on other 1 ran pvecm add .. the cluster is not ok. here is what we've got: s009 fbc240 /etc # pvecm nodes Node Sts Inc Joined Name 1...

Hello I'm trying to set up a 3 node cluster using wiki information. First question - does fencing need to be set up before creating the cluster?

Hello We've two 1.9 servers uing heartbeat and drbd . When upgrading the secondary to 2.0 using pve-upgrade-1.9-to-2.0 I noticed heartbeat was removed. After completing the upgrade I tried to install heartbeat and got: root@fbc4 /etc # aptitude install heartbeat The following NEW...

using dkms to install zfs see http://pve.proxmox.com/wiki/ZFS#dkms_install

I put that information to http://pve.proxmox.com/wiki/ZFS#kvm_tuning .

regarding: "Had to change primarycache to ALL to make native ZFS run more smoothly" Is that setting also needed ? if so where is it set?