Recent content by NSW

Reporting back, no luck with the other kernels. Still crashing with the same error on both boxes. I even tried pushing one of the servers up to the pvetest repo and updating with no effect. Updated firmware on the interconnecting switch, still no luck. I guess the last option i have is to...

Udo and Dirk, Thanks for the input. I've checked the BIOS on both and they are up to date. Whats wired is the other identical server, still running 3.2-4, has had no crashing issues at all. It's only the updated boxes that are crashing. I may look at rolling back the kernel and see if that...

Hi, I am getting some random crashing with both a new install and an updated install. I've searched and cant really find any good information on it. If someone out there has any ideas, i would greatly appreciate the help. This node is part of a small cluster that was being updated from 3.2-4 to...

Well, some things to check... Are your VM's getting a proper IP address, subnet mask, gateway and DNS settings? Can you ping other VM's running on vmbr1? Can you ping other computers on your internal network? Also... Have you tried other bonding modes on bond0? You may also try removing the...

Yes, bond your interfaces and add the bond (bond0) to vmbr0. You can add all the interfaces if you wish. You will remove the configuration for eth0 if you include it in the bond. Whatever IP address you assign to vmbr0 will be where you can access your web interface and VM's will pass. So...

I'm not a networking wizard and i have the fancy equipment your talking about but this should be doable depending on the mode used. Section below taken from "http://www.linuxhorizon.ro/bonding.html". Have a look at the last two options and note the "does not require any special switch support"...

Not in the configuration for the port. They both look the same. Getting the same address, etc. Maybe try adding the "auto eth0" to it. auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 gateway 192.168.0.1 Are you sure your gateway...

Well in that case i would try to bring up the network card itself before worrying about the vmbr0 bridge. You may want to try giving eth0 a static address and then trying to ping it. Remember to reboot after you save the configuration. # network interface settings auto lo iface lo inet...

Do you have more then one network card in your computer? If so, your connection could be setup on one of the other ports.

I didn't use the backup/restore method. I just took backups in case i needed them. What i did do was take the 1.9 server off the iSCSI array, mount the iSCSI array on the 2.1 server and pull in my original LVM groups/volumes with the original VM data on them. I copied just the small VM *.conf...

Well so far (knock on wood) i'm up and going with 2.1, with both my servers running in a cluster. I will say, the new web interface and feature set is amazing. Big thanks to the Proxmox team for all their hard work.

What careful means in this situation is not having both the old version and new version accessing the same array at the same time. 2.1 wont wipe out your array unless you tell it to, but you can corrupt the data on it if both versions are accessing it at the same time. I migrated my VM's from...

Thanks Dietmar, your input is appreciated! ________________________________________________ Alright, well after one day, i have all my VM's backed up to a separate system for safety and i've started the process of upgrading my cluster. The first thing i've done is move/migrate all my VM's...

No ideas on this one then i take it. Alright, well i'll get full backups and tinker with it. I'll post back here what experiences i come across. I think my first attempt will be rebuilding one server at a time and seeing if it will play nice with the iSCSI array while the other unit is still...