Search results

Yes, I've tried different browser. I even tried curl. # curl -skv https://10.0.0.5:8006/ > /dev/null * Hostname was NOT found in DNS cache* Trying 10.0.0.5... * Connected to 10.0.0.5 (10.0.0.5) port 8006 (#0) * successfully set certificate verify locations: * CAfile: none CApath...

So, any ideas how to fix that behaviour?

Please, do not troll. Cache and cookies were the first thing to check. No luck.

Any hints? I'm experiencing this error on every node in my cluster. No name changes for nodes or anything like that. Several nodes were upgraded from proxmox 3, several are fresh installs. I can only see login form in web gui. After entering correct user/password I receive nothing from server...

Installed pve-kernel-3.10.0-12-pve from pvetest. vlans are working.

eth0 does not have vlans and thus works fine. eth1 has 2 vlans and is not working with -41 kernel. both cards use e1000e driver

no, i'm not using openvz. and no, i will not upgrade to 4.0 just yet, i'd rather stick with -40 kernel. what could possibly break vlans in -41? and what else do you want to know about my network setup? looks like i've told you everything

82579LM and 82574L

here you go auto lo vmbr0 vmbr1 iface lo inet loopback iface vmbr0 inet static address 10.xx.xx.xx netmask 255.255.255.0 gateway 10.xx.xx.xx bridge_ports eth0 bridge_stp off bridge_fd 0 bridge_maxwait 0 iface vmbr1 inet manual...

fyi, bridge+vlans in 2.6.32-164 are also nonfunctional

Yep, missed it. The same problem and no replies. :(

Hi. I have VM with pfsense inside it. Physical node has 2 eth interfaces which I use in following way: eth0 bridged into vmbr0 for lan, eth1 with 2 vlans bridged into vmbr1 for uplinks. # brctl show bridge name bridge id STP enabled interfaces vmbr0...

Yes, no problems since my last post. The problem itself requires a very specific conditions. I believe all tg3 cards are affected by this but the first time I ran into this error only on 2 or 3 servers out of 30. Moving VM to another node however moved the error with it. I guess it's somehow...

And more specifically the problem is related to virtio NIC in KVM guest. I've just changed it to e1000 and the problem hasn't repeated yet.

Recently I've received several Dell R730 servers in Hetzner for existing project. Unfortunatelly the built-in NICs are not very good with KVM virtual machines. As soon as I put some (20-50 Mbps) traffic on VM the host dumps some backtrace and disables the interface. The problem isn't new and is...

Ah, yes, indeed. But .old-dkms are not being removed. Don't know if they should be. # ls -l /boot/ total 57M -rw-r--r-- 1 root root 104K Nov 8 08:42 config-2.6.32-34-pve drwxr-xr-x 4 root root 7.0K Nov 8 13:30 grub -rw-r--r-- 1 root root 17M Nov 9 10:26 initrd.img-2.6.32-33-pve.old-dkms...

This is not really a big deal but why does not old initrd files get removed on kernel removal? # ls -l /boot/ total 71763 -rw-r--r-- 1 root root 105982 Nov 8 08:42 config-2.6.32-34-pve drwxr-xr-x 3 root root 5120 Nov 9 09:12 grub -rw-r--r-- 1 root root 16485840 May 27 08:11...

Unbelivable. Several times with no succes and it was right here under my nose. :D Thanks!

What is the current status of ipset? proxmox-ve-2.6.32 package seems to be dependent on ipset and xt_set.ko is present in pve-kernel package but I'm unable to use it. # ipset -N set1 iphash adds set without errors # ipset --save create set1 hash:ip family inet hashsize 1024 maxelem 65536 there...

Figured it myself :) Just add site to trusted in Security tab of Java CP.