Recent content by Tallaril

You know what? I missed your post! Tragic, because you're right, hal packet solved it! Thanks! You're my hero of the month!

ok, let's start: Node 1: lvdisplay --- Logical volume --- LV Name /dev/bazinga/root VG Name bazinga LV UUID mdjcgr-2Hdy-ioAe-27tw-iJTn-3MH0-6vuyoQ LV Write Access read/write LV Status available # open...

i've installed it through package ... it is a fresh squeeze system with 3 nodes. All 3 have it's own LVM volume group which name is the same as thenodes name. i have swap, home and root configured and the rest as free lvm space. the vm is running in LVM and this works fine .... Which...

Hi there, i have a strange problem with VM machines backup on all nodes. I've configured a automated backup at night. At backup start, the node says: INFO: starting new backup job: vzdump 202 --quiet 1 --mode snapshot --node bazinga-2 --compress 0 --maxfiles 1 --storage backup01 INFO...

Ok, i did it .... it was indeed the IP multicast .... the problem was, taht the external IP had the same shortcut (bazinga) as the internal ... i've removed the shortcut from the external ... and since then ... it works ... Thanks for your help udo :)

I guess i know what the problem is. The master and the first node are within the same rack and connected to the same switch, but this node is within a different rack and connected to a different switch. All three nodes are connected with eth1 to an own internal switch. Is it possible, that...

All right, thanks, that's clear now. I've changed it to expected 1 ... but no changes on the error. I try to restart cman: # /etc/init.d/cman restart Stopping cluster: Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Waiting for corosync to...

The main problem is, that the folder /etc/pve on the not working node looks like this: /etc/pve# ll insgesamt 1 -r--r----- 1 root www-data 465 12. Feb 17:43 cluster.conf lr-xr-x--- 1 root www-data 0 1. Jan 1970 local -> nodes/bazinga lr-xr-x--- 1 root www-data 0 1. Jan 1970 openvz ->...

this is the output on the master: # pvecm status Version: 6.2.0 Config Version: 13 Cluster Name: t4hosting Cluster Id: 50071 Cluster Member: Yes Cluster Generation: 60 Membership state: Cluster-Member Nodes: 2 Expected votes: 2 Total votes: 2 Node votes: 1 Quorum: 2 Active subsystems: 5...

This is a squeeze system with an pve kernel. # pveversion -v pve-manager: 2.0-18 (pve-manager/2.0/16283a5a) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 2.0-55 pve-kernel-2.6.32-6-pve: 2.6.32-55 lvm2: 2.02.88-2pve1 clvm: 2.02.88-2pve1 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-1 libqb...

Hi there, i have a strange problem with the above mentioned kernel. I'm running a cluster with 3 machines. 2 of them work fine, but the 3rd one is giving me continous errors in the syslog: Feb 12 16:22:29 bazinga kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder...

Hi Dietmar, i've solved it in the meantime. Not the way you've mentioned, but similar. I've just copied the cert from the master into the correct folder .... tadaaa Thanks for your help!

This error is solved, those machines were migrated from an old proxmox system (1.9). The conf file missed the vaue: PHYSPAGES="" SWAPPAGES="" Therefore the script couldn't add or multiply anything. The other error still occurs, "No certificate path provided" ...... idk

Hi, I've backuped the machines from my old node and transferred it to the new cluster. Backup and restore works fine and the CT's are up and running again. The only Problem that i have is, that not a single VM is back up. The start fails with: No certificate path provided TASK ERROR: start...

ok, i've got i by myself. The node had a wrong entry in the vhost conf of pve.cfg .... i've changed it to the right path and now it works fine :)